CGPT Tool Routing Lessons
Use this skill when a task involves uncertain file reach, sandbox boundaries, connector-backed files, cloud-synced folders, or paths outside the current writable workspace.
This is a Codex-native adaptation of prior tool-routing lessons. Do not copy Cowork/Desktop Commander mechanics into Codex sessions.
Routing Rules
Workspace files.
- Read with normal shell commands, preferring
rg, Get-Content, and targeted Get-ChildItem.
- Edit with
apply_patch for manual file edits.
- Use repo-local validation before claiming success.
Writable roots.
- Confirm whether the target path is inside the current writable roots before editing.
- If it is outside, request approval with
sandbox_permissions: require_escalated.
- Do not work around approvals by writing elsewhere and asking the user to copy.
Connector files.
- If a user explicitly references Google Drive, Gmail, GitHub, or similar app context, prefer the relevant connector/plugin when available.
- If connector access is unavailable but a synced local tree exists, use the local synced path and state that route.
User profile or app config paths.
- Treat
%APPDATA%, %LOCALAPPDATA%, .codex, .claude, program folders, and system paths as outside normal workspace scope.
- Reads may be allowed; writes usually require escalation or explicit user authorization.
Network or dependency operations.
- If a required command fails due to network, sandbox, or registry/index access, rerun with escalation and a clear justification.
- Do not silently skip dependency installation if it is required for the requested verification.
Failure Signatures
| Symptom |
Likely cause |
Action |
| Access denied in a profile or temp path |
sandbox or filesystem ACL |
switch to workspace path or request escalation |
| File exists in Explorer but command cannot see it |
wrong drive, sync state, allowlist, or path quoting |
verify exact path with Get-Item -LiteralPath |
| Git sees huge whole-file diffs |
line endings or encoding churn |
use cgpt-line-endings-hygiene |
| A connector file cannot be read locally |
not synced or connector required |
use the app connector or ask for path/export |
| Dev/test command cannot download packages |
restricted network |
rerun with escalation if needed |
Reporting
When routing mattered, report:
- which path was used
- whether it was workspace, synced local, connector, or profile/config
- whether escalation was required
- any path or access limitation that remains
Boundaries
- Do not edit memory or profile-level configuration unless the user explicitly asks and the target is verified.
- Do not assume a path from a previous tool environment is valid in Codex.
- Do not use destructive filesystem commands without explicit request and path verification.
1---2name: cgpt-tool-routing-lessons3description: Apply Codex-native routing lessons for filesystem sandbox boundaries, connector scopes, local workspace paths, escalation, and tool choice. Use when file access fails, paths are outside the workspace, connectors may be needed, writes require approval, or a task crosses local/cloud/profile directories.4---56# CGPT Tool Routing Lessons78Use this skill when a task involves uncertain file reach, sandbox boundaries, connector-backed files, cloud-synced folders, or paths outside the current writable workspace.910This is a Codex-native adaptation of prior tool-routing lessons. Do not copy Cowork/Desktop Commander mechanics into Codex sessions.1112## Routing Rules13141. Workspace files.15 - Read with normal shell commands, preferring `rg`, `Get-Content`, and targeted `Get-ChildItem`.16 - Edit with `apply_patch` for manual file edits.17 - Use repo-local validation before claiming success.18192. Writable roots.20 - Confirm whether the target path is inside the current writable roots before editing.21 - If it is outside, request approval with `sandbox_permissions: require_escalated`.22 - Do not work around approvals by writing elsewhere and asking the user to copy.23243. Connector files.25 - If a user explicitly references Google Drive, Gmail, GitHub, or similar app context, prefer the relevant connector/plugin when available.26 - If connector access is unavailable but a synced local tree exists, use the local synced path and state that route.27284. User profile or app config paths.29 - Treat `%APPDATA%`, `%LOCALAPPDATA%`, `.codex`, `.claude`, program folders, and system paths as outside normal workspace scope.30 - Reads may be allowed; writes usually require escalation or explicit user authorization.31325. Network or dependency operations.33 - If a required command fails due to network, sandbox, or registry/index access, rerun with escalation and a clear justification.34 - Do not silently skip dependency installation if it is required for the requested verification.3536## Failure Signatures3738| Symptom | Likely cause | Action |39|---|---|---|40| Access denied in a profile or temp path | sandbox or filesystem ACL | switch to workspace path or request escalation |41| File exists in Explorer but command cannot see it | wrong drive, sync state, allowlist, or path quoting | verify exact path with `Get-Item -LiteralPath` |42| Git sees huge whole-file diffs | line endings or encoding churn | use `cgpt-line-endings-hygiene` |43| A connector file cannot be read locally | not synced or connector required | use the app connector or ask for path/export |44| Dev/test command cannot download packages | restricted network | rerun with escalation if needed |4546## Reporting4748When routing mattered, report:4950- which path was used51- whether it was workspace, synced local, connector, or profile/config52- whether escalation was required53- any path or access limitation that remains5455## Boundaries5657- Do not edit memory or profile-level configuration unless the user explicitly asks and the target is verified.58- Do not assume a path from a previous tool environment is valid in Codex.59- Do not use destructive filesystem commands without explicit request and path verification.
pvsundar