Commands
Commands
Install
deno run -A jsr:@fathym/fai/install
Installs fai globally. Deno is required. After install, fai is available on your PATH.
fai
Start your AI workbench. Opens a session where your AI remembers everything from past sessions and helps you build.
fai
Flags:
| Flag | Description |
|---|---|
--dry-run | Preview what your workbench will do without making changes |
--continue | Continue your last AI conversation |
--rc | Start a remote session |
--mcp | Start fai as an MCP server (stdio mode) |
--mcp=<port> | Start MCP server on a specific TCP port |
--preview | Launch MCP Inspector to explore all active tools |
--share | Open a public relay tunnel - share your workbench remotely |
--sessionId <id> | Skip the session picker and open a specific session |
--agent <name> | Pre-select which AI agent opens with your session |
fai detect
Scan for AI tools, local models, and synthesis providers installed on your system.
fai detect
fai detect --models
fai detect --agents
fai detect --verify
| Flag | Description |
|---|---|
--models | Filter results to models only |
--agents | Filter results to agents only |
--verify | Verify each detected item is reachable |
fai orient
Orient an AI agent with your project context. Generates the agent's context file from your current workbench state.
fai orient
fai orient [content]
| Flag | Description |
|---|---|
--source | Source type for orientation content |
--file | File input for orientation |
--mode | Orientation mode |
--fileSuffix | File suffix to use for generated context file |
fai status
Show the current state of your workbench.
fai status
fai status --paths
| Flag | Description |
|---|---|
--paths | Include file paths in the status output |
fai synthesize
Configure your synthesis provider - the AI model that distills session captures into project knowledge.
fai synthesize
fai synthesize --non-interactive
fai synthesize --agent <name>
| Flag | Description |
|---|---|
--non-interactive | Auto-configure without prompts |
--agent | Pre-select the synthesis agent |
Supported providers: ollama, lmstudio, localai, openrouter, groq, openai, claude-code, capture-only
Note:
ANTHROPIC_API_KEYis not supported — the Anthropic API is not OpenAI-compatible. To use Claude models, setOPENROUTER_API_KEYinstead.
See Local Models → for setup with Ollama, LM Studio, and cloud API keys.
fai mcp generate
Generate .md skill files from the fai MCP server's prompts.
fai mcp generate
fai mcp generate --output <dir>
| Flag | Description |
|---|---|
--output | Directory to write skill files into (default: .claude/commands) |
--server | MCP server binary to connect to (default: current fai binary) |
Connects to fai --mcp=stdio, lists all prompts, and writes one .md file per
prompt. Prompt / separators map to subdirectories: holonic/explain →
<output>/holonic/explain.md. Claude Code reads .claude/commands/ as slash
commands.
This runs automatically in the background on each fai session start for
Claude Code.
fai petname
Manage memorable names for sessions.
fai petname
fai petname [name] [meaning]
| Flag | Description |
|---|---|
--scope | Scope for the petname |
--list | List all petnames |
--remove | Remove a petname |
fai sessions
Work with session history.
fai sessions list
fai sessions list --status <status>
fai sessions list --json
fai sessions [id] capture [content]
fai sessions [id] compound
fai sessions [id] watch
sessions list flags:
| Flag | Description |
|---|---|
--status | Filter by session status (active, sealed, archived) |
--json | Output as JSON |
sessions [id] capture flags:
| Flag | Description |
|---|---|
--file | File to capture |
--mode | Capture mode |
--fileSuffix | File suffix for capture |
--source | Source type |
--agentType | Agent type context |
fai uninstall
Remove fai from your system.
fai uninstall
fai workstreams compact
Compact workstream history.
fai workstreams compact
fai workstreams compact --source <path>
| Flag | Description |
|---|---|
--source | Source path for compaction |
Coming soon
As fai evolves, new commands appear - not from a release schedule, but from how you and the community work. When patterns become common enough, they become commands.
Even the CLI grows with you.