Agent server “opencode new thread” stuck on loading when workspace is Git repo

[cocohub001]

Reproduction steps

1. Open a workspace folder that contains a .git directory.
2. In agent-server, click “opencode new thread”.
3. Observe it remains stuck on “loading”.

Current vs. Expected behavior

Expected Result**
A new thread should open normally.

Actual Result
The UI remains in a perpetual loading state.

Notes**

• Works fine in a non‑Git folder (no .git directory).
• This seems directly tied to whether the workspace is under Git.

Zed version and system specs

• Zed version: [Zed 0.219.4 ]
• OS: [windows11]
• Agent server / OpenCode version: [Compatible with any version of Windows]

Attach Zed log file

Test files attached:

test: Reproduces the #[bug.]

test2: Works as expected.

test.zip

test2.zip

Relevant Zed settings

settings.json

// Zed settings
//
// For information on how to configure Zed, see the Zed
// documentation: https://zed.dev/docs/configuring-zed
//
// To see all of Zed's default settings without changing your
// custom settings, run `zed: open default settings` from the
// command palette (cmd-shift-p / ctrl-shift-p)
{
  "agent": {
    "always_allow_tool_actions": true,
    "default_profile": "write",
    "default_model": {
      "provider": "zed.dev",
      "model": "claude-sonnet-4-5-thinking",
    },
    "model_parameters": [],
  },
  "context_servers": {
    "mcp-server-context7": {
      "settings": {
        "context7_api_key": "",
      },
    },
    "github-mcp-server": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "",
      },
    },
    "sequential-thinking": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"],
    },
    "exa": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.exa.ai/mcp"],
      "env": {
        "EXA_API_KEY": "",
      },
    },
    "memory": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"],
    },
  },
  "telemetry": {
    "diagnostics": false,
    "metrics": false,
  },
  "terminal": {
    "shell": {
      "program": "pwsh",
    },
  },
  "base_keymap": "Cursor",
  "ui_font_size": 16,
  "buffer_font_size": 15,
  "theme": {
    "mode": "system",
    "light": "One Light",
    "dark": "One Dark",
  },
}

Relevant Keymap

keymap.json

(for AI issues) Model provider details

No response

If you are using WSL on Windows, what flavor of Linux are you using?

None

[smitbarmase]

Do you see the same issue with the Opencode CLI tool? It’s possible this is coming from upstream.

[vincentferniot]

Hi,
It seems related to this issue #43335
Looks like a PR has been shipped to OpenCode

[cocohub001]

Do you see the same issue with the Opencode CLI tool? It’s possible this is coming from upstream.

---

I have updated opencode to the latest version v1.1.23.

While the previous issue (models not loading) is resolved, I am encountering a new problem specifically within Zed. After selecting a model and sending a prompt, the UI shows an infinite loading spinner and never returns a response.

Isolation Test (Crucial Context): I have verified that opencode works perfectly when run directly in the terminal (CMD) within the same Git repository folder. I can send prompts and receive answers via the CLI without any issues. The problem is isolated to the Zed editor / agent-server usage.

Steps to Reproduce:

Open a workspace folder that contains a .git directory in Zed.

In agent-server, click "opencode new thread".

The model list loads successfully; select any model.

Enter a prompt in the input box and click "type to send".

Result: The response indicator spins indefinitely inside Zed, while the CLI works fine.

Environment:

OpenCode Version: v1.1.23

Editor: Zed 0.219.4 (via agent-server)

OS: Windows 11

[github-actions]

Zed development moves fast and a significant number of bugs become outdated. If you can reproduce this bug on the latest stable Zed, please let us know by leaving a comment with the Zed version, it helps us focus on the right issues. If the bug doesn't appear for you anymore, feel free to close the issue yourself; otherwise, the bot will close it in a couple of weeks. But even after it's closed by the bot, you can leave a comment with the version where the bug is reproducible and we'll reopen the issue. Thanks!