YouBothAgent▾
You — Business rules and flows you own. Read these yourself.
Both — Know the idea; your agent follows the details.
Agent — Conventions and references your agent follows. Look up as needed.














CLI Reference▾
AkanJS Reference▾akan code runs an AI coding agent in your terminal that already knows this workspace. Ask it to add a field and run the validation loop, with no editor, no MCP client setup, and no explaining the module conventions first..env, e.g. DEEPSEEK_API_KEY for the default model.akan code to start a session, or akan code "<prompt>" for one run.read · write · edit · ls · grep · find · bashplan_workflow · apply_workflow · run_validationakan mcp gives an editor's agent.akan-module · akan-store · akan-validate · …~/.akan/code/skills or .akan/code/skills.AGENTS.mdAGENTS.md sits in the context window, so the agent follows the conventions from the first turn.| Command | Agent runs in |
|---|---|
| ↳ What it is | |
| akan code | Your terminal |
| An agent of its own that already carries the tools and rules above. | |
| akan mcp | Your editor |
| A server that lets an editor's agent reach this workspace's tools. | |
| akan agent install | Your editor |
| Writes the rule files an editor's agent reads. | |
| Mode | When |
|---|---|
| ↳ What you get | |
| RPC | --rpc |
| Serves akan wire frames over stdio for another process to drive. | |
| Full-screen session | --interactive, or no prompt and no --json on a terminal |
| A chat you keep talking to. A prompt you pass becomes its first message. | |
| One run | Any other call with a prompt |
Runs the prompt to the end and prints each event. With --json, one JSON line per event. | |
--json, a missing prompt is an error. In a pipe or a CI step, always pass one: akan code "add a comment module".--json makes its output machine-readable.apps/<app>. Without it, the whole repo is in scope.<provider>/<id>. Default: deepseek/deepseek-flash; without its key, the first available.--interactive.local and web save sessions.<PROVIDER>_API_KEY in the workspace .env or your shell, e.g. DEEPSEEK_API_KEY.akan code --resume <id>..akan/code/sessions in the workspace. An id that is not there is an error..env, .env.*, secrets/, *.pem and *.key, whatever its allowlist.--profile. It decides which tools exist, whether writes wait for approval, where sessions are kept, and how much of the project sits in the window.read, ls, grep and find, no AGENTS.md, sessions in memory.local, but every file write waits for your approval.await holds the turn open until you answer. suspend ends the turn and reopens one with your answer, so it survives a process restart.review gets only the Akan tools that change nothing.web asks before write and edit only. bash never waits for approval.~/.akan/code/mcp.json is yours and .akan/code/mcp.json is the checkout's; on a shared name the workspace entry wins.--app is a real boundary. It moves the profile's root to apps/<app>, and file tools refuse any path outside it. That holds better than a prompt politely asking the agent to stay there.

.env is refused, but a shell can still reach any path. The real boundary is the container the pod profile runs in.