iflow-mcp_yiwenlu66-piloty

<p align="center"> <img src="assets/logo.png" alt="PiloTY logo" width="220" /> </p> # PiloTY PiloTY (PTY for your AI Copilot) is an MCP server that gives an agent a persistent, interactive terminal. If you have used Claude Code / Codex to run shell commands, you have probably hit the same wall: tool calls tend to be stateless. Each call starts "fresh", so environment variables disappear, interactive programs cannot be driven reliably, and long-running processes get cut off or orphaned while the agent is thinking. PiloTY exists to make the agent's terminal behave more like a human's: start something in a real terminal, come back later, and keep going. Warning: PiloTY exposes unrestricted terminal access. Treat it like giving the agent your keyboard. ## What it enables - Long-running commands: builds, installs, migrations, test suites. Start once, check output later. - Log monitoring: `tail -f`, `journalctl -f`, `kubectl logs -f`, CI logs, service restarts. - "Vibe debugging": keep a REPL/debugger open while the agent reads code and tries ideas (`python`, `ipython`, `pdb`). - Privileged operations: handle interactive password prompts (`sudo`, SSH passwords, key passphrases). - SSH-based devops: keep a remote login session alive across tool calls; run remote commands in the same shell. - Terminal UIs: `less`, `man`, `top`, `vim` can work, but cursor-heavy programs often require screen snapshots instead of plain text output. ## Quickstart PiloTY is meant to be launched by an MCP client over stdio. Add it to Codex CLI as an MCP server: ```bash codex mcp add piloty -- uvx --from git+https://github.com/yiwenlu66/PiloTY.git piloty ``` If you prefer SSH-based Git fetch: ```bash codex mcp add piloty -- uvx --from git+ssh://git@github.com/yiwenlu66/PiloTY.git piloty ``` If you already have a local clone: ```bash codex mcp add piloty -- uv --directory /path/to/PiloTY run piloty ``` Run the server command directly (without adding it to an MCP client): ```bash…