Roadmap

Where Slipstream UI is today, what lands in each minor, and exactly what changes at 1.0. Dates are targets, not contracts — scope moves, the guarantees below do not.

0.1.x

Shipping nowcurrent

Foundation — the AI-first contract

  • 48 components (31 core + 17 AI), each with a COMPONENT_MANIFEST
  • MCP server: list/search/get tools + validate_usage
  • shadcn-compatible registry, CLI (init/add/list/diff), /llm markdown + llms.txt
  • Docs: grouped navigation, nine guides, interactive demos, browser-support tables
  • jest-axe suites on every component; manifest schema + TS drift enforced in CI

0.2

Target: Dec 2026

AI surface depth + remaining core gaps

  • Multi-thread primitives (thread list + active-thread contract components)
  • Attachments 2.0: previews, upload progress, multi-file constraints
  • Model selector + queue/plan (todo) surfaces for agent UIs
  • Generative-UI primitive: render agent-described component trees safely
  • Core gaps: date/calendar input, richer Combobox patterns, toast position API
  • validate_usage v2: actionable fix suggestions and whole-tree validation

0.3

Target: Q1 2027

Proof and starters

  • Public Storybook with visual-regression + a11y reports
  • First-class starters: Vercel AI SDK, LangGraph, raw SSE
  • Production app-shell templates (multi-thread workspace, settings)
  • Bundle-size and tree-shaking measurements published
  • Decision guides + honest comparison pages (vs shadcn AI Elements, vs assistant-ui)

1.0

Target: Q2 2027

Stability promise

  • API freeze: breaking changes only in major versions after 1.0
  • Deprecation policy: announce in a minor, remove in the next major, migration note in the changelog every time
  • Published migration guide 0.x → 1.0 with codemods where possible
  • Long-term support statement for the 1.x line

Stability guarantees

Semantic versioning, honestly

Patch = fixes only. Minor = new components/props (backward-compatible unless marked deprecated). Major = breaking, with migration notes. Until 1.0 the minor number may move breaking changes — always listed in the changelog first.

Specs ship with the code

Every component carries a versioned COMPONENT_MANIFEST; prop schemas, TypeScript types, and manifests are CI-checked for drift, so agents and humans see the same truth on every release.

Accessibility regressions are bugs

jest-axe suites run per package in CI. A release never knowingly ships an axe violation; reported a11y issues block the next patch.

Stateless stays stateless

No runtime lock-in will be introduced to core or ai components. Batteries-included conveniences live in optional packages, never in the primitives.

How this stays honest

  • Every release is written up in the changelog — breaking changes and migration steps included.
  • Manifest versions bump with their component, so diffable specs track the API.
  • Items move between releases when reality disagrees with the target window; the table above is updated in the same PR that moves the work.

Shape the roadmap

Missing something? Open an issue with the component or surface you need — the 0.2 list is ordered by what agent-builder demand has surfaced so far.

Versioning policyRequest an item
Was this page helpful?