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 & cloudMigrationsExamplesObservability
Make state changes, tool calls, scheduled work, and human decisions inspectable.
Start from a fresh project
This guide is self-contained. Create an empty Ayjnt project, then replace the starter agent with the files shown below. Run commands from the new project directory unless a step says otherwise.
bunx ayjnt new try-observability --empty
cd try-observability
bun install
# remove agents/alive once you are ready to add the guide's filesObserve the harness, not only the model
The Agents SDK emits diagnostics-channel events and integrates with Cloudflare logs, metrics, and traces. Ayjnt’s browser and terminal surfaces should present the same execution record in a human-readable way.
- Agent identity, instance, and route
- Model request, provider, latency, and token usage
- Tool arguments, result summary, duration, and side-effect class
- Schedules, workflow steps, retries, queues, and fiber recovery
- Human approvals, edits, cancellations, and overrides
Run it and verify the result
Trigger one state update and one callable method, then confirm both event categories appear in the subscriber output.
bun run build
bun run dev
# the local app is now available at http://localhost:8787