What should we build next? Vote on ClawFleet's roadmap direction #83
weiyong1024
started this conversation in
Ideas
Replies: 3 comments
🛡️ Option A: Stronger IsolationMicroVM-level sandboxing, network policies, filesystem restrictions, per-instance resource limits. 👍 this comment to vote for Stronger Isolation |
0 replies
🎨 Option B: Better Management UXMonitoring, logs aggregation, one-click config templates, backup/restore, team collaboration. 👍 this comment to vote for Better UX |
0 replies
🔌 Option C: Multi-Agent PlatformSupport beyond OpenClaw — Claude Code, Codex CLI, Open Interpreter, custom agents. Universal orchestration for any containerized AI agent. 👍 this comment to vote for Multi-Agent Platform |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We just launched ClawFleet and we're deciding where to focus next. Your vote helps us prioritize.
The three directions
🛡️ Option A: Stronger Isolation
Upgrade from Docker containers to MicroVM-level sandboxing. Network policies, filesystem restrictions, per-instance resource limits. For users who need maximum security between their AI agents and host system.
🎨 Option B: Better Management UX
More dashboard features — monitoring, logs aggregation, one-click config templates, backup/restore, team collaboration. Make managing a fleet of 10+ instances as easy as managing one.
🔌 Option C: Multi-Agent Platform
Support AI agents beyond OpenClaw — Claude Code, Codex CLI, Open Interpreter, custom agents. Turn ClawFleet into a universal orchestration layer for any AI agent that runs in a container.
How to vote: Give a 👍 to the comment below that matches your preferred direction.
Feel free to reply with details about what specific features matter most to you. If you have ideas that don't fit these three directions, drop them in the comments — we read every one.
All reactions