01
Chat owns the thinking
Planning and independent review stay in a plain cloud Chat thread.
Chat ↔ Codex, ringside
One goal.
Two corners.
Chat calls the play. Codex ships the change. TagTeamGPT keeps the same mission moving between them inside the desktop app.
Open source Desktop native Human on BLOCKED
PLAN IN CHAT × BUILD IN CODEX
INIT → PLAN → EXECUTE → REVIEW → DONE ✦ INIT → PLAN → EXECUTE → REVIEW → DONE
Interactive protocol
See the baton move.
Four stages. One task ID. No context avalanche.
CHATplan + review
CODEXedit + test
[C2C] PLAN
01 / 04
Round 01 · Chat
Turn intent into a finite plan.
Chat reasons about the goal, identifies the likely files, and defines what done means before Codex touches the repo.
The corner rules
Clear roles. Clean handoffs.
02
Codex owns the repo
Edits, shell commands, and tests happen where the project is mounted.
03
Keybinds move the baton
Desktop shortcuts and clipboard messages replace nested browser automation.
04
MCP stays read-only
Optional repo visibility gives Chat evidence without handing it write access.
Get in the ring
Install once.
Tag in anywhere.
Copy the skill to your shared Codex skills folder, open a cloud Chat thread for planning, and mount the real project in Codex.
Read the full setup guidegit clone https://github.com/tuckcode/TagTeamGPT.git
cd TagTeamGPT
mkdir -p ~/.agents/skills
cp -R .agents/skills/tagteam ~/.agents/skills/tagteam$ Invoke with $tagteam
THE BELL IS YOUR PROMPT.