Document the post-3.1 milestones needed to make the stable workspace product feel natural in chat-driven LLM interfaces.

Add a follow-on roadmap for model-native file ops, workspace naming and discovery, tool profiles, shell output cleanup, and use-case recipes with smoke coverage. Link it from the README, vision doc, and completed workspace GA roadmap so the next phase is explicit.

Keep the sequence anchored to the workspace-first vision and continue to treat disk tools as secondary rather than the main chat-facing surface.

2026-03-12 21:06:14 -03:00

1.4 KiB

Raw Blame History

`3.6.0` Use-Case Recipes And Smoke Packs

Status: Planned

Goal

Turn the five target workflows into first-class documented stories and runnable verification paths.

Public API Changes

No new core API is required in this milestone.

The main deliverable is packaging the now-mature workspace surface into clear recipes, examples, and smoke scenarios that prove the intended user experience.

Implementation Boundaries

build on the existing stable workspace contract and the earlier chat-first milestones
keep the focus on user-facing flows, not internal test harness complexity
treat the recipes as product documentation, not private maintainer notes

Non-Goals

no new CI or scheduler abstractions
no speculative cloud orchestration work
no broad expansion of disk tooling as the main story

Acceptance Scenarios

cold-start repo validation has a documented and smoke-tested flow
repro-plus-fix loops have a documented and smoke-tested flow
parallel isolated workspaces have a documented and smoke-tested flow
unsafe or untrusted code inspection has a documented and smoke-tested flow
review and evaluation workflows have a documented and smoke-tested flow

Required Repo Updates

a dedicated doc or section for each target use case
at least one canonical example per use case in CLI, SDK, or MCP form
smoke scenarios that prove each flow on a real Firecracker-backed path

1.4 KiB Raw Blame History

3.6.0 Use-Case Recipes And Smoke Packs