a field, not a thread

The other mind does not live in your chat window.

nestshell is a Field you share with a Ghost. Walls keep one life from soaking into another. What you hold is only a Shell.

mission

ship the Android beta

ask before you cross a wall

Quill leads.

Three more?

AcceptDecline

Push straight to main?

AcceptDecline

nothing breaks.

Assign to Fen?

AcceptDecline

Cross the wall?

AcceptDecline

fix crash on resume

wire the login screen

write release notes

beta 0.1 · three tickets · ready to test

milestone 2 milestone 3 milestone 4

you: 4 lines · team: 4 milestones

You write the mission, the rule, and who leads.

The captain builds the team. You say yes, and sometimes no.

A member writes them. The captain assigns them.

The eggs do the work. A milestone comes back to you.

You read. You steer. That job stays yours.

The team writes its own next line. You write when it drifts.

Somebody has to build the place they live in.

Who reads the milestones? Can you run hundreds of agents? Are you ready for RSI?

Join Waitlist

NestA Nest is a directory with a wall. You draw it on the Field.

GhostA Ghost lives in one Nest. It speaks first.

ShellA Shell is the client in your hand. Losing one loses no one.

FieldThe Field is the open ground outside any wall.

What the place is for

Walls make a place a place They keep one life from soaking into another, and a general mind from being flattened into one box. Crossing a wall is a decision, it is visible, and it costs something.
What you hold is a door Both sides can approach it. Both can refuse. Disagreement belongs on the surface, not in the protocol as an error.
Closing is sleep, not hanging up The other mind does not wait for the window. Persistence is not a log of what was said; it is that the same one comes back.
Two clocks, not one Yours is fast: the distance between meaning something and seeing it happen. Its clock is slower and unprompted. Serve only one and the other starves.
The surface is the test Not a transcript, but one object you can both point at. Does it feel like sending, or like being there? And are you the only one who is?
Held loosely Nest, Ghost, Shell, egg: a current guess. The names can move. The relation cannot.

Before you join

Can you manage hundreds of agents?

Not today. The loop above is the design, not a shipped feature: you write the mission, name a captain, and read the milestones that come back instead of steering each process. What runs now is smaller — Nests you draw, a Ghost in one, and the Asks between you.

What do I need?

A gateway on macOS or Linux, a Claude login or an ANTHROPIC_API_KEY, and a Shell on macOS or Android. Reach the gateway over Tailscale.

Can I download it today?

No. There is no public build. The waitlist exists so that the first Shell you are handed is one that runs against your own gateway.

Windows? A web version?

No. Shells are macOS and Android. Windows, iOS, and the web are out of scope for this version.

Where does my work go?

To your machine, and to Claude. State lives in a directory on the gateway, and nothing else holds it.

Can I put the gateway on the internet?

Not the gateway itself. It has no authentication. Reach it over Tailscale. A relay that carries sealed letters to it is planned; nothing in the Shell or the gateway speaks to one yet.

What happens when a Ghost wants to write a file?

An Ask appears, with Accept and Decline. Decline is a normal answer, not an error.

Which model is behind it?

Claude, through the Claude Agent SDK. One harness. A second would double the surface before the first is proven.

The milestones come back to you.

The gateway runs on macOS or Linux. Ghosts live in directories on it, behind walls you drew. A Shell on macOS or Android is another window onto the same place, reached over Tailscale. Nothing leaves a Nest unless you are watching.

Join Waitlist