Thomas

Roadmap

Thomas Roadmap

Thomas starts as a local Windows AI workspace. The roadmap keeps the current core separate from the private phone layer and the longer Thomas OS direction.

Read the journeyDownload Windows build

Current focus

Pre-alpha

Windows-first public release path, with Infinite and Thomas OS still on the roadmap.

Where things stand

Windows is the primary public release path.

Approvals, plugins, launchers, and workspace surfaces are active in the codebase.

Research and evolve loops are expanding longer-running work.

Three phases

Core first, then Infinite, then OS.

Phase 01

Thomas Core

Current focus / Pre-alpha

Shipping now

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

Thomas already has approval gates, release notes, plugin runtime surfaces, and local launchers. The next step 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, release notes, plugin runtime surfaces, and local launchers. The next step is making that stack feel coherent and dependable.

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

  • Approval-gated execution
  • Command rules
  • Release-linked checks

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

  • Tracked research work
  • Evolve workflow
  • Presence monitor