Designed for people in the loop

Build agents
people can work with.

Ayjnt is an agent harness framework for building capable agents with a browser interface, a terminal interface, and a safe path to the host.

bunx ayjnt new my-agent
browser
localhost:8787/code/demo
Agent is workingReading src/runtime/tools.ts
ready when you are
Ayjnt mascot
terminal fix the failing bridge test 3 files updated
you
Powered by Bun workerd local by default · cloud when you want it
Why a harness?

Intelligence is only
part of the system.

A model can reason. A harness makes that reasoning useful: it gives the agent tools, context, memory, boundaries, observability, and a place for people to step in.

01

Give it context

State, history, files, and the right information at the right moment.

02

Give it capabilities

Tools that run near the agent or cross the bridge to the host.

03

Give it boundaries

Isolation, explicit permissions, and human approval for meaningful actions.

04

Keep people present

A useful interface for directing, inspecting, and collaborating with the agent.

Learn about harness engineering
Architecture

The right runtime
for each kind of work.

Isolation where agents reason. Native capability where work touches the machine. A typed, permission-aware bridge between them.

Human You choose the interface
app.tsx browser cli.ts terminal
01
Agent runtime

Safe, stateful, instant.

Agents run in workerd V8 isolates, with durable state, scheduling, workflows, and agent-to-agent RPC.

workerdisolatedeployable
typed bridge tools cross with explicit permissions
02
Host runtime

Close to the machine.

Host actions run in Bun, where agents can work with files, shells, databases, processes, and local connectors.

Bunlocalpermissioned
Human You choose the interface
app.tsx browser cli.ts terminal
requests
01
Agent runtime · workerd

Safe, stateful, instant.

Agents reason in isolated V8 environments with durable state, scheduling, workflows, and agent-to-agent RPC.

isolatedeployable
typed bridgetools cross with explicit permissions
02
Host runtime · Bun

Close to the machine.

Host actions work with files, shells, databases, processes, and local connectors.

localpermissioned
Human interfaces

Every agent gets
a front door.

The interface lives beside the agent, not in a separate product. Create the surface that fits the moment—or provide both.

Browserapp.tsx

Typed, realtime React UI co-located with the agent it controls.

bridge tests2,814 tokens

Find the race in the host bridge and fix it.

AY

I found a pending request that can outlive its connection. I’m adding cancellation and a regression test.

edit src/core/hostBridge.ts
Terminalcli.ts

Full-screen, scriptable, and close to the files and tools developers already use.

ayjnt-code~/projects/ayjnt

you clean up the docs and examples

agent I’ll inventory the current site first.

Search examples/** 24 results

Read docs-astro/src/pages/index.astro

agent There are three overlapping scheduling examples. I’ll consolidate them into one practical brief agent.

Examples

Six real starting points.
No catalog filler.

Each example teaches a distinct harness pattern and includes a human interface you can run, inspect, and adapt.

Explore all examples
Start building

From idea to running agent
in four commands.

Start locally. Add a browser UI, a terminal UI, or both. Deploy the agent runtime only when you need the cloud.

Read the quickstart
terminal
bunx ayjnt new my-agent
cd my-agent
bun install
bun run dev