Troubleshooting

No Agent Handle Found

Set agent in code or CONFIGURE_AGENT in the environment.

new Configure({ apiKey, agent: "your-agent" });

For MCP, connect the client to https://mcp.configure.dev (or run npx configure setup); OAuth discovery supplies identity. No login command or saved handle is needed.

Tool Not Enabled

Connector and action tools must be enabled before profile.executeTool() can run them. Enable the action tools your app supports, then let execution enforce linked state, connector state, permissions, scopes, approval state, and product policy.

profile.tools({ actions: ["email.send"] });

(Legacy package MCP only: the hosted mcp.configure.dev server needs no env configuration.) For package MCP, connector and action environment values are validated. Unknown CONFIGURE_CONNECTORS or CONFIGURE_ACTIONS values fail at startup.

Commit Required

If MCP returns commit_required, call configure_profile_commit with bounded messages or toolResults from the surrounding turn. Include memories only for durable user facts, preferences, or intents; do not use provenance-only summaries. Do not use MCP commit for bulk import or raw transcript storage. Use configure_profile_import for that.

Connector Not Connected

If Gmail, Calendar, Drive, or Notion is not connected, connector-backed tools return a connector error. Call configure_connect with the matching app and give the user the returned link, then retry.

Legacy Routes

Legacy memory route aliases are not active. Use the SDK or /v1/profile/* routes.

Python Examples

Python examples are not included yet. Use the TypeScript quickstart for the current SDK flow.