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

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

Durable Object migrations

Keep storage identity stable while the file tree and class names evolve.

The lockfile is production history

.ayjnt/migrations.json is generated but committed. It records append-only Durable Object migrations so every developer and deployment agrees on what already exists.

Run ayjnt migrate to preview, then ayjnt build to stage an intentional change.

Renames and deletion

Give long-lived agents a stable exported agentId before renaming their folder or class. Ayjnt can then preserve storage identity across the rename.

Removing an identity can produce a destructive class deletion. Treat migration diffs like database schema changes and review them before deploy.