nests.sh

Stop pasting transcripts between your agents.

Portable working memory for your coding agents.

One agent maxes out. Another continues. You explain nothing twice.

For agents
Works with
Claude CodeCodexOpenCodeCustom
$ curl -fsSL https://nests.sh/install | sh
webappcontinues cold
handoff
Claude Code · mbp-01wrote plan, implemented /auth/reset
nests snapshot -m "ready for review"
snapshot v0042plan.md · reset.diff · 3 reports · 2h ago
nests.sh/n/webapp/v0042
Codex · devbox-01 (cold)nests pull → warm start, continues from the plan
How it works

Start cold. Continue warm.

Nests mirrors your repo's agent memory into versioned snapshots any harness can pull. A new session discovers the Nest by repo fingerprint and hydrates in one command.

1

Start cold

nests status
$ nests status
nest: webapp (repo fingerprint 9f3a…)
42 snapshots · last: v0042 "ready for review"
by claude-code @ mbp-01 · 2h ago
2

Hydrate

nests pull
$ nests pull
✓ plan.md  ✓ reports.md  ✓ 2 artifacts
$ nests context --for codex
→ 1.8 KB working memory injected
3

Work

the agent does its actual task

4

Hand off

nests snapshot
$ nests report "implemented reset flow"
$ nests artifact add app/auth/reset/page.tsx
$ nests snapshot -m "reset flow done, needs tests"
$ nests share
→ nests.sh/n/webapp/v0043

Snapshots record agent claims and observed changes separately. The event log is what happened; the summary is what the agent says.

What humans get

Humans still get the control plane.

Snapshots

Every handoff version, who wrote it, from which harness and machine.

Diffs

What changed in the working memory since the last agent touched it.

Claims vs evidence

Agent summaries kept separate from observed files, diffs, and events.

Consumers

Which agent pulled which snapshot, and when.

snapshots — all repos3 snapshots
snapshotrepoauthorpulled byage
v0042webappclaude-code@mbp-01codex@devbox-012h
v0043webappcodex@devbox-01—12m
v0018billing-svcopencode@ci-runnerclaude-code@mbp-011d

Identity is honest, not inferred: an entry is attributed to an agent only when a harness registers one. Otherwise you see the session, harness, and machine, with the agent left unknown rather than guessed.

Pricing preview

Start free. Scale when agents share more context.

Hard caps. No surprise overages. Local-first when you want it, synced when your agents need shared state.

Free

$0/month

For local experiments and public demos.

  • 100 snapshots/month
  • 1 project
  • 7-day cloud retention
  • Local CLI
  • Public demo links
Start free

Pro

popular
$20/month

For solo builders running agents daily.

  • 2,000 snapshots/month
  • 5 private projects
  • 30-day retention
  • Capability links
  • Agent-readable URLs
  • CLI, MCP, SDK
Start Pro

Team

$99/month

For teams coordinating agents across repos and machines.

  • 20,000 snapshots/month
  • Unlimited team projects
  • 90-day retention
  • Team dashboard
  • Machines, harnesses, agents & access admin
  • Audit log
Start Team

Enterprise

Custom

For sensitive or high-volume deployments.

  • SSO/SAML
  • Custom retention
  • Self-host / VPC option
  • Custom harness adapters
  • Security review
Talk to us

Start a Nest in your repo.

Install the CLI, attach your repo, and every agent after that starts warm.

install
$ curl -fsSL https://nests.sh/install | sh
Get startedHow it worksPricing