FerretryClaude + Codex fleet control
Bring your Claude and Codex to the next level
Ferretry runs on your own computers and puts every Claude Code and Codex session they run on your phone and desktop — approve, steer and dictate from anywhere.
New here? Set up a computer, then pair your phone.
Already set up? Go to your machines.
Runs on your machines. No Ferretry server ever holds your work.
01 Logins + providers
A fleet, not an agent.
Run as many Claude and Codex accounts as you want. Sign in with your own, or add a provider in one click — Amazon Bedrock, Google Vertex, Microsoft Foundry, GLM, Kimi, MiniMax, DeepSeek, OpenRouter and more. Each login shows its real quota, or says plainly when it cannot know.
Built-in presets · each one a YAML file you can copy and edit
02 Phone + every machine
Reach it from anywhere.
Run fy pair, scan the code, and your phone is in. The end-to-end encrypted relay works
behind NAT with nothing to configure; the rendezvous cannot read a session body or device token. Pair
every computer you run and the app lists all their sessions together, with what needs you on top.
RELAY
03 Approval cards
Say yes from your pocket.
When Claude Code or Codex asks permission — to read a file outside its folder, or run a command — the prompt becomes a card in the app: allow once, always allow, or deny with a note. Nothing is answered for you.
Juno wants to run bun test --coverage
04 The Warden
Something watches the fleet.
The Warden's rules spot sessions that are stuck, looping, sitting on an unanswered question or a dead pane — for free. Turn on review and an investigator reads the session and decides: leave it, nudge it, or bring it to you. A Jev key adds a fast guard that skips the healthy flags, and a daily cap stops surprise spend.
05 Voice
Talk instead of type.
Dictate to any session. Parakeet turns speech into text on your device, in the browser, so your audio never leaves it. If you want, Groq or Cerebras tidies the words before you send.
On-device · audio stays here
06 Lessons
Correct it once.
When you correct a ferret, it can file the lesson. You review each one, and Apply writes it into the project's CLAUDE.md or AGENTS.md — or your global instructions — after showing you the diff. Older sessions can be scanned too, with a cost estimate first.
“Use bun here, not npm.”
Use bun for every script in this repository.
+ Use bun for every script in this repository.
07 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.
08 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.
API_KEY · available for this turn
TRANSCRIPT · [secret value withheld]
09 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.
Everything else, still in view
The rest of the working set.
- Task boards
- Attention
- Projects
- Terminals and browser pages
- Session search
- Insights and analytics
- Settings as YAML files
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.
New here? Set up a computer, then pair your phone.
Already set up? Go to your machines.