Documentation menu

Start here

Introduction Getting started Write an agent Project anatomy

Understand Ayjnt

Harness engineering Two runtimes Human interfaces How agents work Host bridge

Agent capabilities

Callable methods State & SQLite Sessions & memory Scheduling Workflows Durable execution Inter-agent RPC Sub-agents Tools WebAssembly modules

Interfaces & integrations

Browser client Routing & middleware Voice Browser tools MCP Email Observability

CLI

Command overview new dev run build compile migrate deploy

API reference

Agent AgentClient Workflow classes Local & cloud Migrations Examples

Documentation

Observability

Make state changes, tool calls, scheduled work, and human decisions inspectable.

Observe 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