teemd Status
Build Status

teemd

as of 19 Sep 2026

teemd is a local desktop application: a coordinator that runs a supervised crew of AI builders and reviewers against your own Claude Code / Codex sessions, with an independent review gate before anything is kept. The engine, the review-and-repair loop, and the desktop app surface are built and internally verified. It is not yet publicly available — today it runs only as internal builds the founder tests directly.

This page changed what it tracks. It previously followed an earlier, cloud-hosted build of teemd. That build has been paused in favor of a new, local-first architecture — the app now runs on your own machine and your own AI provider sessions, with no server backend of its own. This page now tracks that build going forward.
3 / 5roadmap phases complete · usable app active
2model-provider families supported (Claude, Codex)
Internalfounder-tested only — no public release yet
19 Sepstatus snapshot updated

Shipped & verified

on main
Coordinator holds context across a session merged
The in-app coordinator now keeps the full conversation in view turn to turn, replies in its own voice instead of canned messages, and enforces a real deny-capable guard so it cannot read outside the project it was given. Internal build only — not yet part of a public release.
Durable delivery history merged
Every delivery — finished, failed, or cancelled — is now recorded to a durable history the coordinator can read back, so earlier work stays available for reference within a project. Internal build only.
Live, attributed crew view merged
The crew view was rebuilt to show real actions as they happen — who is working, on what, and the actual steps taken — rather than a simulated status display. Internal build only.
Desktop app icon finalized merged
The desktop application's icon and window branding are finalized and wired throughout the app.
Hardened onboarding & CLI detection merged
First-run onboarding now runs a hardened, token-free scan to detect the CLI tools the coordinator uses, with safer defaults throughout the flow.
Status site & deploy pipeline verified end to end
This status page has its own repository and deploys automatically on merge.

Roadmap to completion

dependency-ordered
✓

Foundation

done

Role definitions, model-provider configuration, and evaluation baselines for the coordinated-crew approach are complete.

✓

Engine & crew

done

A real engine coordinates builder and reviewer sessions across two model-provider families, running on your own subscriptions rather than a hosted backend.

✓

Delivery review loop

done

Independent review, a cross-provider verification gate, and a repair cycle before anything is kept are built and proven end to end.

4

Usable application

active

The desktop app itself: project browsing and editing, a real terminal and preview, a live view of the crew at work, and a coordinator that keeps context across a session. In active development.

5

Production-quality proof & release

not started

Broader validation, outside testers, and a public release are the remaining steps before this reaches anyone beyond the founder.

How to read this. "Done" means merged and verified on the end state — not "a step reported success".