Claude Code,
with context beyond the repo.
Give Claude Code the customer requirements and team decisions behind the code it changes.
Lobu MCP authenticated · workspace: Product
Find our agreed onboarding fix, implement it, and record what shipped.
I'll retrieve the source-linked decision first, make the smallest change, then save the verified result for the next agent.
- Retrieve the onboarding decision (completed)
- Implement the approved change (in progress)
- Test and save the shipped result (pending)
search_memory(onboarding decision source:customer-feedback)Found 1 exact decision · 3 linked sources
query_sdk(client.events.readMany({ entity_id: onboarding }))Confirmed owner, affected step, and acceptance criteria
Update(src/onboarding/ConnectAgent.tsx)
Made the first successful connection the primary next step
42 return <OnboardingStep>43-removed: <ExploreWorkspace />43+added: <ConnectFirstAgent primary />44+added: <SourceLinkedExample />45 </OnboardingStep>
Bash(bun test)18 passed, 0 failed in 1.7s(ctrl+o to expand)
bun test v1.2.21
✓ onboarding > connects an agent first
✓ onboarding > preserves linked sources
18 pass
0 fail
Thinking…(0s · ↑ 0 tokens · esc to interrupt)
xhigh · /effort
auto mode on (shift+tab to cycle) · ← for agents
The context is already there.
Lobu syncs your connected sources in the background. Search the live company model with its records, relationships and source events together.
How memory worksYour team's agents, too.
Claude Code can call shared organization agents with their own skills, identity and permissions. Use paired devices or sandboxed tools where access is granted.
Shared agents and accessAdd Lobu to Claude Code.
Connect the MCP server, sign in and choose your workspace. The guide covers your client and self-hosted setup.
https://lobu.ai/mcpMCP server · Sign in with your Lobu account