Lobu — Multi-tenant OpenClaw for Organizations
Lobu is an open-source multi-tenant gateway for OpenClaw. One sandbox and filesystem per user/channel. Shared memory across contexts. Agents never see secrets.
OpenClaw is a full agent runtime (~800k LOC) but it's single-tenant by design — every user shares the same filesystem and bash session. Lobu rewrites only the gateway layer (~40k LOC) to be multi-tenant and keeps OpenClaw's Pi harness untouched inside each worker.
Embedded mode uses just-bash + Nix for reproducible packages. Each user gets an isolated virtual filesystem and bash session at ~50MB per instance — tested at 300 concurrent instances on a single machine, no Docker needed.
Embed OpenClaw-powered agents into your product, or give your team agents without managing a separate instance per person.
https://github.com/user-attachments/assets/d72a9286-0325-4b8b-afc0-c1efe9c96f4e
Channels & API
- REST API — programmatic agent creation, control, and state.
- Slack — multi-channel/DM agents with rich interactivity.
- Telegram — long-polling bot with interactive workflows.
- WhatsApp — WhatsApp Business Cloud API.
- Discord — channel + DM bot support.
- Teams — Microsoft Teams bot.
Quick Start
Scaffold and run via the CLI:
npx @lobu/cli@latest init my-bot
cd my-bot && npx @lobu/cli@latest run -d
Starter Skills
Install the Lobu starter skill into any local skills/ directory:
npx @lobu/cli@latest skills add lobu
Install the Owletto starter skill separately when the agent should understand Owletto memory and tooling:
npx owletto@latest skills add owletto
npx owletto@latest init
Deployment modes
Architecture
flowchart LR
Slack[Slack] <--> GW[Gateway]
Telegram[Telegram] <--> GW
WhatsApp[WhatsApp] <--> GW
Discord[Discord] <--> GW
API[REST API] <--> GW
GW <--> Redis[(Redis)]
GW -->|spawn| W[Worker]
subgraph Sandbox
W
end
W -.->|HTTP proxy| GW
W -.->|MCP proxy| GW
GW -->|domain filter| Internet((Internet))
GW -->|scoped tokens| MCP[MCP Servers]
Capabilities
Every Lobu agent ships with tools for autonomous execution and persistence:
| Feature | Built-in Tools |
|---|
| Autonomous scheduling — one-time or cron | ScheduleReminder, ListReminders, CancelReminder |
| Human-in-the-loop — pause on button input, resume on answer | AskUserQuestion |
| Full Linux toolbox — sandboxed shell, file edit, search | bash, read, write, edit, grep, find, ls |
| Conversation context — pull earlier thread messages | GetChannelHistory |
| File & media delivery — share reports, charts, audio | UploadUserFile, GenerateAudio |
Skills — extend via lobu.toml or admin settings | lobu.toml, Settings UI |
| Connected APIs — GitHub, Google, etc. with Owletto-managed OAuth | MCP tools via Owletto |
| Managed MCP proxy — any MCP server with secret injection | MCP Proxy |
| Nix + external MCP — browsing, headless UI, custom tools | bash (Nix), MCP servers |
Popular MCP integrations
- Productivity: Google Calendar, Slack, Jira, Notion
- Development: GitHub, GitLab, Postgres, Docker
- Knowledge: Wikipedia, Brave Search, YouTube, PDF Search
Design
- Gateway as single egress. All worker traffic — internet and MCP — routes through the gateway. Workers have no direct network access; domain filtering controls which services they reach.
- MCP proxy. Gateway resolves
${env:VAR} secrets and routes to upstream MCP servers. OAuth for third-party APIs stays in Owletto — workers never see tokens.
- Multi-platform, multi-tenant. One instance serves Slack, Telegram, WhatsApp, Discord, Teams, and the REST API. Each channel/DM gets its own runtime, model, tools, credentials, and Nix packages.
- OpenClaw runtime. Workers run OpenClaw Pi Agent with per-agent model selection. Supports OpenClaw skills and
IDENTITY.md / SOUL.md / USER.md workspace files.
- Multi-provider auth. 16 LLM providers (OpenAI, Gemini, Groq, DeepSeek, Mistral, …) via a config-driven registry. API keys stay on the gateway.
How Lobu Differs