ck:team

You can orchestrate parallel multi-session collaboration by spawning independent Codex teammates with their own context windows, communicating via shared task lists and messaging to handle research, implementation, review, and debug workflows.

Use agent team templates like ck:research, ck:cook, ck:code-review, and ck:debug to spawn specialized teammates, applying optional git worktree isolation for implementation tasks to prevent file conflicts.

Yes, parallel multi-session collaboration requires Agent Teams enabled, the Claude Code CLI terminal, and all teammate sessions must run the Opus 4.6 model.

Git worktree isolation provides each implementation teammate with a separate working directory, preventing file conflicts when multiple agents modify code simultaneously during parallel sessions.

Yes, you can launch a research session with multiple researchers using a command like /ck:team research <topic> --researchers 3, allowing independent agents to explore the same topic in parallel.

Agent teams require all teammates to run Opus 4.6 and depend on shared task lists for messaging, meaning coordination overhead increases with more sessions and context is isolated per teammate window.