teemd Status
Build Status

teemd

as of 16 October 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 hosted build service: builds run on your machine. This page now tracks that build going forward.
3 / 5roadmap phases complete · usable app active
2frontier families (Claude, Codex) + open-weight via your own Ollama setup
Internalfounder-tested only — no public release yet
16 Octstatus snapshot updated

Launch plan

Windows first
Windows launch: coming soon
A beta will run before launch

Completed

merged & checked

Desktop app features listed here are in internal builds and not yet publicly released.

Codex sign-in inside the app merged
On Windows, teemd now installs and manages its own copy of the Codex command-line tool. You can sign in to Codex from inside teemd, and the app confirms when the sign-in has succeeded. Internal builds only.
Clear messages when Jen can't reply merged
When Jen, the coordinator, can't answer, it now tells you why: you are signed out, a usage limit was reached, the model is unavailable, the provider had an error, or the request timed out. It falls back to a general message only when the cause can't be identified. Onboarding also names the sign-in step you need. Internal builds only.
Work recovered after a crash or restart merged
If teemd closes or crashes while a delivery is on hold, the held work is restored when you reopen the app. Anything teemd has to set aside during recovery goes to a recovery folder you can open from the File menu, instead of being thrown away. Internal builds only.
Account sign-up and free trial merged
Your first sign-in creates your teemd account and workspace and starts your free trial. Each account gets one trial. Installed builds are set up to use teemd's account service, and you sign in before starting a build. Internal builds only.
Guided tool setup merged
Onboarding now has a "Set up your tools" checklist that walks you through what teemd needs. Settings can check that Codex is set up correctly and, if you agree, repair it. Internal builds only.
Planning fix for requests that name files merged
An open-ended request that also mentions a few files is no longer wrongly limited to just those files and refused at planning. Internal builds only.
Audit log in Settings merged
A new Audit log section in Settings shows a proof record for each delivery, alongside a stream of audit events. Internal builds only.
Broader secret masking merged
teemd now recognises and masks more kinds of secrets, including cloud access keys, in what the app shows and records. Internal builds only.
Signed desktop builds & update engine merged
The desktop app is produced as a code-signed Windows installer, and the release process checks that each installer is signed before publishing. The update engine is built into the app; the in-app update experience is coming soon. Internal builds only — no build has been published yet.
Full-pane editor & File menu merged
The Editor now fills the pane with a file tree alongside it, and a File menu covers new, open and close project, plus recently opened projects. Internal build only.
Choose the model for each crew role merged
A crew picker lets you choose which model family runs each role. Open-weight families (GLM, DeepSeek) are available as crew and review options alongside Claude and Codex, through your own Ollama setup and account. teemd does not host or supply any models. Internal build only.
Work is kept when a model fails merged
If a model or provider fails mid-delivery — including a sign-in failure — teemd now pauses and keeps the work instead of losing it, and the delivery can then be resumed. Internal build only.
Outages count as failures merged
When a supporting crew step's model provider is down, that step now counts as a failure rather than a false success. Internal build only.
Coordinator read guard hardened merged
The coordinator's file-reading guard has been hardened against attempts to read credential and secrets files. Internal build only.
Account sign-in merged
Account sign-in is available in the app. Internal builds only.
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 live verified end to end
This status page has its own repository and deploys automatically on merge.

In progress & coming soon

before launch
Working toward any language or stack in progress
teemd will detect your project and use its own build and test commands. You'll confirm the check plan before work starts, and anything that can't be checked will be clearly labelled "unverified", never shown as a pass.
Resume after Hold in progress
When you put a delivery on hold at the review step, teemd will keep its work and you'll be able to resume it later.
Confirm the scope of a request in progress
Jen will show which parts of your project a request may change, and you'll confirm that scope before the build starts.
Codex as Jen's model in progress
You will be able to run Jen, the coordinator, on Codex as well as Claude. Built; end-to-end testing on the installed app is still to come.
Redesigned interface: Technical Dark in progress
The interface will be redesigned, with Technical Dark as the new default look.
Automatic failover coming soon
If a model fails during a delivery, teemd will move the work to another available model automatically instead of waiting for you to resume it.
More builds at once, with your own API keys coming soon
You'll be able to run more than three builds at the same time by adding your own API keys.
In-app updates coming soon
You'll be able to see when a new version of teemd is ready and update it from inside the app.
Reliability hardening coming soon
teemd will recover more smoothly from dropped network connections, let you sign back in to your AI tools from inside the app, and handle a nearly full disk more clearly.

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, a coordinator that keeps context across a session, and account sign-in. In active development. Work toward support for any language or stack, and the redesigned interface, is under way.

5

Production-quality proof & release

in progress

Signed desktop builds exist and the update engine is built into the app. A beta and the public launch come next (see the launch plan above). Outside testing and a public release have not happened yet.

How to read this. "Completed" means merged and checked. Desktop app features are in internal builds and none are publicly released yet; only items tagged "live", such as this status site, are public. "In progress" means being built, reviewed or tested now. "Coming soon" means planned. A roadmap phase is "done" only when it is merged and verified on the end state, not when a step reports success.