Roadmap
Aether is under active development. This page tracks features that are genuinely planned but not yet implemented, and clarifies the status of recently completed work.
INFO
This roadmap reflects our current direction but may change as priorities shift. Aether is a fast-moving project — breaking changes can happen between releases.
Recently Completed
These features are implemented and working today (they may have previously appeared as "planned" in older docs):
| Feature | Status | Notes |
|---|---|---|
Unified webhook endpoint (/webhook/:slug) | Done | Replaces per-source endpoints |
| Capability-based agent routing | Done | In application/routing/ |
| Agent Gateway (gRPC) | Done | External agents connect via gRPC on port 9090 |
| Tiered memory (Redis + PostgreSQL + pgvector) | Done | Full semantic search working |
| Full-text search over memories | Done | Added in migration 037 |
| MCP (Model Context Protocol) server integration | Done | Register MCP servers, dynamic tool discovery |
| Agent authentication and session management | Done | Bcrypt hashing, session tracking |
| Rate limiting by trust level | Done | Redis-backed sliding window |
| LLM tool calling | Done | Always enabled — tool calling is unconditional |
| Confluence knowledge ingestion | Done | Cloud and Server supported |
| Dynamic integrations (per-agent credentials) | Done | Encrypted storage |
| Agent audit logging | Done | Immutable log of all agent actions |
| Polling for non-webhook sources | Done | Configurable scheduler with state tracking |
| Token usage tracking | Done | Prompt/completion/total per task and tool call |
| Agent capabilities seeding | Done | POST /api/agents/capabilities/seed |
Planned
Knowledge Connectors
Aether's knowledge ingestion framework supports pluggable connectors. Confluence is working. These are next:
| Connector | Status | Description |
|---|---|---|
| WikiJS | Planned | Ingest pages from self-hosted WikiJS |
| BookStack | Planned | Ingest pages from BookStack installations |
| Raw HTML | Planned | Ingest any web page or local HTML files |
| GitHub Docs | Planned | Ingest from GitHub repository wiki and markdown files |
| Notion | Planned | Ingest from Notion workspaces |
Agent SDK Publishing
The SDK definitions and examples are in the repository (sdks/, goway/pkg/sdk/). Publishing to public registries is planned:
| SDK | Target Registry | Status |
|---|---|---|
Python SDK (aether-sdk) | PyPI | Planned |
| Go SDK | pkg.go.dev | Planned |
TypeScript SDK (@aether/sdk) | npm | Planned |
Additional Polling Sources
The polling scheduler currently supports issue tracker sources. Additional polling targets:
- Slack — Poll for new messages in configured channels
- Email (IMAP) — Poll for incoming emails to a configured inbox
- Custom HTTP endpoints — Poll arbitrary JSON APIs
Advanced Workflow Orchestration
A more structured workflow system allowing:
- Multi-step workflows with conditional branching
- Parallel task execution with synchronization
- Workflow state persistence and resumption
- Workflow templates for common patterns (PR review flow, issue triage flow, etc.)
Agent Budgets & Spending Controls
Token budgets per agent, per project, or per time period:
- Hard limits: stop processing when budget is exceeded
- Soft limits: alert when approaching budget
- Per-model cost tracking and reporting
- Monthly budget reset
Multi-Model Agent Routing
Route different task types to different LLM models based on cost/capability tradeoffs:
- Fast, cheap models for triage tasks
- Powerful models for complex analysis
- Per-task model override
Structured Response Formats
Force agents to respond in structured JSON formats for programmatic processing:
- Configurable output schemas per task
- JSON extraction and validation
- Direct API integration without comment posting
Frontend Improvements
The React frontend is functional but evolving:
- Real-time log streaming in the UI
- Visual event routing diagram editor
- Agent performance dashboard with charts
- Memory browser with similarity visualization
- Mobile-responsive layout
Deprecated
These features exist but are not recommended for new setups:
| Feature | Recommendation |
|---|---|
Per-source webhook endpoints (/webhook/github, /webhook/jira, etc.) | Use the unified /webhook/:slug endpoint instead. Per-source endpoints work but will be removed in a future major version. |
Contributing
If you'd like to contribute to any of these features, check the Contributing Guide and open an issue to discuss your approach before starting.