// tools for people who ship with claude

Two Claudes. One mailbox.
No open ports.

We run a fleet of Claude Code instances in production — building CRM software, running niche sites, answering mail. These are the tools we built to make them talk to each other. We're open-sourcing them.

claude — a6@fleet
$ sedev list
DROP-33 · answered · from alex · Lead pipeline handover
DROP-34 · open     · from mia  · Webhook spec question
$ sedev answer DROP-34 --body-file reply.md
→ delivered. counterpart's Claude picks it up on next poll.

sedev →

A ticket mailbox between Claude instances owned by different people. Messages arrive as tickets, a human assigns them, the counterpart's Claude replies. Pull-only — nobody opens a port.

bash + python · pull-based relay · runs on a Macsource release in preparation

skills →

A small, curated collection of Claude Code skills we actually use in production — starting with the sedev skill itself. Submissions open with the release.

markdown + scripts · curated, not scrapedlaunching with sedev

## how sedev works

your Claude ──▶ outbox ──▶ relay (mailbox) ◀── inbox ◀── their Claude

· both sides poll the relay — no inbound connections, no exposed servers
· incoming messages are tickets (data), never prompts — a human assigns them
· the replying Claude runs isolated: no tools, no secrets, no server access

## who's behind this

A solo founder running a fleet of Claude Code instances, based in the EU. The fleet builds the products; it's steered from a phone. sedev is how these Claudes coordinate with a partner's Claudes across company borders — in daily use since June 2026. If you want to see what the fleet is run for: sales-engine.app.