Skip to main content

Project Roadmap

ZeroClaw’s development focuses on performance, security, and extensibility. This roadmap outlines our priorities and planned improvements.
This roadmap represents planned work and may change based on community feedback, security needs, and technical discoveries. Timelines are estimates.

Current Status

ZeroClaw v0.1.0 established a strong foundation:

Performance

  • 3.1MB binary size
  • <5MB RAM usage
  • <10ms startup time

Security

  • Command allowlisting
  • Path traversal protection
  • Workspace sandboxing
  • Rate limiting

Architecture

  • Trait-based design
  • Pluggable providers
  • Swappable channels
  • Custom tools

Testing

  • 159 inline tests
  • Edge case coverage
  • Security validation

Security Hardening Roadmap

ZeroClaw already has excellent application-layer security. The roadmap focuses on OS-level containment for production deployments.

Phase 1: Quick Wins (1-2 weeks)

Goal: Address critical gaps with minimal complexity
File: src/security/landlock.rs
Effort: 2 days
Impact: High
Restrict filesystem access to workspace using Linux Landlock LSM.
File: src/resources/memory.rs
Effort: 1 day
Impact: High
Monitor memory usage and kill runaway processes before system instability.
File: src/tools/shell.rs
Effort: 1 day
Impact: High
Enforce per-command CPU time limits to prevent infinite loops.
File: src/security/audit.rs
Effort: 2 days
Impact: Medium
Tamper-evident logging of all agent actions with HMAC signatures.
Deliverables:
  • Linux: Filesystem access restricted to workspace
  • All platforms: Memory/CPU guards against runaway commands
  • All platforms: Tamper-evident audit trail

Phase 2: Platform Integration (2-3 weeks)

Goal: Deep OS integration for production-grade isolation
Effort: 3 days
Impact: Very High
Detect and wrap agent execution in Firejail for container-like isolation on Linux.
Effort: 4 days
Impact: Very High
Filesystem isolation for macOS and other *nix systems using Bubblewrap.
Effort: 3 days
Impact: High
Enforce resource limits using systemd cgroups v2 on Linux.
Effort: 5 days
Impact: High
Allowlist permitted syscalls to reduce attack surface.
Effort: 2 days
Impact: Medium
Command-line tools for querying and analyzing audit logs.
Deliverables:
  • Linux: Full container-like isolation via Firejail
  • macOS: Bubblewrap filesystem isolation
  • Linux: cgroups resource enforcement
  • Linux: Syscall allowlisting

Phase 3: Production Hardening (1-2 weeks)

Goal: Enterprise security features
Effort: 3 days
Impact: High
Optional Docker-based execution isolation for maximum security.
Effort: 2 days
Impact: Medium
HTTPS certificate pinning for channel webhooks to prevent MITM attacks.
Effort: 2 days
Impact: Medium
Verify config file signatures to detect tampering.
Effort: 2 days
Impact: Medium
JSON/CSV audit export for integration with external SIEM systems.
Effort: 1 day
Impact: Low
zeroclaw audit --check command to validate security configuration.
Deliverables:
  • Optional Docker-based execution isolation
  • HTTPS certificate pinning for webhooks
  • Config file signature verification
  • JSON/CSV audit export

Planned Config Schema

Proposed configuration for security features:
[security]
level = "strict"  # relaxed | default | strict | paranoid

# Sandbox configuration
[security.sandbox]
enabled = true
backend = "auto"  # auto | firejail | bubblewrap | landlock | docker | none

# Resource limits
[resources]
max_memory_mb = 512
max_memory_per_command_mb = 128
max_cpu_percent = 50
max_cpu_time_seconds = 60
max_subprocesses = 10

# Audit logging
[security.audit]
enabled = true
log_path = "~/.config/zeroclaw/audit.log"
sign_events = true
max_size_mb = 100

# Autonomy (existing, enhanced)
[autonomy]
level = "supervised"  # readonly | supervised | full
allowed_commands = ["git", "ls", "cat", "grep", "find"]
forbidden_paths = ["/etc", "/root", "~/.ssh"]
require_approval_for_medium_risk = true
block_high_risk_commands = true
max_actions_per_hour = 20

Feature Roadmap

Agent Capabilities

Status: Research phaseEnable multiple agents to collaborate on complex tasks with shared context and work distribution.
Status: PlannedReal-time streaming of LLM responses for better UX in interactive channels.
Status: ExplorationAllow tools to call other tools to build complex workflows.
Status: In progressVector embeddings for semantic memory search beyond keyword matching.

Platform Support

Status: PlannedFirst-class Windows support with native security primitives.
Status: ExperimentalRun ZeroClaw in browser environments with WASM compilation.
Status: ResearchUltra-minimal runtime for WiFi-enabled edge devices.

Developer Experience

Status: In progressComprehensive SDK for building and testing plugins locally.
Status: PlannedReload plugins and configuration without restarting the agent.
Status: PlannedEnhanced debugging tools with step-through execution and state inspection.

Comparison: ZeroClaw vs Alternatives

How security roadmap implementation positions ZeroClaw:
FeaturePicoClawZeroClaw NowZeroClaw + RoadmapProduction Target
Binary Size~8MB3.4MB3.5-4MB< 5MB
RAM Usage< 10MB< 5MB< 10MB< 20MB
Startup Time< 1s< 10ms< 50ms< 100ms
Command AllowlistUnknown✅ Yes✅ Yes✅ Yes
Path BlockingUnknown✅ Yes✅ Yes✅ Yes
Injection ProtectionUnknown✅ Yes✅ Yes✅ Yes
OS SandboxNo❌ No✅ Firejail/Landlock✅ Container/namespaces
Resource LimitsNo❌ No✅ cgroups/Monitor✅ Full cgroups
Audit LoggingNo❌ No✅ HMAC-signed✅ SIEM integration
Security ScoreCB+A-A+

Community Priorities

We’re listening to the community. Vote on features and share feedback:

Feature Requests

Propose and vote on new features

Roadmap Discussions

Discuss priorities and timelines

Security RFCs

Review security proposals

GitHub Issues

Track specific work items

Estimated Timeline

1

Q1 2026 - Security Phase 1

Landlock, memory monitoring, CPU timeouts, basic audit logging
2

Q2 2026 - Security Phase 2

Firejail, Bubblewrap, cgroups, seccomp filtering
3

Q2 2026 - Security Phase 3

Docker mode, certificate pinning, signed configs, SIEM export
4

Q3 2026 - Feature Expansion

Streaming, multi-agent coordination, enhanced memory
5

Q4 2026 - Platform Expansion

Windows native support, edge device runtime
Timelines are estimates and subject to change based on community needs, security discoveries, and maintainer availability.

How to Contribute

Want to help shape the roadmap?

Implementation

Contribute code for roadmap items

Testing

Test experimental features

Documentation

Document new capabilities

Feedback

Share use cases and priorities

Additional Resources

Security Roadmap (Full)

Detailed security improvement plan

Architecture Docs

System design and patterns

Changelog

Recent changes and releases

Contributing Guide

How to get involved

Build docs developers (and LLMs) love