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 & cloudMigrationsExamplesLocal and cloud runtime
Run the same agent classes locally in workerd, package them with Bun, or deploy them to Cloudflare.
Three ways to run
| Mode | Agent runtime | Bun host | Best for |
|---|---|---|---|
| ayjnt dev | Wrangler workerd | No | Web UI and Cloudflare bindings |
| ayjnt run / compiled | Local workerd | Yes | CLI, host tools, local products |
| ayjnt deploy | Cloudflare | No | Globally available durable agents |
Design portable capabilities
Agent code, state, schedules, workflows, and tools.ts can run locally or deployed. cli.ts and tools.host.ts are local-product capabilities powered by Bun.
If a host tool is optional in cloud mode, mark it with the documented optional-deploy marker and make the agent behave sensibly when the tool is absent.