The spec beside the agent

Linux builds are available today. macOS and Windows are not supported yet. Early and actively developed — expect rough edges.

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.

Real terminals, several per repository, beside the change's proposal. Screenshots show illustrative example content.

Sessions that last

• 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 in their last directory with the previous screen replayed.
• 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

A Slack mention waiting in the inbox, 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.

How it works

1. Add your repositories to the workspace.
2. Start a Claude Code session in one of them — or a shell, or both.
3. 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.

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

Download for Linux (AppImage)

Linux builds are available today. macOS and Windows are not supported yet.

From the latest GitHub release. Early and actively developed — expect rough edges.