Reference
CLI
bin/kevin runs the MCP server's logic from a plain terminal, for cron jobs, scripts, and one-shots.
export PATH="$HOME/Developer/agent-kevin/bin:$PATH" # a clone; a marketplace install lives in your host's plugin cache
kevin helpkevin help prints every group, command, flag, env var, and example. The major groups:
| Group | What it does |
|---|---|
kevin task <subcmd> | Query, get, create, update, close, thread, scan tasks |
kevin capture | Feed the inbox or the feedback log. See Capture |
kevin dashboard | Rebuild projects/TASKS.md and dashboard.html |
kevin knowledge lint [--fix] | Structural wiki check: broken links, orphans, missing backlinks, invalid frontmatter. --fix rewrites links and inserts backlinks |
kevin compile <subcmd> | status (queue), next (peek), write <id> (mark complete). Synthesis itself needs a session |
kevin prune | Delete daily memory older than the retention window (14 days) |
kevin links | Rewrite bare task ids and shorthand into wikilinks across the wiki |
kevin seed <subcmd> | scan, export, import <zip> [--dry-run] [--overwrite] |
kevin worktree <repo> --branch= · worktree list · worktree remove | Create and bootstrap a sibling worktree; audit every worktree with a verdict; remove one safely |
kevin database <subcmd> | list, schema, query, fork against the configured Postgres connections |
kevin session-start · session-capture · guard | The hook entry points |
kevin ping | Print resolved paths and timezone |
kevin task query --status=active
kevin task create --project=blog-dev --title="Draft launch post" --priority=P1 --type=task
kevin task thread bd-004 --message="Outline drafted" --type=info
kevin knowledge lint --fix
kevin compile statusRunning outside a session
The CLI resolves its home from the current directory, and a plain terminal has no launch directory to fall back on. Run it from inside the home, or point it at one:
KEVIN_HOME=~/Documents/Agents/Kevin kevin task query --status=activeAnywhere else it refuses and tells you what it resolved, rather than scaffolding a knowledge/ tree into whatever repo you were standing in.
Compile still needs a session
The compile pipeline returns prompts, not synthesized output, so full evolution runs through knowledge-compile or sync inside a session. The CLI prepares and inspects; it does not think.