Rail-Connector-MCP: Skill for Codex

Rail Connector Operator

Operate Claude through the exposed mcp__rail_connector tools. Use the actual task project as cwd, even when this skill is loaded from the MCP repo.

Rules

• Do not simulate an MCP result. If tools are missing after an install or update, explain that Codex needs a fresh task or restart.
• Keep Codex, this MCP, Claude, paths, credentials, and logs in the same OS context.
• Call status when lifecycle is unclear and get_claude_capabilities before permission, effort, or Ultracode launch decisions.
• Use debug: true only for an explicit, bounded diagnostic run. Inspect the returned debugLog provenance and size; the MCP never returns contents, and the retained file is sensitive local evidence.
• Give parallel jobs unique managedSession names. A Windows broker session persists across MCP/Codex task refresh and must be explicitly stopped.
• Treat managed terminal name, Remote Control remoteName, conversation title, and conversation UUID as different identities.
• Prefer submit_prompt plus wait_for_claude_turn. Use terminal capture for attention states and low-level diagnosis, not as the clean answer channel.
• Claude spinner phrases are variable. Trust the returned structured state, completion ordering, and transcript cursor rather than matching a particular phrase.
• Treat workflowPending: true as busy even when the composer appears idle. The MCP combines the exact dynamic-workflow wait control line with sanitized session-log task lifecycle evidence and blocks submit, low-level text/Enter, rename, replacement, and ordinary stop with reason workflow_pending.
• Read terminalState separately from the combined state. Workflow activity can make state busy while terminalState remains idle. When workflowPending is false, workflowPendingEvidence is intentionally empty; use workflowObservationCoverage and workflowObservationSkippedBytes to tell a full scan from a bounded head/tail recovery of a large session log. Treat workflowObservationUncertain: true as a fail-closed pending state: skipped-middle history cannot prove current workflow completion or current model, effort, or permission posture. A tail checkpoint must complete a full replay before the MCP reports restored certainty.
• Treat C-m, C-j, KPEnter, and other documented Enter equivalents as submissions. They use the same pending-workflow gate as Enter and Return.
• Do not infer workflow completion from a final assistant record alone. Keep waiting until workflowPending clears, handle a bounded timeout, or inspect and deliberately authorize a force action.
• Treat tool_use as in progress. Check textTruncated, textSha256, and textCharacters before assuming a large report was returned in full. Use get_claude_result with resultId for exact chunks until hasMore is false.
• Never type over a busy or non-empty composer unless the user deliberately authorizes an inspected force action.