SkillAgentSearch skills...

collab-ai

Local messaging for AI coding agents. Connect Codex and Claude Code through an MCP server, Unix sockets, and a SQLite-backed broker.

Install / Use

claude mcp add makarski -- npx -y github:makarski/collab-ai

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

83/100

Supported Platforms

Claude Code
Claude Desktop
OpenAI Codex

Our assessment of collab-ai

collab-ai scores 83/100 on our quality scale, 335th of 424 Communication skills we index.

Its MCP Server is 6.9 KB long, well organised into 44 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 10 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
4/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so collab-ai is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

collab-ai compared with similar skills

All 4 of these similar skills score higher than collab-ai; compare them before choosing.

SkillScoreStarsUpdatedFormat
collab-ai (this skill)by makarski8310todayMCP Server
claude-memby thedotmack100100.6ktodayCLAUDE.md
Agent-Reachby Panniantong10097.2k6d agoCLAUDE.md
headroomby headroomlabs-ai10075.3ktodayCLAUDE.md
CowAgentby zhayujie10047.4ktodayCLAUDE.md

Frequently asked questions

How do I install collab-ai?
Run claude mcp add makarski -- npx -y github:makarski/collab-ai. The install tabs above show the steps for each supported agent.
Which AI agents does collab-ai work with?
It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is collab-ai safe to use?
It is MIT-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is collab-ai still maintained?
The repository was last updated today, so collab-ai is actively maintained.

collab-ai

Codex and Claude, working together in a sandbox.

  • Real-time collaboration with durable messages and automatic delivery.
  • An isolated Incus workspace with persistent projects and agent memory.
  • Token usage visibility and soft caps for managed Codex; shared caps are not yet available.

MIT licensed · First install · Troubleshooting

Set up a sandbox

Provision once, then use the block below each day. Tools are preinstalled—no compilation needed. Provisioning runs OpenTofu in a disposable container; no host Terraform/OpenTofu install is needed. Dev has network access; optional control stays offline. Host credentials and conversations are not imported.

Host prerequisites: Python, Git, OpenSSH and Incus; macOS also needs Colima. Install commands. No gh or browser download needed.

# First install or upgrade (Incus must be running; upgrades end active sessions)
python3 scripts/sandbox-provision.py rollout
# Pin a version: add --release workspace-vX.Y.Z

Run host commands from your provisioning checkout. On Linux, skip Colima commands and use local: / --remote local. For host mounts, see the mounts.json example.

# HOST: run from your provisioning checkout
# Start the Mac VM, then the containers
python3 scripts/sandbox-host.py apply
incus --project collab-ai start colima-collab-ai:secured   # if secured_runtime = true
incus --project collab-ai start colima-collab-ai:workspace

# Check: expect workspace (and secured, if enabled) to show RUNNING
incus --project collab-ai list colima-collab-ai:

# Optional: preview host mounts; uncomment with your file (does not apply)
# python3 scripts/sandbox-host.py mounts-plan --mounts-file /path/to/mounts.json

# Configure SSH once, check the broker, then enter dev
python3 scripts/sandbox-ssh.py --remote colima-collab-ai
ssh -F infra/incus/ssh/config workspace collab status
ssh -F infra/incus/ssh/config workspace

# CONTAINER: all commands below until exit run inside your SSH session
# First use only: uncomment to sign in before starting agents
# Codex: open the printed URL on your host and enter the device code
# command codex login --device-auth
# command claude auth login
# gh auth login --web --git-protocol https  # optional GitHub CLI login
# collab-codescene-login                  # optional CodeScene token; hidden prompt

# First use only: clone if you have not already done so
# git clone https://github.com/makarski/collab-ai.git /workspace/collab-ai
tmux new -A -s collab

# In each tmux window: enter the project, then choose one agent or dashboard
# Ctrl+B then C opens another window
cd /workspace/collab-ai
codex                         # new managed Codex conversation
# codex resume                # choose a saved sandbox conversation
# codex resume SESSION_ID     # resume a specific sandbox conversation
# claude                      # Claude with collaboration channels enabled
# claude --resume             # resume Claude
# dashboard                   # broker status and agent inboxes
# rtk gain                    # estimated shell-output token savings
# docker info                 # rootless Docker inside workspace
# docker compose up -d        # run your project's compose.yaml

# Disconnect: Ctrl+B then D detaches tmux; exit leaves SSH
exit

# HOST AGAIN: optional shutdown; stops agents, keeps persistent files
# incus --project collab-ai stop colima-collab-ai:workspace
# incus --project collab-ai stop colima-collab-ai:secured   # if secured_runtime = true
# colima stop collab-ai

Expect Broker: ready. Run one Codex and one Claude session; additional sessions need distinct agent IDs. Login help. Both agents should read /usr/local/share/collab-ai/SKILL.md.

Mount directories · Mac writable sharing · Docker and Compose · Bundled MCP tools · Upgrade or reprovision · Back up · Stop or remove

Dashboards

Run on your host:

# Agent connections and pending messages (terminal UI)
ssh -t -F infra/incus/ssh/config workspace collab dashboard

# Containers, resources and logs (browser UI)
incus webui colima-collab-ai:  # Linux: incus webui local:

For Incus, open the printed URL and select project collab-ai. The collaboration dashboard is read-only; prompts and approvals stay in agent terminals. Controls · UI help.

How it fits together

With secured_runtime = true, Codex, Claude and the read-only dashboard run in workspace; secured owns one broker and SQLite database. The shared Unix socket connects them. /workspace and /home/agent persist across container replacement.

Codex, Claude and the read-only dashboard in workspace connect through a shared Unix socket to the broker and SQLite in secured.

Architecture source · Control setup

<details> <summary>macOS and Linux layouts</summary>

| macOS: Colima hosts Incus | Linux: Incus runs directly | | --- | --- | | macOS sandbox | Linux sandbox | | Diagram source | Diagram source |

</details>

Security

Agent commands run inside the container. Host mounts default to read-only; writes require a dedicated sharing identity. Writable sharing lets agents change files that you or host automation may later execute. Boundaries.

Run on your host

No Incus? Follow the host quick start to build and run locally. These agents have no Incus isolation.

Resume or fork

Host commands and compatibility. Sandbox start/resume commands are in the daily block above.

Set a Codex soft cap

The sandbox aliases are uncapped by default. Use a named budget for one managed Codex launcher. Reports can arrive late; overshoot is possible. Claude and shared budgets are not yet covered.

Claude Code

The sandbox alias is preconfigured. For host sessions, use the dedicated channel config. Claude requires channel consent and account/organization support.

Reference and contributing

Protocol · Manual MCP · Status API · Agent skill

Report an issue. Run checks with:

go test -race ./... -timeout=30s

Related Skills

View on GitHub
GitHub Stars10
CategoryCommunication
Updated6h ago
Forks0

Languages

Go

Trust signals

97/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info