Tide Commander CLI
A visual workspace for teams of Claude Code, Codex, OpenCode, Grok and Pi agents: files, Git, terminals and tasks in one window
- 75 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The server runs agents' local tools and exposes project files in the browser
- Agents act in your name with their own credentials, and `LISTEN_ALL_INTERFACES=1` exposes the server to the network
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/tide-commanderDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The server runs agents' local tools and exposes project files in the browser
- Agents act in your name with their own credentials, and `LISTEN_ALL_INTERFACES=1` exposes the server to the network
This is third-party code. Review the repository files before installing.
What it does
Tide Commander runs a local server on port 6200 and shows a team of agents in the browser. Each agent remains a real process with native tools, credentials and session history, while Tide normalizes the event streams of five agents, Claude Code, Codex, OpenCode, Grok and Pi, into one picture: tool calls, PTY output, background tasks, queues, context gauges and blockers. Teams follow a boss and subordinates model with delegation reports, project areas, labels and task boards, agent memory and switching an agent to another harness with smart context, a visible transcript or a fresh start. Beside it sits a workspace: a multi-root file explorer, a source editor, Git status and diffs, project search, test runs and previews of Markdown, Mermaid, Office documents, PDF and 3D formats. The server keeps sessions, so you can return to them from another browser, a phone or the Android app. Plugins, slash commands, webhooks, REST and WebSocket APIs extend the work, and HTTPS with the `AUTH_TOKEN` token covers remote access.
Who it is for. People who run several agents on one project and want to see their work, files and Git in one window, including from a phone.
Good fit when
- Claude Code and Codex work on a project at once and you need one picture of calls and statuses
- Tasks must be handed out to a team of agents with a boss, labels and a board
- An agent should move to another harness without losing the conversation
- You want to follow progress from a phone or tablet while agents work on the server
Not a fit when
- You need one small tool: the workspace includes an editor, Git, boards, plugins and a server
- You want to work with no agents installed: Tide drives the `claude`, `codex`, `opencode`, `grok` and `pi` commands and provides no models itself
- The server would stand open on a network without protection: without HTTPS and a token it must not leave localhost
Example request
Start Tide Commander, create a Claude Code agent for this project and give it the task from the board marked in progressLimitations
At least one installed and authenticated agent is required: `claude`, `codex`, `opencode`, `grok` or `pi`. Tide Commander runs local tools and exposes project files, so beyond localhost it needs HTTPS and `AUTH_TOKEN`, and binding to all interfaces is switched on with `LISTEN_ALL_INTERFACES=1`. Persistent agent modes are enabled separately in settings. Some features, such as sending context from the Chromium extension, need an extra install. The package is large and the interface is extensive, so it takes noticeably longer to learn than a console session manager.
How to disable. Stop the Tide Commander server and remove the global package with `npm uninstall -g tide-commander` if you installed it that way. A launch through `npx` leaves nothing except server data in the settings directory.
FAQ
Which agents are supported?
Claude Code, Codex, OpenCode, Grok and Pi. Each starts by its own command and several can sit side by side in one project.
How do I reach it from a phone?
Run `tide-commander start --https --generate-auth-token`, add LAN or VPN addresses to the certificate SAN list and keep the token in a password manager. There is also an Android app.
Can I switch an agent without losing the conversation?
Yes, the agent editor moves it to another harness in three ways: smart context, a visible transcript or a fresh start. For OpenCode only a fresh start is available.
Which port does the server use?
6200 on localhost by default. Binding to all interfaces is enabled with `LISTEN_ALL_INTERFACES=1` and access is protected with `AUTH_TOKEN`.
Do I need Bun?
No, `npx tide-commander@latest` is enough. For Bun there is `bunx tide-commander@latest`.
Discussion
No questions or reviews yet.
Related
CLI toolsA tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A local control panel for coding agents: it runs Claude Code and Codex, keeps a task queue and merges verified work into main.
DevChain runs a team of AI coding agents on your own machine with a shared board, chat, code review and live terminals.
A pixel-art office in the browser: each Claude Code or Codex session sits at a desk, types and raises a hand when it needs you.
A Rust CLI where a meta-agent hands work to Claude Code and Codex, each on its own branch and tmux session, in one view.
A local daemon assembles Claude Code, Codex and OpenCode into a team: tasks, separate worktrees, checks and merging.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Tide Commander (this card) | no | 75 | |
| Orchestrator | no | 119 | one agent launches others in the background with no visual workspace |
| cmux | no | 28,779 | a native macOS terminal with tabs and notifications |
| ccmux | no | 241 | shows agents in tmux with no editor or Git |
README in short
The README presents Tide Commander as a visual build suite for creating with AI and shows a 30-second launch. Capability tables, supported harnesses with commands and modes, a secure remote access section and an environment variable reference follow.