Halyard
Running workflow · ledgerline · main · 7 on this Mac, 5 on Anthropic

You dream it. We build it together.

Halyard is the frontier agentic coding harness: a local-first runtime on a Rust kernel. Run one agent or a whole fleet unattended for minutes or hours, with a receipt for every step. You set the rules and the risk you'll manage. You dream it up, and we build it together.

Rust kernel Local-first One agent or a fleet Your rules, your limits
Workflow
Audit approval and tool call sites
Sheet
H-0001
Spokes · hubs
12 · 3 hubs
Progress
Waiting at the gate
Seed
hrb24
Principles

What a harness with its own kernel gives you.

Runs at the risk you set

Work below your line runs on its own, for minutes or hours. Steps above it come to your phone, wherever you are. Answer there and the work keeps going.

Approved from iPhone · agent resumed

A receipt for every step

The kernel logs every tool call and checkpoints every action, so you can review, revert, fork or replay the work. Steps that reach outside the workspace are marked as ones Halyard can't undo.

Restored app.ts to how it was before this action

Sized before it runs

Big jobs are surveyed first, and the agent count and estimated cost show at a gate before anything runs.

12 agents across 3 machines · estimated $4.10 · waiting for you
Compared

How Halyard differs from the tools you already run.

Claude Code and the Codex app are good agents. Conductor and Herdr run several of them side by side. Halyard is the layer underneath: its own kernel decides what runs without you, sandboxes it, and keeps the receipt.

HalyardClaude CodeCodex appConductorHerdr
What it isA runtime with its own Rust kernelAnthropic's coding agentOpenAI's coding agentA Mac app that runs other agents side by sideAn open-source runtime that hosts other agents' CLIs
Runs onmacOS 14+, Windows, LinuxmacOS, Linux, WSL, WindowsmacOS, Windows, LinuxMacmacOS (Apple silicon), Linux, Windows
Several agents at onceOne agent or a fleet, across this Mac*, Anthropic and OpenAISubagents, background sessions, cloud sessionsSubagents, a worktree per chat, cloud tasksA workspace and branch per taskAgents in terminal panes, on any machine over SSH
What runs without askingA risk level you manage; the kernel enforces it at each stepPermission modes with allow, ask and deny rulesPermission modes, including “Approve for me”—Left to each agent's CLI
SandboxEvery agent, alwaysOS sandbox for shell commands, off by defaultOS sandbox with read-only and workspace-write modes—Through wrappers or a Vercel Sandbox plugin
UndoA checkpoint for every action, not just every turn; actions it can't undo are markedCheckpoints per prompt; shell changes not covered———
ReceiptsAn audit log of every tool call, on your machinesOpenTelemetry events, opt-inAudit events for enterprise plans——
ModelsAny model with your own keys, or via local modelsClaude, via Anthropic or your cloud providerOpenAI modelsWhichever agent you run in itWhichever of 20+ agent CLIs you run
Sized before it runsAgent count and estimated cost at a gate————
From your phoneHalyard app on iPhone and AndroidRemote Control and the Claude appChatGPT mobile app—iPhone, iPad and Android apps

— means the vendor's own pages don't mention it, not that the feature is missing. Checked against their docs in November 2026.
* Add additional machines as runners.

Plans and Approvals

The agent works. When a step is risky, it stops and asks you.

This run was generated for you from the page's seed. The plan streams in, then the kernel holds the risky step until you decide. Approve it, deny it, or stop the agent. Afterwards you can revert the whole turn.

Agents / Add idempotency keys to POST /v1/orders
Plan · 4 of 6
Now
Waiting on you to apply the migration to staging
Next
Hand the change over for review
If you stop · estimate
4 files edited in this workspace, each with a checkpoint
Plan
  1. Read the orders handler and middleware
  2. Add migration 0042_idempotency_keys
  3. Implement the middleware and Postgres store
  4. Run the API tests
  5. Apply the migration to staging Needs you
  6. Hand the change over for review
Agents work in this folder on your Mac. This run uses no cloud models.
Kernel

One kernel on your machine. The apps are windows onto it.

The kernel runs agents in a sandbox against your repositories, keeps a checkpoint for every action and writes the audit trail. The desktop and phone apps talk to it through its protocol, so either one can approve, deny or stop.

Asynchronous

Native apps on desktop and phone, talking to the same kernel.

Plan, watch and decide at your desk. When you step away, the app shows the same approvals and the same stop button.

Halyard for Mac showing a live plan five of six steps in, with the agent waiting on approval to run a migration on staging and an activity log of tool calls. Halyard for iPhone showing the same agent's live plan, five of six steps in and waiting on you to run the migration on staging.
Early access

Put Halyard on your machine before it ships.

We are letting in a small group of engineers who already run coding agents and want to see how far they can go.

  • macOS 14 or later on Apple Silicon or Intel, Windows and Linux
  • Bring your own model, or your own keys
  • Runs against your repositories, on your machine, with supervision from your phone
  • A direct line to the people building the kernel
Not ready to sign up? Read the docs The gateway on GitHub
Optional. It helps us pick the first cohort.