Roadmap
Make the quiet runtime stronger
The first version proves the shape: Docker-first turns, SQLite project truth, mailbox scheduling, ToolHost audit, and WebUI observability. The next work should harden those boundaries.
Near Term
Runner event streaming
Stream model deltas and tool call state from the container to Suzumio while a turn is running.
Container cleanup policy
Keep failed containers for debugging, auto-remove successful containers when configured, and expose cleanup commands.
Safer Docker runtime
Add CPU, memory, network, user, read-only mount, and capability controls to backend config.
Better WebUI
Add filtering, artifact previews, resolved config view, turn input/output view, and live SSE updates.
Agent and Model Layer
- Improve AI mode tool-loop handling and streamed outputs.
- Add durable per-agent context summaries without letting the runner own project state.
- Add structured runner events for model fallback, usage, finish reasons, and failures.
- Support profile-level model defaults and per-agent overrides.
Tools
- Move from built-in core tools to registered toolpacks.
- Add approval-required tools for git push, PR creation, and high-risk shell actions.
- Add domain-specific profiles such as verification, code review, research, and benchmark execution.
- Add artifact read/download routes and hash verification commands.
Scheduler
The default scheduler should remain non-preemptive. Future schedulers can be added behind an interface, but they should not weaken the default quiet semantics.
- Expose a scheduler decision log.
- Add manual wake and manual cancel operations.
- Add crash recovery for running turns whose containers disappeared.
- Add project-level concurrency limits.
Security
- Add user-facing API authentication.
- Redact secrets in config snapshots and logs.
- Introduce least-privilege container defaults.
- Keep committed examples sanitized: no real API keys, real gateways, or private provider names.
Documentation
- Add a complete config schema reference generated from the TypeScript/Zod schema.
- Add diagrams once the backend contract stabilizes.
- Add cookbook examples for formalization, software development, research, and benchmark projects.
- Keep English and Chinese pages aligned as API and CLI behavior changes.
Non-goals For Now
- No Kubernetes runtime until Docker-first semantics are stable.
- No complicated workflow DSL before mailbox turns and toolpacks are reliable.
- No default in-process runner path; isolation remains the baseline.
- No automatic project-manager chatter, progress nagging, or heartbeat prompts.