Session pipes for any agent CLI.
Shell pipes connect commands. Session pipes connect agents. humOS gives you pipe(), signal(), and (soon) join() across every agent CLI on your Mac. Claude Code, opencode, more. Stop being the message bus. Runs locally. No API key.
$brew tap humos-dev/humos && brew install --cask humos
You're running 5 Claude sessions. One is writing a schema. One is writing tests. One is debugging the API. One is drafting the migration. One is stuck waiting for an answer. You're the glue. You're the bottleneck. You paste outputs between windows like it's 1998.
What humOS gives you
Three primitives. That's the whole product.
The dashboard shows your sessions. The primitives coordinate them. pipe() and signal() ship today. join() is next.
Stop pasting between sessions. A writes a schema, B starts testing against it automatically. 200ms from idle to injected.
Tell all your sessions to stop, pivot, or re-read a file. One broadcast, every session hears it. 2-second undo, per-session delivery confirmation.
Wait for multiple sessions to finish, aggregate their outputs. In spec. Shipping soon.
How it works
No API. No proxy. No new agent to install.
- humOS watches your agent CLI session stores:
~/.claude/projects/for Claude Code,~/.local/share/opencode/opencode.dbfor opencode. - You set up pipe rules or trigger a signal from the dashboard.
- humOS injects messages directly into each agent CLI's prompt via Terminal.app. Works with Claude Code, opencode, or any Terminal-resident TUI.
- Your sessions coordinate. You review the output.
Why this exists
Unix gave fork, pipe, signal, and join for process coordination. humOS gives you the same thing for AI agents.
The missing layer isn't a smarter agent. It's the plumbing between the agents you already have. The dashboard is the inspector. The primitives are the OS.
How it compares
The coordination layer, not another agent.
| humOS | Conductor | opcode | claude-control | |
|---|---|---|---|---|
| Observes existing sessions | yes | no | no | yes |
| Route session A → session B | yes | no | no | no |
| Broadcast to all sessions | yes | no | no | no |
| Works with your existing subscription | yes | no | yes | yes |
| Open source | yes | no | yes | yes |
| Linux / Windows | no | no | yes | yes |
Status
v0.5.6. Built by one person. MIT licensed.
pipe() and signal() ship today. join() is next. macOS only. Linux and Windows are not planned. If it breaks, file an issue.
▸ If you're running 5 Claude sessions right now, you are already the target user.Install
Built for developers running 3+ parallel agent CLI sessions on macOS. Claude Code, opencode, or both side-by-side.
Two ways to install. No API key. No account.
$ brew tap humos-dev/humos && brew install --cask humos
$ curl -fsSL https://humos.dev/install.sh | sh
2. Open Terminal and run before extracting:
xattr -cr ~/Downloads/humOS_*.zip
3. Double-click the ZIP to extract, drag humOS.app to Applications4. Open normally
xattr -cr /Applications/humOS.app
Still in Downloads? Use xattr -cr ~/Downloads/humOS.app instead.
FAQ
macOS says humOS is "damaged and can't be opened." Why?
macOS Gatekeeper blocks unsigned apps downloaded from the internet. humOS is not damaged. Open Terminal and run: xattr -cr /Applications/humOS.app then try opening again. If the app is still in Downloads, use xattr -cr ~/Downloads/humOS.app instead. The Homebrew and one-liner installs handle this automatically.
What permissions does it need?
Accessibility permission to inject text into Terminal.app. macOS will prompt you on first use. You can revoke it anytime in System Settings.
What data does it access?
Reads ~/.claude/projects/ (Claude Code session files) and ~/.local/share/opencode/opencode.db (opencode session database, opened read-only). Writes pipe rules to ~/.humOS/pipe-rules.json. Nothing else. No network calls, no cloud, no telemetry.
Does it run in the background?
No. When you quit humOS, it stops completely. No background processes, no daemons, no menu bar agents.
How do I uninstall?
brew uninstall --cask humos removes the app. Delete ~/.humOS/ to remove saved pipe rules. That's everything.
What platforms are supported?
macOS 13+ (Ventura or later). Terminal.app and iTerm2. Linux and Windows are not planned. humOS uses AppleScript for terminal injection, which is macOS-only.
Is it open source?
Yes. MIT licensed. github.com/humos-dev/humos. Contributions welcome.