markhor

Markhor

Capra falconeri, for coding agents (Zafar, 2026)

Run Claude Code, Codex, OpenCode and more on your Mac or a server, then drive them from any browser, your phone included. It stays light on your machine and never loses what you send.

A markhor's head in faceted teal, horns curling back, drawn in stippled grain on black.
Plate I. Markhor, adult male.
Markhor on a Mac. The Deck lists five chats: one working, one waiting for a yes or no, one stopped, one done. The open chat shows a seven-step plan, three steps done.
Markhor on a phone: chats grouped by project, each with its agent and state.
Plate II. Markhor at work.

Lives on almost nothing.

The markhor gets by on thin grass and scrub, high in the Karakoram. Markhor the app gets by on a few megabytes, and lets your agents rest when you're done with them.

Diet
Claude Code, Codex, OpenCode, Pi, Cursor, and any agent that speaks ACP.
Habitat
Your Mac or a Linux server, reached from any browser. Your phone counts.
Behaviour
Keeps your two most recent chats ready and stops the rest. Holds every message until it lands, exactly once.
Field notes, 25 October 2026
Server at rest2.9 MiB
Five chats streaming at once9.9 MiBpeak
After those five chats finished9.4 MiB
Messages lost or sent twicenoneby design

Measured on one Mac with Claude Code and Opus 5.5, one run each. The method and raw samples live in the repo, under docs/perf.

Raised on two good tools.

Markhor started as a fix for my own setup: I wanted my agents to run lighter on my Mac. It borrows ideas and code from T3 Code and Zeron, and it will keep borrowing. Both are excellent. Go try them too.

T3 Code on GitHubzeron.sh

T3 Codethe idea of one chat for every agent

Zeronthe code behind the phone apps

Markhorlight enough to run anywhere

Fig. 1. Where Markhor comes from.

Bring your agents up the mountain.