executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
rg-budget-searchIn large or many-file projects, prefer cxs over raw rg/grep to reduce context waste.
Independent GitHub snapshot · Automated classification · Original documentation governs
In large or many-file projects, use MCP cxs(op,args) or CLI cxs before raw rg/grep.
Default flow: find(files_only:true) to identify candidate files, find(paths=[...]) to locate bounded line hits, then use Codex-native reads for the exact file or span.
Use --path or paths for concrete files/directories. Use --scope or scopes only for presets: docs, src, tests, config, analysis, runs, vendor, all.
For small projects, known files, or narrow checks, normal file reads/direct shell tools are fine. If output is truncated, refine query/scope/path or continue files-only pagination with next_page.offset.