Keep the flock in view.
Every Claude Code agent, in one calm place.
episko gives every Claude Code session its own terminal, watches what each one is doing, and gathers them into a single view — so a whole flock of agents is as easy to mind as one chat.
rm -rf node_modules && pnpm install
src/main.tsThe rest of the kit.
The tour is the watching. This is the working gear — what's in the pouch once the flock is actually moving.
Send an agent at an issue.
From the project dashboard, dispatch straight at an open issue: Episko makes the worktree, sends the prompt, and writes a claim to the issue — so a colleague's agent doesn't start the same work twice. When the session ends, the issue is handed back.
One work log, committed.
A generated line per day about what the project did — commits and pull requests, never your spend — written to the repo, so the team reads one history instead of each paying to re-derive it.
Group projects, fold them away.
Name a set — work, side — and collapse it to one line. A folded heading still carries the most urgent glyph it hides, so a tidy-up can't bury an agent waiting on you.
A chain is one row.
A dependsOn chain runs one pane per step but folds into a single row carrying the worst step's status — a failed build reads as a failed chain. Click it and every step tiles the stage.
The whole history, one page at a time.
A commit graph per project — lanes, merges, branch and tag labels — read page by page and fetched as you scroll, so it opens on a huge repo as fast as on a small one.
Every session ever.
Sessions from any terminal — Episko's or not — read from Claude's own transcripts on this machine. Search them, scope them to a project, reopen one where it left off.
Restarts lose nothing.
Episko's launch id is Claude's --session-id, so reopening a session replays Claude's own transcript — nothing captured, nothing to lose. Even a hard reload rebuilds every pane and hands the running processes back, scrollback included.
Wandering agents, noticed.
An agent that moves to another checkout mid-task is spotted — from what it writes and where it runs — and Episko offers the repair: follow it there, or move the conversation back.
Local-first, MIT.
Everything Episko records stays on your machine. In your repo it writes only .episko/ — and asks before creating anything committable. Free and open source.
Gather your flock.
episko is a small native app. Point it at your repos and mind as many Claudes as your limits allow.