Isolated accounts per provider
Several Claude Code, Codex or OpenCode accounts side by side, each in its own home folder. No more signing out and back in.
macOSDesktop app in development
Run every AI CLI from one place
YardPro runs Claude Code, Codex, OpenCode and other AI CLIs side by side, each account isolated, on the model you choose, in a terminal mosaic or a chat view built for many agents at once.
Runs the AI CLIs you already use
YardPro finds each one on your PATH, with its version.
- Claude Code
- Codex
- OpenCode
- Gemini CLI
- Antigravity
- Kimi Code
- Qwen Code
- Cursor CLI
- Copilot CLI
- Goose
- Grok Build
Available now
Built for people who run many agents at once
Already working in the desktop app.
Third-party models
Run Claude Code, OpenCode or Codex on another backend, such as DeepSeek, Kimi, GLM, OpenRouter or Ollama. The API key stays in the system vault.
Folders and workspaces
Link a real folder or keep a virtual one. A workspace can run in its own git worktree, with a default account and extra environment.
Terminal or chat
Open a session as the plain terminal or as a chat: streaming answers, tool cards with diffs and approvals by button. Claude Code and Codex move the same conversation between both.
Usage and limits
5-hour and weekly bars for your Claude and Codex plans in the status bar, with where each number comes from.
One brain for every account
Import your skills, MCP servers, hooks and instructions from each CLI once. YardPro writes them into every account, in each CLI's own format.
Terminal mosaic
A terminal mosaic that keeps up with your agents
Split, drag, zoom and restore. Every workspace remembers its layout.
Tiles per workspace
Split, move and resize terminals. Reopen the app and the layout comes back.
Detach to its own window
Send a terminal to another monitor. It stays attached to the same session.
Keep awake
One click keeps the display awake while long tasks run.
Terminals that keep running
The terminal service keeps your sessions alive while the window is closed.
How it works
From install to a full mosaic in three steps
Accounts, workspaces and terminals, set up from the app.
- Step 01
Connect your accounts
Add an account per provider. YardPro opens the CLI's own sign-in in an isolated terminal, or keeps your API key in the system vault.
- One home folder per account
- Sign-in done by the CLI itself
- API keys only in the system vault
- Step 02
Organize workspaces
Group work in folders. Terminals of a workspace start in its directory with its default account and extra environment.
- Real or virtual folders
- Optional git worktree per workspace
- Provider variables stay in accounts
- Step 03
Run them side by side
Open terminals in a mosaic, zoom into one, see every terminal at once, or send one to another monitor.
- Keyboard shortcuts to split and move
- All terminals in one view
- Layout restored when you reopen
Privacy
Your credentials stay yours
YardPro organizes your CLIs without taking over their configuration.
Detection without reading
To find your CLIs, YardPro only runs each one's --version. It never reads your tokens.
One home per account
Each account signs in inside its own isolated folder, so accounts never share a login.
Keys in the system vault
API keys reach the CLI only through the terminal's environment, never a file.
- DeepSeek
- Kimi
- GLM
- MiniMax
- Qwen
- OpenRouter
- Ollama
Models
Bring any model behind the CLI you trust
Presets for DeepSeek, Kimi, GLM, MiniMax, Qwen, OpenRouter and Ollama, with your own model and endpoint.
On the roadmap
What comes next
Planned and not available yet.
Shared memory
Coming soonFacts every account and every CLI can save and recall, with search by meaning.
Agents that talk to each other
Coming soonA message bus between sessions, and rules that hand work from one agent to the next.
Cost for every provider
Coming soonTokens and cost per session, workspace and account, Gemini and OpenCode included.
Voice dictation
Coming soonDictate straight into the selected terminal, transcribed on your machine.
Built-in browser
Coming soonInspect an element on a page and send it to the terminal.
Mobile remote
Coming soonFollow and control your CLIs from iOS and Android, end-to-end encrypted.
FAQ
Answers to common questions
What YardPro does today, and what it does not.
Is YardPro an IDE?
No. There is no editor, file tree, diff viewer or file search. Your editor stays yours; YardPro runs and organizes your AI CLIs.
Which CLIs does it detect?
Claude Code, Codex, Gemini CLI, Antigravity, OpenCode, Kimi Code, Qwen Code, Cursor CLI, Copilot CLI, Goose and Grok Build, found on your PATH with their version. Any other command runs in a plain shell.
Can I use a chat instead of the terminal?
Yes. A session opens as the terminal or as a chat view that talks to the CLI through the Agent Client Protocol, with approvals by button. Antigravity stays terminal only.
Does YardPro read my tokens?
No. Detection only runs each CLI's --version, each account signs in inside its own folder, and API keys stay in the system vault. The brain keeps only the names of the keys your MCP servers read.
Can I use DeepSeek, Kimi or a local model?
Yes. An account can run Claude Code, OpenCode or Codex on a third-party backend, including Ollama on your own machine. You choose the model and the endpoint.
Which platforms are supported?
macOS comes first. Windows and Linux are not validated yet.
When can I download it?
The macOS download goes live on this page when the desktop app is ready. You can create your account now.
Download
Ready to take command?
YardPro for macOS is in development. The download goes live here.