Roadmap

How to read this page

The roadmap mirrors the public face of the project only. Detailed engineering state lives in docs/BOARD.md, the iteration records, and the backlog. This page is the short, conservative public summary. If a public claim here ever disagrees with a shipped behavior, the shipped behavior wins until the page is updated.

Shipped in v0.9.1

The following are part of the current published release. They are documented in detail on the Capabilities page and the Safety page.

• Shipped TUI, inline, and print execution modes.
• Shipped Local provider configuration with masked secrets per ADR-023.
• Shipped Built-in coding tools (files, search, code intelligence, Git, http_request, web_search, bash) with permission gating.
• Shipped Session storage, search, cleanup, maintenance, memory consolidation, and exploration ingestion.
• Shipped Runtime Skills from .talos/skills/, ~/.talos/skills/, and inherited parent .talos/skills/, plus shared ~/.agents/skills/ discovery enabled by default. Symbolic-link traversal remains disabled by default.
• Shipped MCP stdio tools and JSON-RPC infrastructure.
• Shipped Read-only loopback dashboard in TUI mode with startup URL/token visibility.
• Shipped Initial talos-runtime embeddable facade (pre-1.0; ADR-024).
• Shipped Explicit local read-only WASM packages selected with --plugin DIRECTORY, without host calls or automatic discovery.

Planned

These items are scoped but not yet shipped. The order below is a sequencing preference, not a release-date commitment.

• Planned cargo install talos-cli --bin talos as a validated Cargo install path. The --path source install works today; crates.io publication is separately gated by the publication matrix and requires explicit maintainer approval.
• Planned Stable 1.0 SDK guarantee for the talos-runtime facade. Gated by REL-002, which requires Talos to perform 100% self-bootstrap development as the primary runtime with recorded evidence. A four-month hardening plan is underway to produce the prerequisites and evidence.
• Planned A bounded document-extraction and save workflow for PDF and Office formats, building on the current http_request / web_search foundation (see WEBFETCH-001).
• Planned Multi-resource tool permission profiles beyond the current ADR-026 foundation.

Research

These items are exploratory. They have no committed timeline and are not presented as shipped. Some are tracked as separate product-differentiation work and will not land in the Talos core runtime at all.

• Research Web control expansion beyond the read-only dashboard MVP. Tracked separately under WEB-001. Remote access, browser automation, web approvals, and web write/action routes are not shipped and are not safety boundaries.
• Research Remote plugin distribution, automatic discovery, host calls, write-capable plugins, and a plugin marketplace. Architecture decisions are accepted (ADR-027/028/029/030) but runtime implementation remains gated by a focused wasmtime dependency and security review. Tracked under PLUGIN-001.
• Research Remote or P2P session control. Tracked under REMOTE-001. A remote-session control surface requires an ADR gate before any prototype work.
• Research Local micro-model decision layer (small on-device model for hints). Tracked under MODEL-002.

Non-goals for v0.9.1

These are explicit non-goals. They are listed so users do not have to discover them by experiment.

• Talos is not a remote multi-user service. There is no remote control plane, no hosted session router, and no remote approval UI.
• Talos is not a marketplace runtime. The Remote plugin distribution, automatic discovery, write-capable plugins, and a plugin marketplace are research only.
• Talos is not a remote web control plane or browser automation product. The shipped dashboard is local, read-only, loopback-only, and token-gated; broader web control remains a separate research track (WEB-001).
• Talos is not an autonomous background daemon. It runs interactively or in print mode; it does not sit in the background waiting for a trigger.
• Talos does not auto-commit, auto-publish, or auto-merge. Git writes happen only through explicit tool or user action.

Engineering status

For the current engineering operating view (Now, Review, Blocked, Next, Done), use docs/BOARD.md and the iteration records. Those are the source of truth for engineering progress; this roadmap is the source of truth for the public boundary.