Agent Settings

Agent settings control behavior of each worker session.

What You Can Configure

Two surfaces feed an agent’s effective config:

• Runtime config — the camelCase keys below, stored per agent and edited through the web UI or the settings API.
• lobu.config.ts operator config — code-as-config declarations on defineAgent (e.g. tools, egress, guardrails) applied with lobu apply.

Runtime config keys:

• Provider and model — model, modelSelection (auto/pinned), providerModelPreferences, installedProviders
• Skills/plugins and connector config — skillsConfig, pluginsConfig, and connector connections
• Permission grants (network domains) — networkConfig
• Agent prompts — identityMd, soulMd, userMd
• Auth profiles — authProfiles for multi-provider credential management
• Worker environment — nixConfig for Nix packages
• Verbose logging — verboseLogging to show tool calls and reasoning
• Template inheritance — templateAgentId for settings fallback from a template agent

Allowed/disallowed tools are part of the lobu.config.ts operator surface — the agent tools field.

How Settings Apply

• Gateway is the source of truth for settings.
• Worker fetches session context from gateway before execution.
• Tool policy is applied before tools are exposed to the model.

See Tool Policy for the operator-facing config, and lobu.config.ts reference for the exact schema.

Practical Guidance

• Keep tool permissions minimal.
• Add only required domains/grants.
• Prefer explicit permission grants over broad access.

Memory

An agent’s memory is org-scoped. Set org on defineConfig({ org }) in lobu.config.ts and the gateway serves a memory MCP endpoint scoped to that org — every agent in the org reads and writes the same entity and event graph.

Effective config	Memory
org set	Org-scoped Lobu memory over MCP. Cross-session, shareable across agents.
MEMORY_URL set	Overrides the base MCP endpoint (for local or custom Lobu deployments) before the gateway scopes it to the org.

lobu init scaffolds the memory wiring for memory-enabled projects:

• org / orgName in defineConfig (lobu.config.ts)
• the entity, relationship, and behavior types declared with defineEntityType / defineRelationshipType / defineBehavior
• data/

For Lobu Cloud, Lobu can use the hosted default automatically. For Lobu Local and Custom URL, MEMORY_URL remains the base-endpoint override.

External clients — Claude, ChatGPT, OpenClaw, Cursor, your own — connect to that same MCP endpoint. See Connect from.