# Ccb Launcher

> Compatibility shim for the legacy CCB environment bootstrap workflow from claude-ccb-skills. Use when the user wants to start CCB, check CCB status, launch WezTerm, or troubleshoot the local CCB environment.

- Skill: `leolin990405/ccb-launcher` (Agent Skill)
- Install (CLI): `npx skillmds@latest add leolin990405/ccb-launcher`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leolin990405/ccb-launcher/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: LeoLin990405 (https://skillmd.com/u/leolin990405)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/leolin990405/ccb-launcher

---


# CCB Launcher (Compatibility)

This compatibility skill preserves the legacy `ccb-launcher` entrypoint from `claude-ccb-skills`.

Canonical orchestration now lives in `../ccb-unified/SKILL.md`, but this shim keeps the legacy launch workflow available as an installed leaf skill.

## Core Workflow

1. Validate the environment with `ccb -v`, `python3 --version`, and `echo $TERM_PROGRAM`.
2. If the user is not already in WezTerm or tmux, launch WezTerm with `open -a WezTerm` and tell the user to run `ccb` there.
3. Check configuration with `cat ~/.ccb/ccb.config`.
4. Recommend launch commands such as `ccb`, `ccb codex gemini`, or `ccb -r`.
5. Use provider health checks like `cping`, `gping`, `oping`, `iping`, `kping`, `qping`, `dskping`, and `dping` when troubleshooting.

## Notes

- CCB must run interactively inside WezTerm or tmux.
- Keep this shim for legacy entrypoint compatibility.
- Prefer `ccb-unified` for new multi-provider orchestration flows.