Roadmap

Thomas Roadmap

Thomas is still pre-alpha. The job right now is to make the core trustworthy, turn that core into a private app network you can carry on your phone, and then push all of that into a real AI-native operating system.

Current build

v0.14.38 / pre-alpha

Current repo state across the March 17-18, 2026 shipping streak.

Where things stand

Approval-gated execution is already live.

Plugin surfaces, launchers, and control-plane pieces are already in the repo.

Research and evolve loops are pushing Thomas beyond one-shot prompting.

Three phases

One route, one active phase at a time.

Phase 01

Thomas Core

Current build / Pre-Alpha

Shipping now

Make local execution trustworthy before the surface area gets much larger.

Thomas already has approval gates, evidence-linked releases, plugin runtime surfaces, and local launchers. The next job is making that stack feel coherent and dependable.

Startup routerApproval gatesDesktop pluginsMy Stuff launcher

Selected phase

Thomas Core

Thomas becomes a dependable local execution layer with enough trust and clarity to support everything that comes after it.

Why this phase matters

Thomas already has approval gates, evidence-linked releases, plugin runtime surfaces, and local launchers. The next job is making that stack feel coherent and dependable.

This is the center of the product: command families, explicit approvals, and release-linked evidence working together.

  • Approval-gated execution
  • Command family contracts
  • Artifact-backed evidence

Research programs, evolve flows, and presence monitoring push Thomas toward a system that can keep making progress without losing visibility.

  • Tracked research artifacts
  • Evolve workflow
  • Presence monitor