Kore — Development skill for Claude Code

kore

Manage **kore sessions** — interactive Claude Code CLI running inside `tmux` across one or more machines — and watch/drive them from a **web dashboard**, or expose them to an agent as **MCP tools**. One command to start, no environment setup, stdlib only.

A "kore session" is a tmux session named `kore-` on a machine running `claude` interactively. The engine starts/stops those sessions, captures their panes, and types into them over tmux (`send-keys` / `capture-pane` / control-mode `attach`).

Server and client

kore has an explicit two-role model — there is no transport to choose and nothing is hardcoded:

• kore server starts the central node: the dashboard, the engine, and the agent registry. The server is also a worker, so on a single machine kore server is all you need — the engine runs that host's tmux commands locally.
• kore client --server --token joins another machine as a worker. You don't type that line by hand: the server prints it (k3s / tailscale style), and you paste it on the new machine. The client runs a small stdlib agent that registers itself into the roster and answers the server over HTTP.

The engine routes **per node**: a command for the server's own host runs locally; a command for a client runs over HTTP against that client's agent. No Ray, no shared filesystem, no cluster manager.

browser ─HTTP─▶ server.py ─▶ koreops.py ─▶ kore-bridge.py ─┬─self──▶ subprocess on the server host ─▶ tmux kore-
 xterm.js       (WB token)   (write door)  (engine)         │
 terminal                                                   └─client▶ kore-agent (on a client) ─HTTP─▶ tmux kore-
                                       agent registry ◀── each client's agent POSTs /api/agents/register every ~15s

**Env naming:** every setting is a `KORE_*` variable (`KORE_AGENT_TOKEN`, `KORE_NODE_IP`, …). This is the only spelling the code reads.

Quickstart (one machine, zero con