Roadmap
Where Boitata is headed. Checked items are done.
Sprint 1: Foundation
- Provider trait with multi-provider support
- Agent loop with context management
- Tool registry and first built-in tools
- File system tools (read, write, list)
Sprint 2: Tools
- Code operations (cargo check, clippy, fmt, test, add)
- Search tools (ripgrep integration)
- Git operations (status, diff, commit, branch)
- Command execution with safety checks (timeout, output cap, opt-out)
Sprint 3: MCP Integration
-
MCP client implementation (via
rmcp) - Tool discovery and registration
- Remote transport (Streamable HTTP) and stdio
- Resource access for context gathering
Sprint 4: Blueprint System
- Hybrid deterministic/agentic workflows (agent/tool/script/human node graphs)
-
YAML blueprint definitions (
--blueprint <path>to a user-provided.yaml) -
Example blueprints under
examples/blueprints/(default,fix_lint_errors,fix_test_failure,setup_devbox,human_approval,containerized_task) - Parallel super-steps (fan-out / fan-in), in-memory checkpoint and retry, human-in-the-loop
Sprint 5: Interfaces
- Cargo workspace of focused crates (core / agent / orchestrator / cli / server)
- HTTP/SSE server with an embedded React web UI for task monitoring
-
CLI
--remotemode: schedule a task on a server and stream its progress
Sprint 6: Sandboxed Execution
-
Container blueprint nodes (
provision/checkout/exec) via Docker, with automatic teardown at run end -
Sandboxbackend trait so other backends can slot in -
boitata-agentas an Agent Client Protocol (ACP) server and client (boitata-acp) -
agent_sandboxnode: run the agent inside a sandbox over ACP -
Firecracker microVM
Sandboxbackend (ACP over vsock) and a rootfs image - End-to-end: a task spins up a VM with the code, its deps, and an agent that edits, compiles, and tests inside it
Later
- Container/VM hardening (resource limits, dropped capabilities, network policy)
- Multi-tenant authentication and per-run credential isolation
- Snapshot/restore for retries; a durable task queue