Roadmap

INFO

Everything on this page is Planned. Dates are targets, not commitments. The whitepaper says the same of its own schedule: "These periods are planning targets and do not establish completion."

Near term: the beta

Item	What changes for you
Signed and notarized build	No more right-click → Open. macOS keeps your permission grants across updates.
Points live	The points server connected in every build, so you can activate your node and see verified work counted.
Verified email sign-in	Sign in with an email you confirm, so your node and points are tied to you across devices. Today the optional email is stored unverified.
Claude Desktop extension	A packaged Desktop Extension, replacing today's config entry, and Desktop conversations listed in Vistara alongside your other agents.
Teams	Presence (which workstreams teammates have running, and which are blocked), handoffs to a teammate's Vistara, questions routed to the person who owns the decision, and shared verified results. Teams share state and results. They do not get remote control of each other's machines or agents.

The whitepaper's timeline

The whitepaper (v1.1, September 2026, Section 9.1, Table 13) gives this sequence. Each phase has an exit measure. The order follows need: reliable unattended runs for one person first, then attended and parallel work, then teams, then the market.

Target	Main capabilities	Exit measure
Q4 2026	Production hardening and public rollout of the daemon on Windows, macOS and Linux. Reliable unattended runs across the major coding agents: adapters, stop classification and recovery, wake management, safe checkpoints. Signed mandates with bounded permissions, the policy engine and sandbox, and budgets in the resource governor. Goal specs with check libraries for code; verification V0 to V3; flight recorder and receipts; the morning review on desktop and phone. Points and usage instrumentation for the launch distribution, counted in verified goals and receipts. On-chain primitives for launch: the token, governance staking, the fee router, the receipt anchor and the operator registry, audited before deployment.	Users completing unattended nights on their own repositories; stall recovery rate and morning acceptance rate published; launch-distribution eligibility computed from receipts; contracts live with audit reports published.
Q1 2027	Attended and parallel operation: several goals at once with foreground priority, attention rules in the mandate, the continuous brief, conflict classification, and the Workstate store for daemon-run goals. Check libraries for research, marketing, data and design goals. Quota-window scheduling. Context keeper. Paid individual tier.	Paying users; retention after four weeks; interruptions per accepted goal published; share of goals settled by mechanical checks alone.
Q2 2027	Interactive session state read from harnesses that expose it, so the Workstate covers foreground work. Team tier with shared Workstates, decisions and dependencies; organization mandate and goal templates. Work market on testnet: escrow, verifier of record, hosted verifier, arbitration roster, work records in ERC-8004 format; operator onboarding with USDC bonds.	Workstates handed between people per team per week; test jobs settled end to end by mechanical checks; dispute process exercised.
Q3 2027	Enterprise tier: organization policy floor, approved models and tools, per-team budgets, roles, audit export, self-hosted services. Work market on mainnet. Open-source maintainer program. First goal templates published for buyers.	Enterprise pilots running self-hosted; settled payments from distinct funded accounts; independent operators with settled history; published dispute statistics.
2028	Goal templates and check libraries for further kinds of work; aggregate performance records by harness and model; additional settlement networks; a published Workstate format for third-party harnesses and tools.	Settled value per month; acceptance rate of market deliverables; third-party tools reading and writing Workstates.

$VSTR in the timeline

From the whitepaper (Sections 5.1 and 5.3):

• Q4 2026: token generation, together with the public release of the daemon and the first contracts on Base: the token, governance staking, the fee router, the receipt anchor and the operator registry.
• Between generation and the escrow launch: no protocol fees and therefore no buybacks.
• 2027: the work escrow launches. It is the only source of protocol fees. Buybacks begin with the first fee the router receives.

The token has two functions only: protocol fees on settled work buy it and burn it, and staked holders govern the parameters that set those fees. Payments in the system are in USDC. The whitepaper states that its allocation and schedules are a proposal and may change before token generation.

How the beta relates to this timeline

The beta took a different first step from the one the whitepaper sequences. The whitepaper starts with goals the daemon runs on its own, unattended, and adds interactive sessions later (Q2 2027). The beta starts with the interactive sessions you already run: it reads their state through hooks and transcripts, and routes their questions to you.

Parts of later phases exist in narrow form today:

Whitepaper item	In the beta
Workstate	Workstate v0 per session and project: status, checks, last change, next step.
Continuous brief	Cards for questions and approvals as they happen.
Mandate and policy engine	A local, unsigned policy file that auto-approves routine work inside the repo.
Verification V1 and V2	Repo checks re-run in a separate git worktree, and a test-integrity diff check.
Handoff	Send work to another agent on the same Mac, or copy it.
Points instrumentation	Signed contributions for verified completions and active days.

Everything else in the table above is not built yet.