The project is divided into 4 main phases, with an estimated total development cycle of 12-16 weeks.
Phase 1: Core Framework (4-5 weeks)
↓
Phase 2: Basic Extensions (3-4 weeks)
↓
Phase 3: Agent Runtime (3-4 weeks)
↓
Phase 4: Ecosystem Enhancement (2-3 weeks)
Build an extensible core framework, define all protocols, and implement the microkernel.
- Create project directory structure
- Create architecture documentation
- Initialize Cargo workspace
- Configure CI/CD (GitHub Actions)
- Configure code quality tools (clippy, rustfmt)
- Extension trait definition
- Tool trait definition
- LLMProvider trait definition
- Channel trait definition
- MemoryBackend trait definition
- Agent trait definition
- Skill-related type definitions
- Common type definitions (Message, ToolResult, etc.)
- Error type definitions
- TaskQueue implementation
- Task subscribe/publish
- Middleware support
- Request-response pattern
- ExecutionContext implementation
- Context data storage
- Abort signal
- Sub-context creation
- ExtensionRegistry implementation
- Extension registration/unregistration
- Dependency resolution
- ToolRegistry implementation
- ProviderRegistry implementation
- Kernel implementation
- Extension lifecycle management
- Extension context creation
- Startup/shutdown process refinement
- Configuration schema definition
- TOML configuration parsing
- Environment variable substitution
- Configuration validation
- Configuration hot-reload (optional, Phase 4)
- protocols tests
- core tests
- config tests
- Compilable core framework
- Complete protocol definitions
- Unit test coverage
Implement basic tools and providers to validate the framework design.
-
#[extension]macro -
#[tool]macro - Macro tests
- read_file tool
- write_file tool
- edit_file tool (SEARCH/REPLACE)
- list_directory tool
- create_directory tool
- delete_file tool
- move_file tool
- Tests
- exec tool (command execution)
- Persistent shell session
- Background process management
- Timeout control
- Tests
- glob tool (file pattern matching)
- grep tool (content search)
- Integrated ripgrep
- Tests
- API client implementation
- Streaming completion
- Function calling support
- Error handling and retry
- Tests
- API client implementation
- Streaming completion
- Function calling support
- Tests
- API client implementation
- Streaming completion
- Function calling support
- Tests
- Database schema
- CRUD operations
- Basic search
- Tests
- 7+ available tools (filesystem, shell, search)
- 3 LLM Providers (Anthropic, OpenAI, Ark)
- 1 memory backend
- Extension development examples
Implement complete Agent runtime and API gateway.
- SessionManager implementation
- Session creation/retrieval
- Session persistence
- Session cleanup
- HistoryManager implementation
- Message history management
- History compression (summarization)
- ContextBuilder implementation
- System prompt construction
- Tool injection
- Skill injection
- AgentLoop implementation
- Main loop logic
- Tool execution
- Streaming response
- Error handling and retry
- Termination condition checking
- AgentRuntime implementation
- Agent scheduling
- Concurrency control
- HTTP server (axum)
- OpenAI compatible API
- Health check endpoint
- Admin endpoints
- WebSocket server
- Connection management
- Message protocol
- Heartbeat mechanism
- RunLoopBridge
- Request routing
- Session association
- TaskQueue implementation
- RunLoop implementation
- Source0/Source1 patterns
- Observer pattern
- Timer support
- CronTimer support
- Skill loader implementation
- Markdown parser
- Progressive disclosure (L1/L2/L3)
- Multiple format adapters (Claude Code, Microsoft, OpenClaw)
- Skill injection logic
- General agent implementation
- Tool selection logic
- Tests
- End-to-end tests
- API tests
- Agent execution tests
- Complete runnable Agent system
- HTTP/WebSocket API
- General Agent
- Dynamic skills
Enhance ecosystem, improve usability and extensibility.
- provider-gemini (Google Gemini)
- provider-local (Local models/Ollama)
- tools-web
- web_fetch tool
- web_search tool
- tools-code
- Code analysis tools
- LSP integration (optional)
- tools-browser
- Browser automation (CDP)
- AI-powered click/fill/extract
- tools-desktop
- Screenshot
- Mouse control
- Keyboard control
- OCR
- channel-telegram (Telegram channel, optional)
- MCP protocol bridge (planned)
- memory-vector
- Embedding generation
- Vector storage
- Hybrid search
- memory-hybrid
- Full-text search
- Vector search
- Fusion ranking
- autohands-daemon
- Process daemonization
- PID file management
- Signal handling
- macOS LaunchAgent support
- Linux Systemd support
- API documentation
- Architecture documentation
- Extension development guide
- Example projects
- Benchmark tests
- Performance analysis and optimization
- Memory optimization
- 4 Providers
- 46+ Tools
- MCP support
- Daemon support
- Complete documentation
| Milestone | Target Date | Content |
|---|---|---|
| M1: Core Framework | Week 4-5 | Protocol definitions, microkernel, configuration |
| M2: Basic Usable | Week 7-9 | Basic tools, providers, agent |
| M3: Feature Complete | Week 10-12 | API server, skills, channels |
| M4: Production Ready | Week 12-16 | MCP, optimization, documentation |
| Risk | Impact | Mitigation |
|---|---|---|
| Long Rust compilation time | Development efficiency | Use incremental compilation, mold linker |
| Missing MCP SDK | Development cycle | Implement protocol ourselves |
| Complex extension system | Delay | Initially only implement static extensions |
| LLM API changes | Compatibility | Abstraction layer isolation |
- Test-Driven - Write tests first, then implementation
- Documentation in Sync - Update code and documentation together
- Small Iterations - Each PR focuses on a single feature
- Code Review - All code requires review
- Performance Awareness - Focus on performance, avoid premature optimization
Last Updated: 2026-02-09