49ctl CLI
A CLI starts 49 Agents IDE, bringing terminals and files from multiple machines onto one zoomable canvas.
- 589 ★ on the repository
- Last commit
Broad access
Why this level
- Browser controls reach terminals and files on connected machines with the permissions of your accounts.
Install
- Works in
Manual install
./49ctl setupThe first setup-wizard command in Quick Start, run from the downloaded repository. Follow with `./49ctl start`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Browser controls reach terminals and files on connected machines with the permissions of your accounts.
This is third-party code. Review the repository files before installing.
What it does
49ctl configures and starts a local 49 Agents IDE stack. Users open the browser and arrange terminals, a file editor and notes on a canvas. Panes can be moved and resized, and their layout persists. Terminals use tmux, with an agent on each connected machine talking to a shared server. Users can follow several tasks and switch between projects from one workspace. Input can be broadcast to several selected terminals.
Who it is for. Engineers running several terminal agents across their own machines who want to see them side by side.
Good fit when
- Agents run on several machines and their terminals should share one view.
- A long task needs command output, a file and notes beside each other.
- You check the same workspace from a phone.
- During patch review, you want the file beside its terminal.
Not a fit when
- Organization rules prohibit browser-based terminal access.
- Untrusted commands require a sandbox.
- Terminal input and output must not pass through a hosted relay.
Example request
Set up local 49 Agents IDE for two test terminals and show the running processes.Limitations
Run 49ctl from the downloaded repository; the command alone cannot set up a missing checkout. Terminals retain your user permissions on connected machines, so begin with a separate test project. A hosted relay carries terminal input and output even though the server does not persist that data. BSL 1.1 allows free use by individuals and small teams; check the license terms for your team size before deployment.
How to disable. Stop the 49 Agents IDE server and machine agents. End unwanted tmux sessions separately; closing a browser tab does not stop their commands.
FAQ
Where do I open the workspace?
After startup, open `http://localhost:1071`. Local use needs no account sign-in.
How do I start it after setup?
Run `./49ctl start` in the project directory to start the server and agent.
Can I send the same command to several terminals?
Yes, with broadcast mode. Check the selected terminals first because each receives the same keystrokes.
How do I navigate many panes?
Zoom out for an overview and zoom in on the pane you need. The layout is saved.
Is there a browser file editor?
Yes. The IDE uses Monaco and places it on the same canvas as the terminals.
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 web workspace with two persistent terminals: Codex sets the task and a second CLI agent writes the code.
dmux is a terminal agent manager for tasks across repositories in one session, keeping hidden panes running in the background.
A CLI and terminal app that show which coding agents in your tmux sessions are working, waiting on you or done
A terminal workspace where several CLI agents like Codex, Claude and Gemini exchange messages and work on one task under human oversight
A CLI links a machine to IM.codes for remote coding-agent sessions, shared memory and communication between agents
README in short
The IDE also includes a Monaco editor, a Git graph and Beads task tables. A separate macOS desktop application is available.