Multi-provider Reasonix (Go) & Zed

I’ve switched to the emerging Go version of the reasonix agent and managed to wire up other model providers in the first attempt. Here’s an example of making local Ollama and remote OpenCode Go models available:

[[providers]]
name        = "ollama"
kind        = "openai"
base_url    = "http://localhost:11434/v1"
models      = ["model1", "model2", "model3", …]
api_key_env = "OLLAMA_API_KEY"
context_window = 200000

[[providers]]
name        = "opencode-go"
kind        = "openai"
base_url    = "https://opencode.ai/zen/go/v1"
models      = ["model1", "model2", "model3", …]
api_key_env = "OPENCODE_GO_API_KEY"
context_window = 900000

Note that you only need OLLAMA_API_KEY for remote model access.

The main config.toml is at /Users/hrbrmstr/Library/Application Support/reasonix on macOS.

I had some trouble getting the Go reasonix ACP to work with Zed that ended up being reasonix not being able to parse the MCP servers config Zed passes to all ACPs on startup. Ultimately I disabled Zed’s MCPs (I rarely use the Zed Agent anymore) and this config then just magically worked:

"reasonix": {
  "type": "custom",
  "command": "/Users/hrbrmstr/bin/reasonix",
  "args": ["acp"],
},

I’m not quite sure where to file the bug report (likely in the reasonix repo).

The command path is where it is since I compiled the binary locally and moved it. Prior to that, I spent a few mintues with the source code looking for nasiness in the obvious places and then had Claude poke at it as well, and am comfortable enough that there is no additional nation state spyware in it (if you use DeepSeek’s models all privacy bets are off). I feel like this is the safest route for now.

The safety features of reasonix are turned on by default, which is another compelling reason to use it.

It’s not my daily driver yet but it seems like there is at least some value in kicking the tyres.