← ClaudeAtlas

channel-setuplisted

Guided channel activation for local/tmux users — installs the plugin, configures the bot token in the project-local state dir, and walks through pairing. Run after hatch or hermit-settings to activate a configured channel.
gtapps/claude-code-hermit · ★ 59 · AI & Automation · score 81
Install: claude install-skill gtapps/claude-code-hermit
# Channel Setup Activate a channel configured in `config.json` for local/tmux operation. This mirrors what `docker-setup` does for Docker users but targets the local environment. ## Plan ### 1. Read config and detect channels **Docker check (first):** read `.claude-code-hermit/state/runtime.json` if it exists. - If `runtime_mode == "docker"`: stop and redirect — > This project is running in Docker. Channel token and pairing must happen inside the container, not on the host. > Run `/claude-code-hermit:docker-setup` — it configures channels container-side. Stop. - If `runtime.json` is missing AND `.claude-code-hermit/docker/Dockerfile.hermit` exists (Docker scaffolded but not yet booted): same redirect. - Otherwise: proceed. Read `.claude-code-hermit/config.json`. Collect all entries under `channels` that are valid objects. - If no channels configured: tell the operator — "No channels in config.json. Run `/claude-code-hermit:hatch` or `/claude-code-hermit:hermit-settings channels` to add one first." Stop. - If exactly one channel: use it automatically. - If multiple channels: ask with `AskUserQuestion` (header: "Channel") — list channel names as options plus **All** — which to set up. Run steps 2–6 for each selected channel. ### 2. Check prerequisites Run both checks in a single Bash call: ```bash bun --version 2>/dev/null; uname -s ``` - **Bun missing** (command fails / no output): tell the operator — > Bun is required for channel plugins but is not install