AIReins

Let the agents run.Keep the reins.

Your AI workbench, on your own computer. Use Claude Code, Codex and Kimi Code from a browser on your desktop or phone.

View on GitHub Get started
Claude Code, Codex and Kimi Code converge through AR on an Approve button on your phone

One workbench for all three.

Keep the tools you already use. Bring the work into one place.

Your setup comes with you.

Official CLIs, existing logins. Your instructions, skills, hooks, MCP servers and plugins load as usual. Nothing to migrate.

The next move is yours.

Approve or deny tool calls, answer questions and interrupt a run. Everything waiting on you, across all sessions, is collected in one place.

Pick up where you left off.

Search, filter by folder and resume the native history of all three CLIs. Sessions stay in each CLI’s own history.

See the work as it happens.

Sessions together, approvals in view, sub-agents in a tree. Files and a multi-tab terminal are right at hand.

Desktop: sessions from three agents on the left, a Claude session with a pending approval in the middle, and the dispatch flow chart on the right showing Codex and Kimi runs live
The dispatch chart also shows runs from an external delegation tool when connected. Without one, it shows native sub-agents.

Step away. Stay in control.

Connect back over Tailscale. Approve a tool call, answer a question or browse your files, all from your phone.

Add it to your home screen to open it like an app. The remote terminal is off by default; enable it when you need it.

Three phone screens: the session list, a session with an approval card, and the terminal

Screenshots from a local instance running on demo data; the sessions and paths are made up.

Your browser. Your computer.

One Node process. The official CLIs. Your existing logins.

Six steps: open, your tailnet, one process, official CLIs, whole computer, your call

On the same computer, your browser connects directly to loopback. From another device, join your tailnet: Tailscale Serve forwards to AIReins’ remote entry, which checks Host/Origin and allows only the Tailscale logins you approve. The local Node process drives the official CLIs and writes sessions to their own history.

Read Security first.

This is access to your whole computer.

Anyone who can reach AIReins has the power of your user account on that machine.

Read Security in the README
  • Loopback onlyAIReins listens on the local loopback address.
  • Your tailnet, your allowlistRemote access goes only through Tailscale, for logins you explicitly allow.
  • Keep it off the public internetNever expose AIReins with Funnel or port forwarding.

Keep the reins in your hand.

Installation, prerequisites and remote setup are in the README.

Windows + WSL2 and native Linux supported. macOS is experimental, with CI coverage only.

Get started in the README