← ClaudeAtlas

rail-operatorlisted

Operate and inspect local Claude Code Remote Control sessions through the Rail Connector MCP. Use when the user asks Codex to start, list, search, find, inspect, resume, continue, fork, prompt, wait for, capture, rename, archive, reconnect to, or stop Claude; requests Claude bypassPermissions or Ultracode; or needs multiple Codex agents to share persistent Claude sessions safely.
SNComrade/Rail-Connector-MCP · ★ 0 · AI & Automation · score 68
Install: claude install-skill SNComrade/Rail-Connector-MCP
# 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. - 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 `tool_use` as in progress. Check `textTruncated` before assuming a large report was returned in full. - Never type over a busy or non-empty composer unless the user deliberately authorizes an inspected `force` action. ## Permission And Effort Intent Use `permissionMode: "dontAsk"` for report-only work when the installed CLI advertises it, pa