Skip to content
lobu
API Blog

Connect from Codex

Give Codex the company decisions, source evidence, and permissions it needs before it changes code or external systems.

Use mapped devices from Codex

Codex can request governed work that Lobu routes to an authorized device worker for local files, connector syncs, actions, or device Automations. Run lobu daemon on that machine once; a named context keeps one stable host identity, while supported Claude Code, Codex, and OpenCode sessions receive separate per-session identities for interactive delivery. See the device worker setup.

Lobu is open-source but we also have a managed cloud. If you'd like to try, sign in at app.lobu.ai, then point Codex at https://app.lobu.ai/mcp as the MCP endpoint. The same URL works for every workspace. Pick one below to scope it to that example.

Paste this into Codex and it will install Lobu for you.

Prompt for Codex
Connect this Codex session to Lobu, the shared company context layer for agents, over MCP: https://lobu.ai/mcp.

Onboard yourself:
- If you have a CLI: run `codex mcp add lobu --url https://lobu.ai/mcp`, then `codex mcp login lobu` and complete OAuth, then start a fresh Codex task so it loads the new tools.
- If you can't touch a terminal: ask the user to connect Lobu from the Codex Plugins settings, authenticate, and start a fresh task — then continue once connected.

Authenticate when prompted, then:
Read the Lobu skill at https://app.lobu.ai/api/skill/lobu, then run search_sdk for the smallest SDK surface you need. Do not dump the whole workspace.
Search existing memory before answering or saving a duplicate. Use search_memory/save_memory for durable context, query_sdk for reads, run_sdk for writes. Preview consequential writes first and keep every returned source URL, identifier, and approval status exact — never invent one, never fabricate a returned URL or identifier.

Connect Codex

  1. Run codex mcp add lobu --url https://lobu.ai/mcp.
  2. Run codex mcp login lobu and complete the Lobu sign-in flow in your browser.
  3. Start a fresh Codex task so the newly connected tools are loaded.
  4. Ask Codex to run search_sdk before it reads or changes workspace state.

The same Lobu plugin is being prepared for the shared ChatGPT and Codex Plugins Directory. The direct MCP setup above works today and is also the best path for self-hosted instances; replace https://lobu.ai/mcp with your own public endpoint.

Related Docs

Understand the MCP connectionSee how external agent clients reach Lobu tools and memory.Choose what to rememberSeparate session files from shared organizational state.Explore other surfacesUse the same agent in team chat, web, or a custom app.