Roadmap vs journey
Roadmap
The roadmap is the forward-looking page: where Thomas is headed, what the three big phases are, and what each phase is trying to unlock.
Open the roadmapJourney
Track what has shipped, what changed in the architecture, and what constraints still define the product.
Why Thomas exists
AI tools become risky when important actions disappear into a black box. Thomas keeps local work visible and approval-based.
The goal is simple: let AI help with real work while you can still see what is about to run and decide whether to approve it.
What we won't compromise on
- Risky actions need a visible approval step.
- Local-first operation comes before remote convenience.
- Public copy matches the release people can actually download.
Milestones
2026-02
Execution boundary enforced
Request parsing and approval gates now sit in front of every execution path.
2026-02
Command map
Command families are listed clearly so the public surface can show what exists and what is still forming.
2026-02
Release-linked observability
Downloads, release notes, and runtime logs are being pulled into a clearer support path.
2026-03
Gateway and CLI alignment
API routes and CLI commands are moving toward the same approval and validation path.
What's next
- Expand plugin sandbox and policy checks.
- Improve release reproducibility without adding complexity.
- Keep the control plane as a view over local execution, not a standalone agent.
Current boundaries: Local commands still need approval. Unfinished surfaces stay marked as unfinished. Automation does not hide risky behavior.
Thomas Infinite
The mobile companion app for Thomas. Still in development.
See what Thomas is doing from your phone. Queue work, check results, and approve actions while the main Thomas runtime stays in charge.
What stays local
Infinite is a UI surface, not a standalone runtime.
What can be remote
Tokened transport and pairing are supported; key rotation is still in progress.
What it won't do
Infinite never runs commands outside the Thomas core path.