Thales Maciel
f504f0a331
Make persistent workspaces capable of running long-lived background processes instead of forcing everything through one-shot exec calls. Add workspace service start/list/status/logs/stop across the CLI, Python SDK, and MCP server, with multiple named services per workspace, typed readiness probes (file, tcp, http, and command), and aggregate service counts on workspace status. Keep service state and logs outside /workspace so diff and export semantics stay workspace-scoped, and extend the guest agent plus backends to persist service records and logs across separate calls. Update the 2.7.0 docs, examples, changelog, and roadmap milestone to reflect the shipped surface. Validation: uv lock; UV_CACHE_DIR=.uv-cache make check; UV_CACHE_DIR=.uv-cache make dist-check; real guest-backed Firecracker smoke for workspace create, two service starts, list/status/logs, diff unaffected, stop, and delete.
50 lines
2.4 KiB
Markdown
50 lines
2.4 KiB
Markdown
# Task Workspace GA Roadmap
|
|
|
|
This roadmap turns the agent-workspace vision into release-sized milestones.
|
|
|
|
Current baseline is `2.7.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
|
|
- multi-service lifecycle exists with typed readiness and aggregate workspace status counts
|
|
- no 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
|
|
|
|
1. [`2.4.0` Workspace Contract Pivot](task-workspace-ga/2.4.0-workspace-contract-pivot.md) - Done
|
|
2. [`2.5.0` PTY Shell Sessions](task-workspace-ga/2.5.0-pty-shell-sessions.md) - Done
|
|
3. [`2.6.0` Structured Export And Baseline Diff](task-workspace-ga/2.6.0-structured-export-and-baseline-diff.md) - Done
|
|
4. [`2.7.0` Service Lifecycle And Typed Readiness](task-workspace-ga/2.7.0-service-lifecycle-and-typed-readiness.md) - Done
|
|
5. [`2.8.0` Named Snapshots And Reset](task-workspace-ga/2.8.0-named-snapshots-and-reset.md)
|
|
6. [`2.9.0` Secrets](task-workspace-ga/2.9.0-secrets.md)
|
|
7. [`2.10.0` Network Policy And Host Port Publication](task-workspace-ga/2.10.0-network-policy-and-host-port-publication.md)
|
|
8. [`3.0.0` Stable Workspace Product](task-workspace-ga/3.0.0-stable-workspace-product.md)
|
|
9. [`3.1.0` Secondary Disk Tools](task-workspace-ga/3.1.0-secondary-disk-tools.md)
|
|
|
|
## 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
|