Lobu Memory CLI Reference
Lobu memory commands live under lobu memory. Authentication is shared with the rest of the CLI: run lobu login once, then memory commands reuse that session.
- Hosted: app.lobu.ai
- Default MCP endpoint:
https://lobu.ai/mcp
Install And Authenticate
Section titled “Install And Authenticate”# Run without installingnpx @lobu/cli@latest <command>
# Or install globallynpm install -g @lobu/clilobu <command>
# Authenticate once for all Lobu CLI commandslobu loginUse lobu token --raw when another local tool needs a bearer token command.
Runtime
Section titled “Runtime”lobu run is the only local boot path. There is no separate memory runtime command.
lobu runClient Wiring
Section titled “Client Wiring”lobu memory init
Section titled “lobu memory init”Wires an existing project’s agents to a memory MCP endpoint and configures local MCP-capable clients.
lobu memory initlobu memory init --url http://localhost:8787/mcplobu memory init --agent support-bot --skip-auth| Flag | Description |
|---|---|
--url <url> | MCP server URL (skips the picker) |
--agent <id> | Configure a specific agent only |
--skip-auth | Skip the authentication step |
The wizard detects supported clients and auto-configures them when possible. Browser-managed clients fall back to manual setup instructions.
lobu memory configure
Section titled “lobu memory configure”Writes OpenClaw plugin config for @lobu/openclaw-plugin. The generated plugin config uses lobu token --raw, so it reuses top-level lobu login authentication.
openclaw plugins install @lobu/openclaw-pluginlobu loginlobu memory configure --url https://lobu.ai/mcp --org my-orglobu memory health --url https://lobu.ai/mcp --org my-orgHealth
Section titled “Health”lobu memory health
Section titled “lobu memory health”Checks that the current Lobu login can authenticate to the MCP endpoint and list available tools.
lobu memory healthlobu memory health --org my-orglobu doctor --memory-onlyOrganization Selection
Section titled “Organization Selection”lobu memory org
Section titled “lobu memory org”Stores the default memory organization for commands that need an org-scoped MCP URL.
lobu memory org currentlobu memory org set my-orgYou can also override per-command with:
--org <slug>--url <mcp-url>LOBU_MEMORY_ORGLOBU_MEMORY_URL
Run MCP Tools Directly
Section titled “Run MCP Tools Directly”lobu memory run
Section titled “lobu memory run”Lists tools when called without arguments, or executes a tool when given a tool name and JSON params.
# List available toolslobu memory run --org my-org
# Search memorylobu memory run search_memory '{"query":"Acme"}' --org my-org
# Save new memorylobu memory run save_memory '{"content":"Prefers weekly summaries","semantic_type":"preference","metadata":{}}' --org my-org
# Discover SDK methodslobu memory run search_sdk '{"query":"watchers.create"}' --org my-org
# Query with a read-only TypeScript script over the typed client SDKlobu memory run query_sdk '{"script":"export default async (ctx, client) => client.entities.list({ entity_type: \"company\", limit: 5 })"}' --org my-org
# Preview a mutating script without applying write/external SDK callslobu memory run run_sdk '{"dry_run":true,"script":"export default async (ctx, client) => client.entities.create({ type: \"company\", name: \"Acme\" })"}' --org my-orglobu memory exec <script>
Section titled “lobu memory exec <script>”Sugar for lobu memory run run_sdk '{"script": ...}' — runs the given TypeScript ClientSDK script source via the memory MCP without hand-quoting the JSON wrapper. <script> is the script text itself, so pipe a file in with $(cat ...).
lobu memory exec 'export default async (ctx, client) => client.entities.list({ entity_type: "company", limit: 5 })' --org my-orglobu memory exec "$(cat script.ts)" --url https://lobu.ai/mcp --org my-orgAccepts the same --url, --org, and -c/--context flags as lobu memory run.
Seed Project Memory
Section titled “Seed Project Memory”lobu memory seed
Section titled “lobu memory seed”Provisions a memory workspace from lobu.config.ts. The schema (entity types, relationship types, watchers) and the org come from defineConfig; optional seed data records come from YAML files under ./data.
Declare the schema in lobu.config.ts:
import { defineConfig, defineEntityType, defineRelationshipType, defineWatcher,} from "@lobu/cli/config";
const account = defineEntityType({ key: "account", name: "Account" });const owns = defineRelationshipType({ key: "owns", name: "Owns" });const digest = defineWatcher({ agent: "sales", slug: "account-digest", name: "Account digest", schedule: "0 9 * * 1", prompt: "Summarize account changes.", extractionSchema: { type: "object", properties: {} },});
export default defineConfig({ org: "my-org", agents: [/* ... */], entities: [account], relationships: [owns], watchers: [digest],});lobu memory seedlobu memory seed --dry-runlobu memory seed --org my-org --url https://lobu.ai/mcpBrowser Auth
Section titled “Browser Auth”lobu memory browser-auth
Section titled “lobu memory browser-auth”Sets up browser auth for connectors that rely on a real browser session. The CLI launches a dedicated Chrome with remote debugging enabled and stores its CDP endpoint on the auth profile; the connector attaches over CDP at sync time and harvests fresh cookies live from that session. --connector is required.
# Launch a debug Chrome and store the CDP endpoint on the auth profile.# A new Chrome window opens; sign into the site once and leave it open.lobu memory browser-auth --connector x --auth-profile-slug my-profile
# Verify the CDP endpoint on a profile is still reachable.lobu memory browser-auth --connector x --auth-profile-slug my-profile --check| Flag | Description |
|---|---|
--connector <key> | Required. Connector key (e.g. x) |
--domains <list> | Comma-separated cookie-domain override |
--auth-profile-slug <slug> | Browser auth profile slug to store the CDP endpoint on |
--remote-debug-port <port> | Remote debugging port for the dedicated Chrome (default 9222) |
--dedicated-profile <name> | Dedicated Chrome profile dir name |
--check | Check whether the CDP endpoint stored on a browser auth profile is reachable |
Skills
Section titled “Skills”The old standalone Lobu starter skills are folded into a single bundled lobu skill. Enable it from the agent settings UI, or add it to a project:
npx skills add lobu-ai/lobu --skill lobuLocal skills are referenced explicitly from lobu.config.ts via skillFromFile. There is no directory auto-discovery.
Related
Section titled “Related”- Lobu CLI: CLI Reference
- Memory docs: Memory