Open autonomous delivery engine / release candidate

Sworn is the team that carries it.

Baton defines the handoff. Sworn runs the team: selected agents and models carrying approved work through planning, design review, implementation, fresh verification, and the exact merge that passed.

Install Sworn ↓ Read the release notes ↗

Baton graph / Sworn timing wall / saved run

One approved route. A team in motion.

Passed
04 / 07
Active
02 tracks
Elapsed
42:18
Baton / approved delivery graph approved plan · rev 03
Plan Customer operations inbox Exact revision approved
T1 / contract 2 / 2 passed
S01 S02 PASS
T2 / delivery 1 / 3 passed
S03 S04 S05
T3 / interface 1 / 2 passed
S06 T1 → S07 BUILD
Assembly Fresh final check Waits for every exact track head
Merge Exact checked result No green before Git agrees

01 / The team

Five carry the Baton.
One keeps the relay moving.

Baton’s five responsibilities hold delivery authority. Sworn’s orchestrator is operational: it reads the turn, keeps context where that is safe, and routes what happens next. It is not a sixth role.

  1. 01

    Planner

    Frames the route

    Proposes the work, its order, its checks, and the independent tracks that may move together.

    approved plan
  2. 02

    Implementer

    Designs and builds

    Explains the approach first, receives the Captain’s decision, then writes and checks the change.

    exact candidate
  3. 03

    Captain

    Challenges the design

    Reviews the approach before implementation continues and returns PROCEED, REVISE, or ESCALATE.

    design decision
  4. 04

    Verifier

    Checks independently

    Starts fresh and read-only. It tests the real candidate against the approved work, not the builder’s story.

    PASS / FAIL / BLOCKED
  5. 05

    Merge

    Finishes the exchange

    Rechecks the candidate and target, then combines only the exact result that received PASS.

    observed Git result

Sworn / Orchestrator

It interprets the turn without inventing the outcome.

If an agent asks a question, answers in an unexpected format, or hits an operational problem, Sworn may answer from recorded facts and resume it, ask the Captain for guidance, retry the operation, or pause only that track for a person.

It cannot approve a plan, issue a Captain decision, record a Verifier verdict, change scope, or authorise Merge.

02 / Context

Keep the useful thread.
Start the check clean.

Conversation state saves time. Baton records, not conversation memory, decide what is allowed to happen.

A

Build continuity

The Implementer can wait while the Captain reviews.

In one live process, Sworn holds the Implementer’s thread, runs a separate Captain review, then returns the exact decision to that Implementer.

B

Independent first check

The first Verifier always starts fresh and read-only.

It receives the approved work and real candidate without the Implementer’s conversation. A confident build report is not verification.

C

Direct repair

After a real FAIL, the same Verifier thread may check the repair.

Its findings stay useful, but every repaired candidate receives a complete read-only check. Stale context falls back to fresh; final assembly verification is always fresh.

03 / Drivers and models

One driver layer.
The right model for each role.

A driver teaches Sworn how to talk to a runner. Every role uses that same connection layer and names its own profile and model. Sworn does not create a separate driver for each role, choose a default, switch API types, or silently fall back.

Sworn does not sell or manage access to AI models.

Connection Surface Status
Codex CLI Native agentic CLI Explicit choice
Claude Code CLI Native agentic CLI Explicit choice
OpenAI Responses Native Responses API Explicit choice
OpenAI-compatible Chat Completions Explicit choice
DeepSeek Provider API Explicit choice
Gemini Provider API Explicit choice
Bedrock Runtime Converse Explicit choice
Bedrock Mantle OpenAI-compatible Chat Explicit choice

04 / Operate and observe

See the same saved run.
Choose the view you need.

Terminal, JSON, and the local browser board show the same saved run. A dashboard can show activity, but it cannot create a Baton approval or verdict.

Terminalsworn board
Machinesworn status --json
Browsersworn serve

Local evaluation

Measure the loop, not just the final answer.

Sworn records attempts, retries, elapsed time, reported token and cost usage, recovery, session continuation, turn routing, and available quality evidence.

Opt-in OpenTelemetry

Send traces and metrics over OTLP/HTTP.

Export is optional and can only observe. Prompts, responses, reasoning, session IDs, credentials, and source content stay out. A slow or unavailable endpoint cannot affect delivery.

Safe intervention

Pause one part without losing the run.

Pause, resume, cancel, take over, retry exact stopped work, or answer a saved question. Each command names the current saved version, so an old screen cannot change a newer run.

Current commands

Tell the RC exactly what to use.

You supply the approved Baton records, manifest, driver configuration, credentials, and private journal path. Sworn does not yet generate or choose them. 

$ sworn version --json

$ sworn driver inspect --config /abs/drivers.json \
    --profile openai --model YOUR_MODEL --json

$ sworn run --manifest /abs/run.json \
    --journal /abs/run.sqlite --config /abs/drivers.json

$ sworn board --run RUN_ID --journal /abs/run.sqlite
$ sworn serve --run RUN_ID --journal /abs/run.sqlite \
    --config /abs/drivers.json

05 / Open and hosted

The engine stays open.
Hosted sells operation.

Run the complete local engine and board on your own systems under MIT. The hosted service adds the work of operating teams and fleets; it does not withhold the interface or resell inference.

Local / MIT

Your repository remains the authority.

  • Complete engine and responsive local board on supported Linux hosts
  • Your credentials, providers, models, and OTel endpoint
  • Generic webhook and secure self-hosting boundary
  • Source, prompts, diffs, evidence, and raw logs local by default
Read the source ↗
Hosted / Planned

Optional operation for teams and fleets.

  • Secure node enrolment and managed identity
  • Fleet views, notifications, and audit retention
  • Upgrades, availability, and support
  • Hosted requests return to your local Sworn engine
Follow public development ↗

Open source / Available now

Put the team
behind the handoff.

Sworn is public under MIT. Get the current release candidate, bring the providers and models you already use, and run the engine on a supported Linux host you control.

Download v1.0.0-rc.1 ↗ Install guide ↗

Linux x86_64 / Homebrew

brew install --cask swornagent/tap/sworn

sworn version --json