The spec beside the agent

spekterm runs Claude Code sessions for each of your repositories in one window, and shows the OpenSpec change each one is working on — proposal, design, tasks, specs — right next to the terminal.

Download Read the docs

Builds are available for Linux (x86_64) and for macOS on Apple Silicon. Windows and Intel Macs are not supported yet. Early and actively developed — expect rough edges.

spekterm with a Claude Code session in the conversation view, next to the side panel showing the tasks of the OpenSpec change the agent is working on. — A Claude Code session next to the change it is working on: the tasks update as the agent checks them off. Screenshots show illustrative example content.

Not four terminal tabs and an editor

Running agents across several repositories usually means a stack of terminal tabs, plus an editor you switch to just to read the spec. spekterm puts each repository’s sessions in one window and keeps the spec where you can see it: the side panel understands OpenSpec, so it shows the change the agent is working on and follows along as the agent writes to disk.

A side panel that knows OpenSpec

This change

The change’s proposal, design, tasks, and specs as tabs, with task progress. It follows the session you are looking at.

Browse, Graph, Timeline

Every spec and change in the repository, how they relate, and when each change moved.

Worktrees included

Changes in the repository’s git worktrees appear alongside the main checkout’s.

Continue in one click

Hand the next artifact to the agent with OpenSpec’s continue command, from the change itself.

The side panel maximized over the main stage, showing a graph of the repository's specs and the active and archived changes that touched each one. — Maximize the side panel to see how every spec and change relate. Screenshots show illustrative example content.

Sessions that last

A shell session showing git log and the change's files, next to the side panel showing the change's proposal. — Real terminals, several per repository, beside the change's proposal. Screenshots show illustrative example content.

Real terminals — claude and your login shell in real ptys, several per repository, git worktrees included.
They survive a restart — claude sessions resume their conversation; shells come back with the previous screen replayed, in their last directory (on macOS, in their folder).
Hibernate what you are not using — by hand or after a day idle, a session ends its process and waits, dormant, until you wake it.

Read the agent, not just its terminal

Switch an agent session to the conversation view to read the exchange as messages and tool calls. It is built from the agent’s own transcript and hooks — spekterm never scrapes the screen — and the terminal is always one click away.

Work that arrives on its own

The inbox with three Slack mentions waiting, each set to open in the repository its routing picked: api-server, or web-app for the one from #frontend. — Slack mentions waiting in the inbox, each ready to open as a session in the right repository. Screenshots show illustrative example content.

Inbox — when someone mentions you in Slack, it lands in the inbox; accept it to get a Claude Code session in the repository you choose, with the context filled in.
Handoffs — an agent can hand work to another repository’s agent. spekterm opens the session, and you see both ends of the handoff until the work is reported done.

A session that handed work to two others: the rail marks each one's state, and the handoff brief of the finished one shows its task and the result it reported. — Both ends of a handoff: the rail shows who handed what to whom, and the brief keeps the task and its result. Screenshots show illustrative example content.

How it works

Add your repositories to the workspace.
Start a Claude Code session in one of them — or a shell, or both.
Follow the change in the side panel while the agent works, and step in whenever you want.

Local-first, open source

spekterm is a desktop app: your repositories, sessions, and settings stay on your machine. It has no account, no telemetry, and no update check. The programs it starts for you — the claude CLI and the openspec CLI — make their own connections; Data and network lists exactly what connects where. spekterm is MIT-licensed, and its source is on GitHub.

Built on spek

spek is spekterm’s sibling project: an open-source, read-only viewer for OpenSpec content, from the same maintainers — in your browser, in VS Code, in a JetBrains IDE, or as a static page your CI builds. spekterm’s side panel stands on spek’s work:

The engine that reads OpenSpec — scanning specs and changes, task progress, and worktree aggregation come from spek’s core package, @spekjs/core.
The Graph and the Timeline — the same components spek draws, from its @spekjs/ui package.
The mark — spekterm’s icon is spek’s S with a terminal prompt beside it.

The side panel itself is spekterm’s own, made for a narrow column next to a terminal. Use spek to read specs where you already work; use spekterm when you drive agents across repositories and want the spec beside them. They read the same files, and neither needs the other.

Meet spekWhat spek shows, and how to get it for your editor, your browser, or your CI.

Questions

How is this different from running Claude Code in a terminal?

Do I need OpenSpec?

Is my code sent anywhere?

Install and first steps

Download

From the latest GitHub release: an AppImage for Linux, a .dmg for Macs with Apple Silicon.