Opaque "An error occurred while processing your request" (server_error) on tool-bearing calls, while plain replies (no tools) still work:
- Almost always TOO MANY TOOLS. Each connected MCP server adds its tools to the array the model receives; one big server (100+ tools) can push the total past the provider's limit, which then rejects EVERY tool call — not just that server's.
- Fix: a cap (OPENAGI_MAX_MODEL_TOOLS, default 128) advertises core tools + a budget of MCP tools and routes the rest through run_mcp_tool. Confirm the cap is in effect (look for the "[tools] N tools exceed model cap" log), lower it, or disconnect a giant server.
"Invalid 'tools[N].name' ... does not match pattern" error:
- An MCP server NAME (or a tool name) contains a space or punctuation, producing an invalid mcp_<server>_<tool> function name. Rename the server to letters/digits/_/- only.
Budget draining unexpectedly fast, especially while idle:
- Look for a MISPRICED model — a cheap nano/mini billed at flagship rates because a too-broad price-table prefix matched first. Verify the price table lists the exact model variant.
- Look for an UNGATED periodic job calling a big model every cycle regardless of new work (the autopilot pulse should skip when its agent queue is empty; API-diff syncs should spend $0 when nothing's new).

To inspect: use the structural health snapshot, the budget + ledger, and list_cron_jobs.

User asked: {{input}}

Más de este repositorio

mismo repositorio

setup-proactive-outreach

Spshulem/openAGI

Guide configuring proactive outreach so the main reaches out (digest + live decisions) and the Mac app surfaces it with notifications, an overlay list, and inline buttons.

2026-06-172

deploy-update-node

Spshulem/openAGI

Roll out new openAGI code to the main and to Mac nodes (iMessage / computer-use), and restart them safely.

2026-06-152

diagnose-no-imessage-replies

Spshulem/openAGI

Troubleshoot why the agent stopped replying to iMessages, in priority order.

2026-06-152

connect-mcp

Spshulem/openAGI

Connect an MCP server (catalog or custom URL/stdio) and make its tools usable — including completing OAuth on a headless host.

2026-06-152

drive-computer-use

Spshulem/openAGI

Operate a connected computer-use node to accomplish an on-screen task — screenshot, reason, act in a loop.

2026-06-152

schedule-recurring-check

Spshulem/openAGI

Set up a recurring check that only does work (and spends tokens) when there's something new — e.g. "every hour, check BuildBetter for new calls".

2026-06-152

name	diagnose-agent-tool-errors
description	Troubleshoot opaque model/tool failures and runaway budget — and their usual root causes.

Diagnose in this order; report the root cause and the concrete fix.

Opaque "An error occurred while processing your request" (server_error) on tool-bearing calls, while plain replies (no tools) still work:
- Almost always TOO MANY TOOLS. Each connected MCP server adds its tools to the array the model receives; one big server (100+ tools) can push the total past the provider's limit, which then rejects EVERY tool call — not just that server's.
- Fix: a cap (OPENAGI_MAX_MODEL_TOOLS, default 128) advertises core tools + a budget of MCP tools and routes the rest through run_mcp_tool. Confirm the cap is in effect (look for the "[tools] N tools exceed model cap" log), lower it, or disconnect a giant server.
"Invalid 'tools[N].name' ... does not match pattern" error:
- An MCP server NAME (or a tool name) contains a space or punctuation, producing an invalid mcp_<server>_<tool> function name. Rename the server to letters/digits/_/- only.
Budget draining unexpectedly fast, especially while idle:
- Look for a MISPRICED model — a cheap nano/mini billed at flagship rates because a too-broad price-table prefix matched first. Verify the price table lists the exact model variant.
- Look for an UNGATED periodic job calling a big model every cycle regardless of new work (the autopilot pulse should skip when its agent queue is empty; API-diff syncs should spend $0 when nothing's new).

To inspect: use the structural health snapshot, the budget + ledger, and list_cron_jobs.

User asked: {{input}}