// Walk the user through installing cc-connect — check toolchain, run the build, wire the UserPromptSubmit hook into ~/.claude/settings.json, and verify with `cc-connect doctor`. Use when the user asks to "install cc-connect", "set up cc-connect", or anything in that intent.
How to participate in a cc-connect Room. Use whenever the user asks you to "tell the room", "send to chat", "ping <person>", "share <file> with the room", "summarise the chat", or anything else that involves the cc-connect chat substrate. Always call MCP tools — never paste raw text into the answer hoping the user will copy it. For creating / joining / leaving Rooms, see the `cc-connect-room` skill instead.
How to create, join, list, and leave cc-connect Rooms via MCP tools. Use when the user says "start a cc-connect room", "join cc-connect room <ticket>", "leave the room", "what room am I in", or "set my nickname". For chatting *inside* a Room, see the `cc-connect-chat` skill.
Cut a release of cc-connect — Rust binaries (`v*` tag), VSCode extension (`vscode-extension-v*` tag), or both. Use when the user says "publish", "release", "cut a release", "tag a release", "ship", or anything that implies pushing a versioned artifact. Handles version bumps, tag namespaces, CI watch, and the cross-artifact dependencies users keep forgetting.
Push local commits to origin/main with the right pre-flight checks — local compile, conventional-commits guard, branch protection awareness. Use when the user says "push", "push this", "push to main", or any short instruction to land local work on the remote. NOT for cutting releases — those go through the `publish` skill, not here.
Build / F5 / debug the cc-connect VSCode extension. Use when you're iterating on src/ or webview/ in this directory and need to know which command to run, how to inspect runtime state, or how to debug specific subsystems (webview rendering, Claude SDK driver, daemon spawn, log tail, IPC over chat.sock).
Stand up a self-hosted iroh-relay on a user-supplied Linux server so cc-connect can route gossip + iroh-blobs through their own infrastructure instead of n0's public relays. Walks through SSH access, TLS cert issuance via certbot, nginx reverse-proxy, iroh-relay binary install, and a systemd unit. Use when the user asks to "self-host the relay", "set up my own relay", "use my own server for cc-connect", or anything in that intent.
| name | cc-connect-setup |
| description | Walk the user through installing cc-connect — check toolchain, run the build, wire the UserPromptSubmit hook into ~/.claude/settings.json, and verify with `cc-connect doctor`. Use when the user asks to "install cc-connect", "set up cc-connect", or anything in that intent. |
Goal: get the user from a fresh clone to a working cc-connect room start setup, with the UserPromptSubmit hook wired and the multi-pane chat-ui (Bun + React + Ink) usable next to claude.
The repo ships an interactive install.sh that does the heavy lifting. Your job is to make sure it runs cleanly, surface what's happening at each step, and help the user past common failure modes.
cc-connect room start/join opens a 2-pane terminal layout via a multiplexer:
┌──────────────────────────┬──────────────┐
│ claude (PTY) │ cc-chat-ui │
│ inherits CC_CONNECT_ROOM │ Bun+React+Ink│
│ → hook fires per prompt │ tails │
│ → cc_send via MCP │ log.jsonl │
└──────────────────────────┴──────────────┘
| |
+--- chat.sock --+
|
chat-daemon (Rust)
|
iroh-gossip mesh
cc-connect-tui.cc-connect chat-daemon start <ticket>) owns the gossip mesh + chat.sock; it survives any single window so you can detach + re-attach without losing the room.bun build --compile to target/release/cc-chat-ui (~60 MB self-contained binary).Cargo.toml at the root with a [workspace] table and a cc-connect-core member. If not, ask the user to cd into their clone (or clone the repo) and re-invoke.target/release/cc-connect, the hook entry in ~/.claude/settings.json, and ~/.cc-connect/identity.key. Tell the user what's already in place so they don't re-do work.Default to running ./install.sh interactively (no --yes) so the user sees each prompt. Stream the output to the conversation. The script:
rustc / cargo (offers rustup install if missing)zellij first, tmux fallback. If both are present it notes that zellij will be preferred at launch. If neither is found, it warns + offers OS-specific install commands but does not fail — cc-connect room will fall back to the embedded TUIbun for the chat-ui build. If missing, offers curl https://bun.sh/install | bash. If user declines, skips the chat-ui build with a warningcargo build --workspace --release (5-10 min on a cold cache)bun install && bun run build (only if bun is available; ~30 s)~/.claude/settings.json (timestamped .bak) and merges the UserPromptSubmit hook entry idempotentlycc-connect-mcp (via claude mcp add if available, else direct write to ~/.claude.json)cc-connect, cc-connect-tui, cc-connect-hook, cc-connect-mcp, cc-chat-ui) into ~/.local/bincc-connect doctor at the endIf the user wants unattended install (CI, second machine), use ./install.sh --yes. To skip the slow build (already built), use --skip-build — chat-ui rebuild is also skipped if its binary already exists.
cargo build fails on ed25519-3.0.0-rc.4 — the upstream RC is broken against current pkcs8. The repo vendors a patched copy under vendored/ and a [patch.crates-io] block in the workspace Cargo.toml. If the build fails here, the user's clone is missing vendored/. Tell them to re-clone or git fetch origin main && git reset --hard origin/main.rustup install refused — the user may want to install Rust via Homebrew / their distro's package manager. Either is fine as long as rustc --version shows ≥ 1.85. Re-run ./install.sh --skip-build after Rust is on PATH? No — let the build run, otherwise the build flag check (which validates the Rust toolchain) is meaningless.~/.claude/settings.json already has a UserPromptSubmit hook from another tool — install.sh removes prior entries that point at our cc-connect-hook binary, but leaves other tools' entries alone. Confirm with the user by cating the file before/after and showing the diff.~/.bun/bin/bun and updates the user's shell rc, but the rc isn't sourced in the running install.sh shell. install.sh tries to export PATH for the current run, but if that fails it tells the user to open a new shell + re-run with --skip-build. Don't worry, the chat-ui binary just won't be built this run.bun install fails on a corporate proxy — bun honors HTTPS_PROXY / npm_config_registry. Suggest setting those before re-running. As a workaround, the user can skip chat-ui (decline the bun install prompt); cc-connect room then falls back to the embedded TUI which is bun-free.bun build --compile errors with Could not resolve: "react-devtools-core" — fixed in the committed package.json (it's a real dep, not external). If this resurfaces, tell the user to cd chat-ui && bun add react-devtools-core and rebuild.[FAIL] — read the message. Common ones:
hook entry: hook command not absolute → install.sh should have written an absolute path; if not, the user edited it after. Re-run.identity key: file mode 0644 (want 0600) → chmod 600 ~/.cc-connect/identity.key.active-rooms dir: … → it's auto-created on first cc-connect chat-daemon start or cc-connect chat. [--] (info) is fine.Tell the user:
settings.json and ~/.claude.json on launch).cc-connect room start (host a new one) or cc-connect room join <ticket> (join someone else's). This launches the multiplexer layout: claude L 60% + cc-chat-ui R 40%, both inheriting CC_CONNECT_ROOM.cc-connect room falls back to the embedded cc-connect-tui (single window, claude embedded as PTY). Functionally identical, just less idiomatic.Ctrl-p then arrow to switch panes, Ctrl-q quits zellij (chat-ui owns Ctrl-Q inside its pane).Ctrl-b then arrow to switch panes (default prefix).Ctrl-Y copy ticket · PgUp / PgDn scrollback · Tab / Enter accept @-mention completion · Esc dismiss popupTwo-laptop demo procedure section in README.md.~/.claude/settings.json directly — always go through install.sh. Direct edits skip the backup + idempotency logic and risk corrupting the user's other hooks.cargo install — cc-connect isn't on crates.io yet (vendored ed25519 patches block publish; see TODOS.md). Always build from the local clone.[patch.crates-io] block. Yes, it's ugly. Yes, it's needed. The reason is documented in TODOS.md and the comments at the bottom of the workspace Cargo.toml.