Spawns a separate Codex worker at the strongest currently available model and xhigh effort. The Slack thread’s defaults stay untouched.
@ForgeBot Run this as a one-off Codex job using the best available Codex model at xhigh reasoning. Keep this thread’s defaults unchanged. Verify the result. Task: describe the work here.
“Best available” is resolved at run time. This is the reliable way to upgrade a single task; a normal prompt cannot swap the current brain halfway through its turn.
02 · CURRENT THREAD
Turn Up This Session
Use commands in an active Slack thread, then send the task normally.
!model gpt-5.6-sol --session
!reasoning xhigh
Describe the task here.
!reasoning!reasoning reset!model
Session model overrides clear on a new session. Reasoning reset returns to the configured default.
03 · PERSISTENT LOOP
Goal: Keep Going Until Proven
Best for multi-turn work that should continue without repeated “keep going” messages.
!reasoning xhigh
!goal draft Use Codex to reach the stated outcome. Verify with named tests or evidence. Preserve the stated constraints. Stop and ask if a named blocker occurs.
!goal status!goal pause!goal resume!goal clear
A goal auto-continues and judges completion, up to the configured turn budget. It is one durable objective, not a backlog.
04 · TEAM MODE
Codex Lead + Parallel Workers
Use for separable research, implementation, or review work. ForgeBot orchestrates; Codex workers execute; the lead verifies.
@ForgeBot Use a Codex lead plus two parallel Codex workers at the best available model and xhigh effort. Split this into independent workstreams, then have the lead verify and synthesize. Task: describe the work here.
Two parallel workers is the ForgeFX default ceiling. For code, ask for isolated git worktrees when workers will edit independently.
CHOOSE A TEAM SHAPE
Useful Codex Strategies
Builder + ReviewerOne implements; one attacks the diff and tests. Best default for code.
Parallel ResearchWorkers investigate independent sources; lead reconciles conflicts.
Worktree PairTwo isolated branches tackle independent issues; lead integrates only verified work.
Draft + Red TeamOne drafts; one looks for omissions, weak claims, and failure modes.
Slack syntax: Start a channel conversation with @ForgeBot. Once the thread is active, plain replies work. Use !command inside threads because Slack blocks native slash commands there. Native /command works outside threads when installed.
