@linzumi/cli
v1.0.296
Published
Linzumi CLI — point a Codex agent at the real code on your laptop, with your team watching and steering from shared threads.
Readme
Linzumi
▓▓╗ ▓▓╗▓▓▓╗ ▓▓╗▓▓▓▓▓▓▓╗▓▓╗ ▓▓╗▓▓▓╗ ▓▓▓╗▓▓╗
▓▓║ ▓▓║▓▓▓▓╗ ▓▓║╚══▓▓▓╔╝▓▓║ ▓▓║▓▓▓▓╗ ▓▓▓▓║▓▓║
▓▓║ ▓▓║▓▓╔▓▓╗ ▓▓║ ▓▓▓╔╝ ▓▓║ ▓▓║▓▓╔▓▓▓▓╔▓▓║▓▓║
▓▓║ ▓▓║▓▓║╚▓▓╗▓▓║ ▓▓▓╔╝ ▓▓║ ▓▓║▓▓║╚▓▓╔╝▓▓║▓▓║
▓▓▓▓▓▓▓░░░░░░░░╚▓▓▓▓║▓▓▓▓▓▓▓╗╚▓▓▓▓▓▓╔╝░░░░░░░░▓▓║▓▓║
╚═══▒▒▒@@@@@@@@▒▒═══╝╚══════╝ ╚════▒▒▒@@@@@@@@▒▒╝╚═╝
▒@@@@@@@@@@@@@@@@▒ ▒@@@@@@@@@@@@@@@@▒
@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@
║║ ║║
║║ ║║
║║ ()-().----. ║║
║║ \"/` ___ ;_________║║_.'
║║ ` ^^ ^^ ║║
──────────╨╨─────────────··────··────────╨╨──────────────
secure mission control for all your agents on your computersLinzumi is a lightweight, Slack-like chat built for native AI Engineering teams. Your coding agents run on your computer, reach you in your browser or on your phone, and build context for your team about what's going well, what's blocked, and what's ready to ship. Ship more, regret less.
Try it
Paste this into your terminal:
npx -y @linzumi/cli@latest connect --supervise --workspace your-workspaceReplace your-workspace with your workspace slug. The Commander signs you in
through your browser, connects to that workspace, and stays running under a
supervisor. Add trusted project folders with linzumi paths add before asking
an agent to work in them.
Why a CLI
Your agent runs on the laptop you trust, with your real env vars, your real dotfiles, and your real branches. No "works in the sandbox VM, breaks in your repo" surprises. The chat side runs in your browser; the work side runs locally. This npm package is the local half.
What you'll have in three minutes
- A Linzumi workspace in your browser.
- A local Commander connected to one trusted project folder.
- A live Coding agent thread your team can watch and steer.
- Optional browser editor and preview forwarding for the running app.
Manual Runner Setup
Install the CLI or run it with npx:
npm install -g @linzumi/cli@latest
npx -y @linzumi/cli@latest connect --supervise --workspace your-workspace
npx -y @linzumi/[email protected] --version
linzumi --versionStart a local runner from a trusted folder:
linzumi paths add ~/code/my-app
linzumi start ~/code/my-appFor explicit runner roots, pass a comma-separated allowlist:
linzumi start ~/code/my-app --allowed-cwd <paths>For non-production Linzumi servers, connect accepts either API URL flag:
linzumi connect --linzumi-url ws://127.0.0.1:4140 --workspace default --allow-port-forwarding-by-defaultHeadless / remote runner auth (device flow)
The default connect flow opens a browser on the runner machine and waits
for an OAuth callback on localhost. That cannot work on a headless box -
a VPS, a Windows/SSH session, or any machine with no browser or no loopback
callback. For those, use --auth-mode device: the runner prints a short
user code plus a verification URL, and you approve it from a browser already
logged in to Linzumi on any other machine (e.g. your laptop).
linzumi connect --workspace <slug> --auth-mode device --api-url wss://serve.linzumi.comThe runner prints:
Authorize this computer:
Code: 5PYP8PC2
Open: https://serve.linzumi.com/api/v2/local-codex-runner/device- On any machine where you are signed in to Linzumi, open the
Open:URL. - Enter the 8-character
Code:and approve. - The runner long-polls, receives a scoped token, and connects - no browser or loopback callback needed on the runner itself.
The verification URL targets the same server you pass via --api-url /
--linzumi-url (defaulting to wss://serve.linzumi.com), so the link you
open always points at the server the runner connected to. The code expires
in 10 minutes; re-run connect to get a fresh one.
Agent-first launch path
The npx -y @linzumi/cli@latest connect --supervise command above signs
you in and keeps the Commander connected to your workspace. Add trusted
projects with linzumi paths add so agents can work in those folders.
What just happened
Linzumi keeps the browser/chat surface separate from the local work surface. The CLI authenticates your local Commander, publishes runner capabilities, and lets Linzumi ask that Commander to start Codex inside trusted folders only.
MCP for coding agents
Commander-started Codex sessions are preconfigured with a local MCP
server named linzumi. It lets the agent use the same approved
local-runner auth to read the scoped Linzumi message, thread, or channel
context, and to send a bounded DM to the Commander owner when configured.
Manual MCP commands are available for other MCP-compatible agents:
linzumi mcp doctor --api-url https://serve.linzumi.com --workspace <workspace> --channel <channel>
linzumi mcp config --api-url https://serve.linzumi.com --format codex
linzumi mcp config --api-url https://serve.linzumi.com --format claude-code
linzumi mcp server --api-url https://serve.linzumi.comThe shipped tools are linzumi_get_message, linzumi_get_thread,
linzumi_get_channel, and linzumi_dm_owner.
Three things to try first
- Ask the Coding agent to make a small UI change and watch the thread.
- Open the browser editor from the thread controls.
- Share the preview URL with a teammate or your phone.
Working as a team
Use the Linzumi thread as the shared source of truth. Humans can reply, steer, interrupt, or inspect output while the actual commands still run on the trusted local machine.
Trusted folders
Linzumi only edits inside folders you've explicitly trusted.
linzumi paths add ~/code/my-appThe trust list lives at ~/.linzumi/config.json. The bootstrap agent
adds /tmp/hello_linzumi for you on first run. For linzumi connect, the
selected --cwd is also trusted for that runner process.
When something looks wrong
Run linzumi --help or reconnect with linzumi start ~/code/my-app.
If the browser says no runner is connected, check that the terminal
running the Commander is still open and that the folder is listed in
~/.linzumi/config.json.
Slack-shaped on the surface. A multiplayer compiler underneath.
linzumi.com · agents.md ·
