Roadmap
Everything below is dated by priority, not calendar. If a feature has a date, that's because the release plan is real. Everything else moves when it's ready.
Legend: shipping
experimentalplannedNow
Work we're actively simplifying or tightening.
- Model catalog as a first-class file.
docs/reference/models.yamlis the single source the CLI and website both read.shipping - TUI behavior contract. Pin down scrollback, resize, tool-state rendering, and ASCII fallback in a single document so the behavior doesn't drift between releases. planned
- Session JSONL event schema. Typed events covering tool state transitions, file edits, runtime events, and errors.planned
Next
The shape is clear; the work isn't in main yet.
- Provider adapter contract.
ProviderAdapter+ProviderConfig+ModelConfig+CredentialStore. Custom providers viaadapter: openai+compatibility: <profile>. planned - Cloud runtime polish. Cloud-provided browser CDP, cloud-side artifact retrieval, end-of-session diff auto-apply, in-session
/runtime switch <name>, and runtime event persistence toconversation.jsonl. Daytona / Sprites / Modal already ship — this is the followup. planned - Docker sandbox polish. Mount ergonomics, background job handling, state preservation across sessions. experimental
- Web extraction flows. First-class pipelines for page → structured data, built on top of the existing web tools. experimental
Later
Directions we want to head once the foundations land.
- More cloud runtimes. E2B, hopx, Northflank, custom SSH or container workers — same
RuntimeFactory.registeradapter pattern proven by Daytona, Sprites, and Modal. planned - Replay UI. A dedicated surface that reads
conversation.jsonland renders it step-by-step with diffs, tool-call collapse, and time scrubbing. planned - Provider marketplace. User-submitted providers + a curated remote catalog. The remote-fetch and bundled-vs-remote merge half already ships as
glue catalog refresh(overlay at~/.glue/cache/models.yaml); what's still planned is the submission and curation pipeline. planned
Removed
These were in the tree and are coming out — don't plan around them.
- Interaction modes.
code/architect/askselector. - Plan-mode UI. The separate
/planssurface andPlanStore. - OTEL / Langfuse observability. JSONL sessions are the single durable log.