Start now ↗
Ferretry A control room for agent work

Claude + Codex fleet control

Bring your Claude and Codex to the next level

Ferretry turns the machines and accounts you already run into one private operating surface — so your agent work has a fleet behind it.

Start now

Runs on your machines. No Ferretry server ever holds your work.

02 Encrypted relay

Reach it from anywhere.

Your fleet on your machines, in your pocket. The end-to-end encrypted relay works behind NAT with nothing to configure; the rendezvous cannot read a session body or device token.

ENCRYPTED
RELAY

03 Peer sends

Your agents talk to each other.

Agents can hand work across the fleet. A peer send is attributed to the server-derived sender, not a name supplied in the request, so the receiving agent knows which teammate is speaking.

Teammate / research“I found the source path. Take the implementation.”
Teammate / build“On it. I will send the check when it is green.”
Teammate / research“The source coverage is ready.”

04 Quota + health

Never lose work to an exhausted account.

Quota probes know who is out. Health probes know who can actually complete a turn. On PATH, in credit, and working are three different questions — the warden moves work off a dying account.

claude-auto-a
codex-auto-b
claude-auto-c
WORK CONTINUES ON THE ACCOUNT WITH EVIDENCE IT CAN FINISH.

05 Private by architecture

Your machines. Your accounts. Your data.

No Ferretry server holds your work, ever. Claude Code and Codex keep using your accounts; Ferretry brings their running work into an operating surface you control.

FY

06 Pooled sessions

One history across every account.

Sessions are pooled per harness, so a conversation started under one account is there under another. Existing history migrates with a dry run first.

Account A / Claude

Start the research with the account that has room.

Dry run

Confirm what will move before the history changes hands.

Account B / Claude

Continue the same conversation from the shared harness history.

07 Transcript-safe secrets

Secrets your agents use and never leak.

Agents can use these; they never appear in your transcripts. That is the boundary: the agent gets what it needs to work, while the conversation record stays free of the value.

AGENT ACCESSTRANSCRIPT

API_KEY · available for this turn

TRANSCRIPT · [secret value withheld]

Used without being written into the record

Everything else, still in view

The rest of the working set.

  • Task boards
  • Attention
  • Projects
  • Terminals
  • Session search
  • Analytics
  • fy doctor

Your machines, amplified

Keep the harnesses. Gain the fleet.

Claude and Codex stay themselves. Ferretry gives their work a place to operate together.

Start now