Roadmap

Amber is a native C++ AI agent runtime and CLI harness with an extensible plugin architecture. The roadmap is about deepening the capability system, improving runtime quality, and making the project easier to use and contribute to, on Linux and macOS.

Current state

Already shipped and in use:

• Linux and macOS support (Apple Silicon distributed builds via Homebrew)
• Plugin / capability architecture: providers, tools, and UI capabilities through one mechanism
• Multi-provider support: Anthropic, Gemini, OpenRouter, DeepSeek, KiloCode, OpenCode, CommandCode, Custom, OpenAI-compatible
• MCP support over supported transports
• Sub-agents with serial and parallel execution
• Context compression with memory/skill extraction
• Context integrity (FNV-1a hash chain)
• Workspace/path confinement and approval-gated side effects
• Benchmark and evaluation harness (amber-bench)
• Interactive TUI and headless CLI

Near term

• Runtime loading of external plugins (dlopen), building on the existing registry and ledger infrastructure
• Semantic search backends, real embedding models for code search
• More provider plugins and provider-specific dialects
• Skills system, authored and learned skills, project-scoped memory
• MCP ecosystem, more servers, richer tooling over the existing client

Mid term

• Runtime quality, hardening the agent loop, plugin lifecycle, and context management under long sessions
• Testing, expanding the benchmark corpus and hermetic regression coverage
• Usability, onboarding, configuration discovery, and the command tree experience
• Documentation, architecture guides, plugin developer guide, and scenario authoring
• External contribution, lowering the barrier to write and ship plugins

Far term

• Long-duration research, tmux integration, days and weeks of autonomous work
• Multi-agent orchestration, sub-agents with shared context, parallel execution at scale
• Self-hosted LLM tooling, local inference, quantized models, VRAM management

Not on the roadmap

Some things amber is not going to do, by design, not by accident:

• Windows: there is no committed plan. If it arrives, it will be because someone does the work, not because the roadmap promised it.
• Web or GUI frontends: the terminal is the interface. SSH exists.
• SaaS or telemetry: local-first. Your data stays on your machine.
• Mobile apps: amber lives in the terminal.

No dates are promised. If an item above has already shipped, it lives in "Current state" rather than here. The roadmap is a direction, not a calendar.