Overview
IronClaw is a Rust reimplementation inspired by OpenClaw. This document tracks feature parity between the two projects to coordinate development across contributors. Current Version: IronClaw 0.13.1Status Legend
- โ Implemented: Feature is complete and working
- ๐ง Partial: In progress or incomplete implementation
- โ Not Implemented: Feature not yet started
- ๐ฎ Planned: In scope but not started
- ๐ซ Out of Scope: Intentionally skipped
- โ N/A: Not applicable to Rust implementation
Key Architectural Differences
IronClaw intentionally differs from OpenClaw in several areas:1. Rust vs TypeScript
- Native performance: No runtime overhead
- Memory safety: Compile-time guarantees
- Single binary: No dependencies required
2. WASM Sandbox vs Docker
- Lightweight: WASM modules vs full containers
- Faster startup: Milliseconds vs seconds
- Capability-based security: Explicit permission model
3. Database Strategy
- PostgreSQL + libSQL: Dual backend support
- Production-ready: PostgreSQL for production
- Zero-dependency mode: Embedded libSQL for development
4. NEAR AI Focus
- Primary provider: NEAR AI as default LLM backend
- Session-based auth: OAuth flow with refresh tokens
5. No Mobile/Desktop Apps Initially
- Server-first: Focus on core agent functionality
- CLI/TUI: Terminal interface for power users
- Web gateway: Browser-based control UI
6. Novel Features
- WASM channels: Extension mechanism unique to IronClaw
- Tinfoil provider: Private/encrypted inference
- Prompt-based skills: Trust gating and attenuation
Implementation Progress by Category
Core Systems (85% Complete)
Messaging Channels (60% Complete)
Channel Features
LLM Provider Support (70% Complete)
Provider Features
Security & Safety (75% Complete)
Memory & Knowledge (80% Complete)
CLI Commands (75% Complete)
Automation & Hooks (70% Complete)
Web Interface (65% Complete)
Plugin & Extension System (70% Complete)
Media Handling (10% Complete)
Mobile & Desktop Apps (Out of Scope)
Priority Definitions
P0 - Core (Already Done)
Essential features for basic functionality:- โ Agent loop and message handling
- โ Session management and context compaction
- โ WASM and Docker sandboxes
- โ Hybrid search with pgvector
- โ Prompt injection defense
- โ Skills system with trust gating
- โ Core channels (TUI, HTTP, WebChat)
- โ Gateway control plane
- โ Memory CLI commands
P1 - High Priority
Important features for production use:- โ Multi-provider failover
- โ Telegram WASM channel
- โ Hooks system (core + bundled/plugin/workspace)
- โ WhatsApp channel
- โ OpenRouter/OpenAI-compatible provider support
P2 - Medium Priority
Enhanced functionality:- โ Media handling (images, PDFs)
- โ Ollama/local model support
- โ Configuration hot-reload
- โ Channel health monitor
- โ Gateway and cron CLI commands
P3 - Lower Priority
Nice-to-have features:- โ Discord, Matrix channels
- โ TTS/audio features
- โ Video support
- โ Streaming (block/tool/Z.AI)
- โ Memory advanced features (temporal decay, MMR)
- โ Control UI i18n
How to Contribute
1. Claim a Feature
EditFEATURE_PARITY.md in the source repository and add your name/handle to the โOwnerโ field for your chosen section.
2. Create Tracking Issue
Open a GitHub issue for the feature area:3. Update Status
As you work:- Change โ to ๐ง when starting
- Update to โ when complete
- Add notes for design decisions or deviations
4. Update in PR
IncludeFEATURE_PARITY.md updates in your pull request:
Coordination
Section Ownership
- Each major section should have one owner to avoid conflicts
- Owners can delegate sub-features to others
- Update ownership in
FEATURE_PARITY.md
Communication
- GitHub Issues: Track feature implementation
- Pull Requests: Include parity updates
- Discussions: Ask questions and propose designs
- Telegram: @ironclawAI for real-time chat
Review Process
- Reviewers verify parity updates match code changes
- Status changes must be accurate
- Notes should explain any deviations from OpenClaw
- Priorities can be adjusted with justification
Current Status Summary
As of version 0.13.1:
Overall Progress: ~65% feature parity
Next Major Milestones
Q2 2026
- Complete WhatsApp channel (P1)
- Implement media handling (P2)
- Add configuration hot-reload (P2)
- Enhance channel health monitoring (P2)
Q3 2026
- Discord channel implementation (P2)
- Advanced memory features (temporal decay, MMR) (P3)
- Streaming support (block/tool-level) (P3)
- Control UI internationalization (P3)
Q4 2026
- Matrix and additional messaging channels (P3)
- TTS/audio features (P3)
- Video processing support (P3)
- Plugin registry/ClawHub (P3)
Resources
- OpenClaw Repository: github.com/openclaw/openclaw
- IronClaw Repository: github.com/nearai/ironclaw
- Full Parity Matrix: See
FEATURE_PARITY.mdin source repository - Contributing Guide: /development/contributing
- Building Guide: /development/building
- Testing Guide: /development/testing
Questions?
If youโre unsure whether a feature is in scope or how to implement it:- Check the full
FEATURE_PARITY.mdin the source repository - Search existing GitHub issues
- Open a discussion on GitHub
- Ask in the Telegram group