Documentation menu
Start here
IntroductionGetting startedWrite an agentProject anatomyUnderstand Ayjnt
Harness engineeringTwo runtimesHuman interfacesHow agents workHost bridgeAgent capabilities
Callable methodsState & SQLiteSessions & memorySchedulingWorkflowsDurable executionInter-agent RPCSub-agentsToolsInterfaces & integrations
Browser clientRouting & middlewareVoiceBrowser toolsMCPEmailObservabilityCLI
Command overviewnewdevrunbuildcompilemigratedeployAPI reference
AgentAgentClientWorkflow classesLocal & cloudMigrationsExamplesCLI command reference
The Ayjnt CLI discovers the file tree, generates runtime wiring, and runs the same harness locally or in the cloud.
Commands
| Command | Purpose |
|---|---|
| new | Scaffold a project with a browser UI by default |
| dev | Generate files, watch changes, run Wrangler dev |
| run | Boot Ayjnt’s Bun + workerd local runtime and cli.ts |
| build | Generate .ayjnt without starting or deploying |
| compile | Package the app, Bun, and workerd into an executable |
| migrate | Preview the Durable Object migration diff |
| deploy | Run safety checks, build, and deploy with Wrangler |
Shared conventions
dev, build, migrate, and deploy accept --cwd <path>. Unknown flags for Wrangler-backed commands are forwarded, so ayjnt dev --port 8788 works.
Set AYJNT_DEBUG=1 to include stack traces when a command fails.