#Hermes hangs with Ollama Cloud Kimi; google-workspace MCP causes ToolProperty 400

1 messages · Page 1 of 1 (latest)

stoic flume
#

Issue: Hermes hangs at “Initializing agent...” with Ollama Cloud Kimi.

Trying to use:

  • Hermes v0.11.0 (2026.4.23), upstream e5647d78
  • Ubuntu 24.04.4 LTS over SSH
  • Provider: custom
  • Model: kimi-k2.6:cloud
  • Endpoint: http://127.0.0.1:11434/v1

What happened:
Hermes hung after:
Initializing agent...

Earlier separate issue:
google-workspace MCP caused:
HTTP 400: json: cannot unmarshal string into Go struct field ToolFunctionParameters.tools.function.parameters.properties of type api.ToolProperty

What I tried:

  • Updated/restarted Ollama
  • Direct Ollama API worked with stream=false and stream=true
  • Disabled all MCP servers in ~/.hermes/config.yaml
  • Killed stale Hermes/MCP processes
  • Ran hermes memory off
  • Disabled streaming in config

Current result:
hermes chat --toolsets web -q "Say OK only" now works and returns OK in 11s.

Remaining issues:

  1. hermes dump said mcp_servers: 0 even when config had enabled MCP servers and run_agent loaded them.
  2. google-workspace MCP still seems to cause the ToolProperty 400.
  3. Hermes banner showed MCP servers as failed even after disabling them.
  4. Kimi/Ollama Cloud streams delta.reasoning; maybe related to earlier hangs.

Logs:
https://paste.rs/u4Bvz
https://paste.rs/pxxvK

woeful trench
#

Thanks, this helps. The kimi-k2.6:cloud + http://127.0.0.1:11434/v1 setup is expected for Ollama Cloud: the local Ollama daemon is the OpenAI-compatible proxy, even though the model itself is running through Ollama Cloud.

Since hermes chat --toolsets web -q "Say OK only" is now returning OK, the base Ollama/Kimi path looks unblocked. The remaining thing to isolate is the Google Workspace MCP schema hitting Ollama's ToolProperty parser.

There are a couple related schema fixes open around this area:
https://github.com/NousResearch/hermes-agent/pull/14870
https://github.com/NousResearch/hermes-agent/pull/14977

Can you repro once with only that MCP server enabled and send the fresh output from:

hermes mcp list
hermes mcp test google-workspace
hermes chat --toolsets web,mcp-google-workspace -q "Say OK only"

If your MCP server is named something other than google-workspace, use the exact server name from hermes mcp list in the mcp-... toolset. Also send the matching ~/.hermes/logs/errors.log lines around the 400. If it still fails, the important part is the raw schema for the failing MCP tool, because that tells us which schema shape Ollama is rejecting.

stoic flume