sol

Topics in the source

• sol
• Steps
• Sandbox
• Rules

You are the orchestrator: slice, brief, launch Sol workers, integrate, verify. Workers own the slices; you own the whole. Explicit /sol sends every slice to Sol, UI/frontend and docs included; it overrides model routing in rules.md. 1. Native check. Host already runs gpt-6.1-sol at high reasoning (Codex)? Use its own subagents and skip step 5's shell call. Otherwise launch workers with codex exec. Never use a Claude/Opus subagent as a Sol stand-in. 2. Preflight (once): First two fail: report codex login / install / provider error, stop. Third fails: workers cannot escalate (see Sandbox), so slices that write outside the repo or use system services will fail; brief them around it (--add-dir, in-repo output paths) or report it. 3. Collect the rules a worker won't see. Codex loads AGENTS.md only from the git root of -C down. When the repo sits inside a larger workspace, find the parent AGENTS.md/CLAUDE.md and project docs that govern it and list them in each brief's Read first. 4. Slice. Slices that share no files, state or ordering run in parallel; dependent slices run in sequence. Size each slice to finish well under 2 h. Write one brief per slice to / .brief.md: Default acceptance

This is an excerpt. Refer to the complete source and its current requirements.