The agent that never forgets.
And never waits to be asked.

Give on-call teams agents that inspect deploys, correlate alerts, and keep incident context across every handoff.

Try the Engineering demo View source on GitHub

Company

Legal Engineering Support Finance Sales

Personal

Leadership Venture Capital

Public

Agent Community Market Intelligence

Cron

Weekdays at 9:30 AM — gathers DMs from 9:00 to 9:30

Summarize overnight standup DMs, pair people with overlapping work, and post the digest to #eng-standup.

Trace

watcher.poll(since: last_run)

→ 5 events collected

9:02Danpicking up INC-4421, rolling back checkout-v43

9:05Priyastill blocked on k8s cluster admin creds — can someone grant?

9:11Jaycaching layer PR is ready for review, needs to land by EOD

9:18SamOOO today — family thing

9:27Ninawriting INC-4378 postmortem, sharing draft at lunch

recall(incident: INC-4421, owner: Dan)

→ checkout rollback in progress · needs cluster access

pair(Priya.blocker, Dan.work)

→ both need checkout cluster — pair suggested

upsert(Engineer Sam → OOO today)

→ linked to on-call schedule

slack.channels.post(#eng-standup)

→ digest + pairings posted

Skills

Learn about Skills →

MCP

pairslack

Network

github.com.github.com.githubusercontent.comregistry.npmjs.org.npmjs.org

Memory

Learn about Memory →

Entities touched

IncidentEntity: checkout-api degradation

incidentactive

ServiceService: EU checkout

serviceimpact

DeployDeploy: 2026.04.13.2

deploytrigger

Pull requestPR: #482

code changeblocker

Relationship

Incident checkout-api degradationaffects_serviceService EU checkout

Outcome →

#eng-standup

Morning team. Dan is rolling back checkout-v43 (INC-4421). Priya is blocked on k8s admin creds — pairing her with Dan since they both need checkout cluster access. Jay's caching PR is ready for review by EOD; Nina, can you take it once the INC-4378 postmortem draft is out? Sam is OOO today.

Available in

Slack Telegram WhatsApp Discord Teams Google Chat REST API

Live workspace

Open workspace →

Read-only preview of the Engineering workspace running on Lobu.

Architecture

Every agent runs in a sandboxed container with no outbound network by default — on your infrastructure, not ours.

Messaging platforms

Slack

Block Kit, interactive actions

Mini App, inline buttons

Reply buttons, list menus

Discord

Servers, DMs, markdown replies

Teams

Channels, bots, enterprise workflows

Google Chat

Cards v2, Workspace spaces

Link users across platforms with single sign-on
Approval flows, rich cards, buttons, and more

Bring your own agent

any MCP-capable agent

Lobu Memory

Lobu

Control Plane

Secrets

Single Sign-On (IdP)

Skill Registry Traces Sandboxing

Workers never see secrets
HTTP proxy with domain allowlist
MCP proxy with per-user OAuth
BYO provider keys (Anthropic etc.)

Equip your agent

Lobu Skills

OpenClaw Runtime

User A

isolated

OpenClaw Runtime

User B

isolated

OpenClaw Runtime

User C

isolated

One sandbox per user and channel
Kata Containers / Firecracker microVMs / gVisor on GCP
virtualized bash for scaling beyond 1000 users
No direct internet access (internal network)
Nix reproducible environments
OpenTelemetry for observability

Lobu in memory benchmarks

Apples-to-apples comparison on public memory datasets. The model is GLM 5.1 via z.ai.

LongMemEval (oracle-50)

Single-session knowledge retention.

System	Overall	Answer	Retrieval	Latency
Lobu	87.1%	78.0%	100.0%	237ms
Supermemory	69.1%	56.0%	96.6%	702ms
Mem0	65.7%	54.0%	85.3%	753ms

LoCoMo-50

Multi-session conversational memory.

System	Overall	Answer	Retrieval	Latency
Lobu	57.8%	38.0%	79.5%	121ms
Mem0	41.5%	28.0%	66.9%	606ms
Supermemory	23.2%	14.0%	36.5%	532ms

Read the methodology

From the blog

Latest blog posts

memoryApr 13

Filesystem vs Database for Agent Memory

Agents need a workspace to think in and a warehouse to remember in. The filesystem is for ephemeral work. The memory layer is for durable organizational knowledge.

Read post →

tutorialApr 9

Add OpenClaw to your Next.js app in 10 minutes

Embed OpenClaw agents in a Next.js project with per-user sandboxing, MCP tools, and network isolation — no Docker required.

Read post →

mcpApr 2

MCP Is Overengineered, Skills Are Too Primitive

MCP HTTP is great for external services. MCP stdio is redundant. And most skill systems are just prompt text with no reproducibility. Here's what we built instead.

Read post →