picoclaw/pkg/mcp
dtapps 8d4cc3fbba fix(agent): make MCP initialization failure non-fatal
When all MCP servers fail to connect (e.g., network unreachable),
the agent loop would exit immediately, leaving the application in a
zombie state where the gateway is running but no messages can be
processed.

Changes:
- Downgrade MCP init failure from fatal error to warning in Run(),
  ProcessDirectWithChannel(), ProcessHeartbeat(), and Continue()
- Add 30s timeout to HTTP client used for SSE/HTTP MCP transports
  to prevent indefinite blocking on unreachable servers

The agent now continues operating without MCP tools when servers are
unavailable, rather than becoming completely unresponsive.
2026-04-30 22:56:40 +08:00
..
isolated_command_transport.go Feat/support isolation (#2423) 2026-04-08 18:15:42 +08:00
manager.go fix(agent): make MCP initialization failure non-fatal 2026-04-30 22:56:40 +08:00
manager_test.go fix(mcp): retry tool calls on lost HTTP sessions and fix client lifecycle 2026-04-24 20:20:57 +02:00