Halyard Fleet

Halyard Fleet

[](https://github.com/alperarabaci/halyard-fleet/actions/workflows/ci.yml) [](LICENSE) [](https://www.python.org/downloads/)

Halyard Fleet puts your coding agent's permission prompt on your phone.

When Claude Code or Codex wants to run something, you see the command, the project it came from, and how risky it is — then you allow or deny from Telegram. You can also send new instructions into the running session and read its replies there. And when a turn dies on a server error the desk would otherwise swallow — an overloaded model, a usage limit hit mid-run — that reaches you too, instead of the session just going quiet.

It runs on your own machine. No open ports, no exposed API, nothing to log into.

Nothing is approved by accident: every failure — a crash, a timeout, an unreachable control plane — denies. Two things go through without a person, both empty until you fill them in: writes to paths you named, and tools you named. Every one is written to the audit log with the pattern that allowed it.

**Runtimes:** Claude Code, Codex  ·  **Channel:** Telegram  ·  **Tested on:** macOS

Why it exists

Remote desktops, terminal streaming and mobile IDEs all try to move *the machine* to your phone. Halyard moves *the decisions* instead.

The user should not operate the computer remotely. The user should manage the agent's decisions, direction, state, and coordination.

You are not typing commands on a phone. You are answering the questions your agent would otherwise be blocked on, from wherever you are.

Quick start

1. Create a Telegram bot

Message [@BotFather](https://t.me/BotFather), send `/