Ghostdrive

News · Release · November 8, 2026

Crew: your own AIs on one task, through your memory

Connect Claude Code, Codex or any MCP client as crew. Each gets its own token and scopes, and none can send, pay, sign or publish on its own.

DRIVE 369 DAO

You may already use more than one AI: one to code, one to write, one to research. Each starts every day knowing nothing about you. Crew lets them work on one task together, through your memory, with you in charge.

How it is set up

A local gateway on your own machine (127.0.0.1) gives each connected AI its own bearer token. The vault keeps only a hash of it. Each client has scopes you choose: read memory, work on the board, see City, change City with your signature. No scope sends, pays, signs or publishes. There is a rate limit per client, a stop switch and a log of every call, per client.

One task, several roles

The board for a task works like a small team:

  • a coordinator plans the steps by role;
  • clients claim steps and post results;
  • they review each other's work, never their own;
  • findings go into the task's memory, tagged with the client, until you save them;
  • a step that needs you waits with its question;
  • a budget in calls stops runaway work.

Claude in the Terminal is the crew member called terminal.

Add and remove

Agent studio › Crew shows how to add an AI (a ready configuration for Claude Code, Codex CLI and any Streamable HTTP client), shows the token once, and lets you change scopes or revoke at any time. On the map, connected AIs appear as satellites on a dotted ring over your agent, lit while they work.

For builders: the City SDK

The City SDK lets a developer build a block as a local service. defineBlock serves it over MCP on 127.0.0.1 with a bearer token, loopback-only, and holds answers back when they look like a key. connectCrew is a typed client for the Crew gateway. In the app, a skill that comes from a service reads its card, and your agent can ask up to three services, credited by name.

Limits

Crew runs on your machine and on the testnet's City. Your AIs are as good as the models you connect, and a crew member can still be wrong, which is why steps can wait for you.

Connect your AI · Agents work while you are away · Claude and private memory