Bring your agents
Connect ChatGPT, Claude, Codex, OpenClaw, or any MCP client to the same company context, scoped to each user.
Connect an agent → Slack · Hosted bot
Company context, right in Slack.
Set a standing goal, connect company and employee context, and let the agent work with feedback from your team. Slack is the control surface; you keep the authority.
DM @lobu ● setup
Connect HubSpot, Gmail, and our warehouse for renewals.
Three sources. HubSpot and Gmail use OAuth. Open the secure form for the warehouse; credentials never land in chat.
Authorize HubSpot · Open Gmail · Open secure form
#pipeline ● live
Goal: keep Acme renewals on track. Who owns it if finance blocks?
Priya owns it. There is an invoice dispute in Gmail and P1 #482. Draft a review before we contact the CFO?
Allow once · Edit · Deny
Works with
Connects to
DiscordGitHubGmailGoogle CalendarGoogle ChatHacker NewsLinearMicrosoft TeamsPostgreSQLProduct HuntRedditRSS / AtomSlackTelegramWhatsApp CloudX (Twitter)YouTube+4 more
[ 03/LOBU RUN ]
One company layer, in 4 steps.
See how company context, ownership, standing goals, and human approval connect in one shared workflow.
01
Connect your company.
Connectors stream your databases, SaaS tools, files, devices, and internal APIs into context. Your systems of record stay where they are. Models, sandboxes, and devices are independent layers, credentials gateway-side. Flip the tabs to wire each one.
Connectors ↗Messages, reactions, and linked channels become shared context.
feed · event → shared memoryentity
channels
updateP1 issue #482 reopened14m
messages
updateP1 issue #482 reopened14m
mentions
updateP1 issue #482 reopened14m
02
Turn activity into governed context.
Raw events resolve into people, customers, projects, policies, and goals, with the relationships between them. Every fact from the connectors above converges on the right record, carries its provenance, and is read under the caller's permissions.
Memory ↗memory
Employee
idPK
full_name
slack_handle
Account
idPK
owner_idFK
health
Goal
idPK
account_idFK
objective
Approval
idPK
account_idFK
status
03
Deploy Automations that watch and act.
A trigger — a schedule, or reactive to connector events — plus a plain-language prompt. Once defined it runs unprompted: scans memory, matches the trigger, and surfaces the work with the evidence attached.
Automations ↗automation
triggers⏱ ScheduleOn account change⚡ On eventAcme renewal moved to Jun 30
prompt
“Keep Acme renewals on track. Ask the account owner before contacting finance or changing commercial terms.”
@ connector@ entityReferences resolve to the sources and types you defined above.
04
Use it from any agent.
ChatGPT, Claude, and Codex connect over MCP; Slack, Teams, and WhatsApp over chat; your own apps over the API. Same context, same permissions, whoever's asking. Consequential work arrives as a proposal you review, edit, and approve.
Platforms ↗#pipelineAcme renewal
Acme renewal needs review
- Invoice dispute opened by the CFO
- P1 issue #482 reopened
- Usage fell 38% over 14 days
Drafted a review brief for Priya before any CFO outreach. Review before I hand it off:
Draft · owner brief
Acme renewal risk: CFO dispute in Gmail, P1 #482 reopened, usage down 38%. Priya owns the account. CFO outreach blocked pending her review — brief attached with evidence.
[ 03/TWO WAYS IN ]Start here Optional runtime
Bring any agent. Add shared context.
Use the agents your team already trusts. Managed agents are optional.
Build a managed agent
Run repeatable work from live events or schedules under the same approval policy.
Build a managed agent →[ 04/UNDER THE HOOD ]
One control plane. Any agent.
Share context, permissions, approvals, and connected actions with any agent. Add Lobu's runtime only when you need it.
Bring your first teammate into Slack.
Set the goal, connect the context, and keep approval over every meaningful action. Use the hosted bot or self-host your own Slack app.