termic.dev
Documentation menu

Roadmap

What is committed to and what is only an idea: a mobile companion app is planned; orchestration, Windows, a scoped MCP control plane, ambient status and theme imports are ideas nobody has decided on yet.

Termic is built in the open and used daily by the person building it, so the roadmap tracks real friction rather than a marketing plan.

There are two lists here, and the difference between them is a commitment. Planned is what will be built, and each item has an issue on GitHub labelled planned where its progress lives. Ideas are not committed to. Several are detailed enough to build from, but none of them is decided, and they deliberately have no tracking issue, because an issue implies someone intends to do it.

An approved idea becomes a spec and gets an issue at the same time. That is the whole promotion path.

Planned

  • Mobile companion app. (#165) Check on and steer tasks while away from the Mac.

Ideas

  • MCP endpoint, phases B1 and B2. Phase A shipped: the stateless loopback endpoint, the settings surface, one-click client setup. What is left is the per-task bearer token that answers which task is calling and what it may do, which is the narrowest grant a sandboxed agent could be given. The 2026-07-28 revision of the MCP specification reopened enough of that design that it is an idea again rather than a plan.

  • Intentional agent-driven orchestration. The plumbing already ships: an agent can spawn a task and wait on it, prompt another, read its result and branch on the exit code, via the CLI or MCP. What is missing is intent, and an opinion about shape (fan out, queue behind, supervisor and workers).

  • Windows support, then Windows prebuilts. Linux AppImage CI is live; the Windows installer is the matching matrix entry, and it depends on the app compiling on Windows at all. The existing audit is a prediction, not a build.

  • Ambient agent status. A Dock tile, or a strip beside the Dock, showing what every agent is doing without bringing the window forward.

  • Import Warp and Ghostty themes. Termic has a native JSON theme format, but two large theme ecosystems already exist and neither is ours. Scan both directories, translate, and let people pick from the library they already collected.

  • Linear integration. GitHub and GitLab already work: start a task from an issue, open the PR from the app, watch it from the right panel. Linear is the same shape and is not built.

  • A native Linux sandbox. Linux itself ships today (a signed AppImage every release) and Docker mode already gives it a container cage. What is missing is a native equivalent of the macOS Seatbelt, via bubblewrap or Landlock, so the Shield toggle means something without Docker installed.

  • Wider Linux reach. ARM Linux builds and a Flathub submission, alongside the x86_64 AppImage that ships today.

  • Opt-in usage telemetry. Anonymous, off by default, one toggle: which features are used and how often, plus crash reports. No code, no prompts, no file paths, no agent output, no project names.

  • Termic in the official Homebrew cask repository. Today the install path is the project’s own tap, so it takes a brew tap first. Upstream would make it plain brew install --cask termic. The cask is ready and the pull request is filed; it is closed on one thing only, Homebrew’s notability bar for an author submitting their own software, which stars are the realistic way to clear.

Recently shipped

Things that were on this list and are now in the app:

The full list is in the changelog.

How priorities get set

This list moves based on what gets used and what gets reported. If a missing feature is blocking you, saying so (via the in-app email button or a GitHub issue) is the most direct way to move it up.

Last reviewed: September 7, 2026