CG Mode (Claude + GLM)

CG (Claude + GLM) mode is a hybrid mode where the leader uses the Claude API and the workers use the GLM API. It is implemented with tmux-session-level environment variable isolation and executes the Tokenomics split — “Claude plans deep, GLM implements cheap” — inside a single session. For implementation-heavy work, it saves roughly 60-70% of the cost.

moai cg runs
    │
    ├── 1. Inject GLM settings into the tmux session environment
    │      (ANTHROPIC_AUTH_TOKEN, BASE_URL, MODEL_* variables)
    │
    ├── 2. Remove GLM environment variables from settings.local.json
    │      → the leader pane uses the Claude API
    │
    ├── 3. Set teammateMode: "tmux" in settings.local.json
    │      → workers inherit GLM env vars in new panes
    │
    └── 4. Launch Claude Code (replaces the current process)

┌─────────────────────────────────────────────────────────────┐
│  Leader (current tmux pane, Claude API)                      │
│  - Workflow orchestration                                    │
│  - Handles plan, quality, and sync phases                    │
│  - No GLM env vars → uses the Claude API                     │
└──────────────────────┬──────────────────────────────────────┘
                       │ Teammate spawn (new tmux pane)
                       ▼
┌─────────────────────────────────────────────────────────────┐
│  Teammates (new tmux panes, GLM API)                         │
│  - Inherit tmux session env vars → use the GLM API           │
│  - Execute implementation work in the run phase              │
│  - Communicate with the leader via SendMessage               │
└─────────────────────────────────────────────────────────────┘

moai glm sk-your-glm-api-key

The key is stored safely in ~/.moai/.env.glm.

If you are already inside tmux, there is no need to create a new session.

# If you are not in tmux:
tmux new -s moai

Tip: setting tmux as your VS Code terminal default lets you skip this step entirely.

moai cg

moai cg automatically launches Claude Code in the current pane. There is no need to run claude separately.

/moai "Implement user authentication feature"

From here it works as usual. The orchestrator (the leader, Claude) handles planning, quality, and sync, while implementation-heavy work is delegated to GLM teammates in new tmux panes.

Note: the old --team flag (the Agent Teams static-orchestration layer) was retired in v3.0. Forcing it falls back to sub-agent mode. CG mode’s leader/worker separation runs on Claude Code’s built-in teammate runtime (tmux panes), and that runtime is preserved.

Since v3.0.0, when moai cg injects the GLM token (ANTHROPIC_AUTH_TOKEN) into the tmux session environment, it uses the source-file channel (tmux source-file <tmp>) instead of the argv channel (tmux set-environment <KEY> <VALUE>). The token is no longer exposed in plaintext to ps auxe, /proc/<pid>/cmdline, auditd logs, sysmon traces, or crash dumps (CWE-214).

1. Create a temp file under ~/.moai/run/ with mkstemp (mode 0o600 enforced)
2. Write a single set-environment -t <session> <KEY> <VALUE> line
3. Have tmux read the file into the environment via tmux source-file <tmp>
4. Unlink with os.Remove immediately after injection

Only the temp file path appears in argv — the token itself is never exposed.

Values that are not tokens — CLAUDE_CONFIG_DIR, ANTHROPIC_BASE_URL, ANTHROPIC_DEFAULT_*_MODEL, etc. — keep the existing argv path (no security threat).

The ~/.moai/.env.glm source file must keep 0o600 permissions in your environment. The moai glm command sets this automatically:

stat -c '%a' ~/.moai/.env.glm    # Linux: 600
stat -f '%A' ~/.moai/.env.glm    # macOS: 600

Verify the token is not exposed in argv while CG mode is running:

# Inside a new tmux session after running moai cg
ps auxe | grep -i 'tmux set-environment.*ANTHROPIC_AUTH_TOKEN'
# Expected: 0 matches (the token is not in argv)

For the detailed threat model, failure behavior (the ErrTmuxSensitiveInjectFailed sentinel), and additional checks, see Security Notes — CWE-214.

teammateMode is a Claude Code built-in display setting, stored in settings.local.json. It is a different concept from MoAI’s team-mode (the old --team flag, retired in v3.0) — the teammate runtime itself is provided by Claude Code, and teammateMode controls only its display style.

moai cg and moai glm set teammateMode to "tmux" in settings.local.json, and moai cc clears it to an empty value. The teammateMode setting takes precedence over the old CLAUDE_CODE_TEAMMATE_DISPLAY environment variable.

CG mode can only separate leader/worker APIs in the tmux display mode.

Good fit for CG mode:

• Implementation-heavy SPEC execution (run phase)
• Code generation
• Test writing
• Documentation generation

Good fit for Claude-only (cc):

• Architecture design/planning (needs Opus reasoning)
• Security reviews (needs Claude’s security training)
• Complex debugging (needs advanced reasoning)

• Model Policy — per-agent model assignments
• FAQ — execution mode FAQ
• CLI Reference — moai cc, moai glm, moai cg details