CLI Reference
Projects
Section titled “Projects”tycho project create my-project --path ~/Code/my-project --name "My Project"tycho project show my-projecttycho project update my-project --group Personal --harness codextycho project archive my-projectProjects must be created explicitly. tycho project my-project no longer creates one and fails without changing the registry.
Agent Sessions
Section titled “Agent Sessions”tycho agent create my-project "Refactor the auth module" --runtycho agent listtycho agent list my-projecttycho agent status my-project-agent-3tycho agent logs my-project-agent-3 --type conversationtycho agent send my-project-agent-3 "The tests still fail. Try a smaller change."tycho agent stop my-project-agent-3tycho agent archive my-project-agent-3tycho agent clone my-project-agent-3 --runCreate an explicit child session:
tycho agent create my-project "Check the API boundary" \ --parent-agent my-project-agent-3 \ --runTycho never infers a parent from TYCHO_AGENT_KEY. A managed agent must pass --parent-agent "$TYCHO_AGENT_KEY" explicitly. Omitting it creates an unrelated root; --root makes that intent explicit.
The same relationship can be attached to an idle existing session before its next run:
tycho agent send child-agent-key "Continue the delegated check" \ --parent-agent parent-agent-keytycho agent run child-agent-key --parent-agent parent-agent-key--parent-agent and --root are mutually exclusive. A managed session that creates work with --server must choose one explicitly. Both parent and child must exist on that target server. See Delegating Work Between Agents.
Inspect archived sessions without mixing them into active polling:
tycho agent list --archivedtycho agent list --include-archivedSchedules
Section titled “Schedules”tycho schedule create weekday-maintenance \ --cron "0 9 * * 1-5" --timezone local --project-key my-project \ --agent-name "Weekday maintenance" --message "Run the maintenance check."tycho schedule update weekday-maintenance --agent codex --model gpt-6-astra --reasoning-effort mediumtycho schedule listtycho schedule validatetycho schedule run weekly-reviewtycho schedule pause weekly-reviewtycho schedule resume weekly-reviewtycho schedule reloadtycho schedule daemontycho schedule daemon --oncetycho schedule daemon --dry-runThe dedicated daemon owns the clock; the TUI and Remote UI only manage it. See Schedules.
Remote UI
Section titled “Remote UI”tycho servetycho serve daemontycho restartCheck the installed version with tycho --version or tycho -v. tycho update upgrades a Homebrew installation and restarts running local services through their stable launcher; source checkouts update through Git instead.
When Tailscale is available, Tycho can expose a MagicDNS URL and terminal QR code for checking agent state from another device on your tailnet.
See Remote UI for localhost, bearer-token, tailnet, multiserver, and browser workspace boundaries.
Second Brain Memory Handoffs
Section titled “Second Brain Memory Handoffs”tycho memory handoffstycho memory handoffs --server vps --jsonSuccessful runs may return a semantic memory_handoff. Tycho stores it with run-owned provenance and exposes it locally or from one configured peer. This command does not search raw conversations or failed runs.
Remote Servers
Section titled “Remote Servers”After adding a server under remote_servers in ~/.tycho/config/hq.yml, store and verify its credential without placing the token on the command line:
tycho server login vpstycho server status vpstycho server verify vpstycho server logout vpstycho server migrate vpstycho server migrate --alllogin verifies before saving unless --no-verify is set. status reports metadata and never prints the token. migrate moves legacy inline hq.yml tokens into the private credential store.
Target that server with the same project and agent commands:
tycho project list --server vpstycho project show my-project --server vps --jsontycho agent list my-project --server vpstycho agent status my-project-agent-3 --server vps --jsontycho agent create my-project "Inspect the failing build" --server vpstycho agent run my-project-agent-3 --server vpstycho agent send my-project-agent-3 "Try the smaller reproduction" --server vpstycho agent stop my-project-agent-3 --server vpstycho agent archive my-project-agent-3 --server vpsProject list and show, the remote agent lifecycle above, and metrics support --json. Local-only agent logs and agent clone do not accept --server.
Usage Metrics
Section titled “Usage Metrics”tycho metrics backfill --timezone Asia/Jakarta --jsontycho metrics query \ --from 2026-08-01 \ --to 2026-08-16 \ --timezone Asia/Jakartatycho metrics query --server vps --from 2026-08-01 --to 2026-08-16 --timezone UTC --jsonThe range starts at --from and ends before --to. Offset-free boundaries use the named IANA timezone; values with Z or an explicit offset are absolute. Query filters accept comma-separated --group, --project, --agent, --harness, --model, and --status values.
Tycho normalizes finalized managed runs and native sessions across harnesses. Missing telemetry, session baselines, models, or prices remain unknown rather than becoming zero; costs are estimates, not invoices. Agent and project archives mark matching records as archived without moving them out of the global query path.
Backfill is best-effort and idempotent. Use --durable-only to read active and archived manifests without inspecting legacy raw telemetry:
tycho metrics backfill --durable-only --jsonWhen legacy run headers have no offset, pass --timezone. Repeating a completed backfill leaves the same stable records unchanged.