Kelyra 0.1.2 is live on npm. Open Console
kelyra 
██╗  ██╗███████╗██╗  ██╗   ██╗██████╗  █████╗
██║ ██╔╝██╔════╝██║  ╚██╗ ██╔╝██╔══██╗██╔══██╗
█████╔╝ █████╗  ██║   ╚████╔╝ ██████╔╝███████║
██╔═██╗ ██╔══╝  ██║    ╚██╔╝  ██╔══██╗██╔══██║
██║  ██╗███████╗███████╗██║   ██║  ██║██║  ██║
╚═╝  ╚═╝╚══════╝╚══════╝╚═╝   ╚═╝  ╚═╝╚═╝  ╚═╝

Make every agent edit prove itself.

Kelyra is a local execution boundary for AI coding agents. It checks file actions against real disk state, records signed receipts, and keeps risky writes behind policy.

Open Console Protocol
kelyra -- ~/project

$ kelyra swd apply --stdin --json

✔ Verified: PATCH src/auth.ts

✔ Receipt saved: swd-20260526-8f1c2a

$ kelyra proof share swd-20260526-8f1c2a

Verification demo

The proof layer is the product.

Kelyra turns each model edit into a claim, compares it with the actual filesystem, and records the outcome for reviewers.

Normal edit

A matching file action leaves a receipt.

The agent proposes a PATCH, SWD checks the result on disk, and Kelyra saves the proof.

Claim
PATCH src/auth.ts
Check
intent and hash matched
Outcome
receipt created
── SWD Verification ──
✔ Verified: PATCH src/auth.ts
✔ Receipt: swd-20260526-8f1c2a
Tokens: 4,812 total via anthropic
Budget: 4,812/500k · 1/3 turns · ~$0.024

Mismatch

False claims are rejected.

If the agent declares a write that did not happen, Kelyra returns the actual state instead of accepting the transcript.

Claim
MODIFY README.md
Check
content hash drift
Outcome
correction turn
✖ Verification failed
Expected: 9b2d3c1a
Actual:   44f0aa91

Correction turn:
The file differs from your declared CONTENT_HASH.
Re-read README.md and submit a corrected FILE_ACTION.

Policy gate

Risky paths hit policy first.

Sensitive files and command surfaces are stopped or require explicit opt-in before writes happen.

Claim
CREATE .env
Check
sensitive path
Outcome
write blocked
{
  "ok": false,
  "rejected": [{
    "path": ".env",
    "risk": "block",
    "reason": "Sensitive file writes are blocked"
  }]
}

Entry points

Use the surface your workflow needs.

Kelyra can run the agent, learn repo rules, or sit behind another agent as the verified file-edit boundary.

Agent runner

Run one task or open chat

Call your configured provider through Kelyra and verify every file edit before it counts.

kelyra init
kelyra run "explain this repo"
Repo memory

Generate and load skills

Keep repository rules, review expectations, and risk surfaces active in every session.

kelyra learn
kelyra run --file TASK.md -s repo
External agents

Use Kelyra over MCP

Give MCP clients and external agents dry-runs, verified applies, rollback, and receipts.

kelyra mcp
swd_dry_run / swd_apply
Operator workflow

Diagnose, explain, and publish

Run readiness checks, explain CI failures, publish proof pages, and inspect receipt history.

kelyra doctor
kelyra ci explain

Proof first

Every accepted edit leaves evidence.

Kelyra snapshots the filesystem before and after model output, verifies declared actions, and exports proof reviewers can inspect without trusting a chat transcript.

01

Strict Write Discipline

Agents must declare file actions. Kelyra checks disk reality before accepting the result.

02

Signed Receipts

Each verified run records hashes, provider, branch, policy, and proof context.

03

Policy Gates

Teams can require signatures, block risky paths, and enforce receipt-backed changes in CI.

04

Shareable Proof

Portable bundles and static HTML pages expose file status, integrity, signatures, and diffs.

How it works

One path from intent to evidence.

1

Agent proposes actions

Use Kelyra chat/run, MCP, or external-agent JSON with declared file actions.

2

Boundary validates

Paths are constrained, sensitive files are checked, and project policy is loaded.

3

SWD verifies disk

The engine snapshots before and after state, hashes files, and rolls back failed writes.

4

Receipts keep record

Successful writes produce local receipts, proof bundles, share pages, and CI-verifiable records.

Proof-driven workspace SWD on · receipts ready
Fix the token rotation bug in src/auth.ts and prove the change.
I found the unsafe reuse path. I will patch the rotation flow, verify the write, and attach the receipt.
PATCH src/auth.ts
Status verified
Receipt swd-8f1c2a
Ask Kelyra to inspect, patch, or export proof...

Console surface

A command center for proof-driven work.

Kelyra Console brings proof chat, receipt review, source-backed research, and app workspaces into one operator surface.

Access model

Open core. Hosted command center.

Kelyra Core

Open-source CLI for local SWD verification, receipts, policy checks, proof sharing, diagnostics, and CI gates.

  • No wallet required
  • Bring your own provider key
  • Works with external agents
  • Explains CI failures locally

Kelyra Console

Browser workspace for proof chat, hosted jobs, quota-aware app tools, and receipt history.

  • Local bridge proof mode
  • Hosted proof history
  • Fresh/full quota tracking
Core Open protocol engine
Console Hosted chat + proof
Teams Policy, CI, attestations

Quick start

Run Kelyra locally first.

npm install -g kelyra
kelyra doctor
kelyra providers check
kelyra console