Complete the 2.6.0 workspace milestone by adding explicit host-out export and immutable-baseline diff across the CLI, Python SDK, and MCP server. Capture a baseline archive at workspace creation, export live /workspace paths through the guest agent, and compute structured whole-workspace diffs on the host without affecting command logs or shell state. The docs, roadmap, bundled guest agent, and workspace example now reflect the new create -> sync -> diff -> export workflow. Validation: uv lock, UV_CACHE_DIR=.uv-cache make check, UV_CACHE_DIR=.uv-cache make dist-check, and a real guest-backed Firecracker smoke covering workspace create, sync push, diff, export, and delete.
2.3 KiB
2.3 KiB
Task Workspace GA Roadmap
This roadmap turns the agent-workspace vision into release-sized milestones.
Current baseline is 2.6.0:
- workspace persistence exists and the public surface is now workspace-first
- host crossing currently covers create-time seeding, later sync push, and explicit export
- persistent PTY shell sessions exist alongside one-shot
workspace exec - immutable create-time baselines now power whole-workspace diff
- no service, snapshot, reset, or secrets contract exists yet
Locked roadmap decisions:
- no backward compatibility goal for the current
task_*naming - workspace-first naming lands first, before later features
- snapshots are real named snapshots, not only reset-to-baseline
Every milestone below must update CLI, SDK, and MCP together. Each milestone is also expected to update:
README.md- install/first-run docs
docs/public-contract.md- help text and runnable examples
- at least one real Firecracker smoke scenario
Milestones
2.4.0Workspace Contract Pivot - Done2.5.0PTY Shell Sessions - Done2.6.0Structured Export And Baseline Diff - Done2.7.0Service Lifecycle And Typed Readiness2.8.0Named Snapshots And Reset2.9.0Secrets2.10.0Network Policy And Host Port Publication3.0.0Stable Workspace Product3.1.0Secondary Disk Tools
Definition Of Done For The Roadmap
The workspace product is ready to leave beta when:
- the public contract is workspace-first rather than task-first
- an agent can inhabit a sandbox through shell, exec, service, diff, export, snapshot, reset, and explicit host-crossing operations
- the main docs lead with the workspace product, not one-shot VM execution
- the remaining deliberate deferrals are secondary disk tools rather than core workspace features