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

CLI

ayjnt deploy

Build and deploy the agent runtime to Cloudflare with migration safety checks.

Usage

example

ayjnt deploy [options]

--cwd <path>  project root
--force       skip git safety checks
-h, --help    show command help

# additional flags go to wrangler deploy
ayjnt deploy --env production

Preflight

By default Ayjnt requires a clean tree, a branch that is synchronized with its origin, and a committed migration lockfile. This prevents two deploys from creating divergent append-only Durable Object histories.

--force bypasses git coordination, not runtime constraints. Projects with required Bun host tools cannot deploy because Cloudflare has no host process.