anomalyco / anomalyco/opencode

TUI/Desktop: Bun/Effect stack dumped as collapsible tool block on every tool call (Build · grok-4.6)

Open
#49,324 0 comments 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Sep 16, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

On every tool call, the conversation pane inserts a collapsible block titled "Build · grok-4.6" with an OpenCode Bun/
Effect stack (not model output).

The block starts with "Click to collapse" and looks like:

  at A (B:/~BUN/root/chunk-k9zx24wq.js:67:13392)
  at <anonymous> (B:/~BUN/root/chunk-k9zx24wq.js:67:13895)
  at ~effect/Effect/evaluate (B:/~BUN/root/chunk-nhtrqkcr.js:25:4492)
  at runLoop (B:/~BUN/root/chunk-nhtrqkcr.js:25:2045)
  at evaluate (B:/~BUN/root/chunk-nhtrqkcr.js:25:1435)
  at <anonymous> (B:/~BUN/root/chunk-nhtrqkcr.js:25:5664)

The tools themselves usually complete (bash/edit/read succeed). The stack is not stored in the session DB or in
opencode.log — it only appears in the live UI.

This is not the same as #16841 (console.trace garbles the terminal; closed as not planned). Here the stack is rendered
as a collapsible tool/agent output block.

Provider: custom OpenAI-compatible grok-4.6 via @ai-sdk/openai (not official xAI).

Plugins

pebrel.js; MCP: reqable

OpenCode version

1.18.31

Steps to reproduce
  1. Windows 11, OpenCode 1.18.31 TUI/Desktop
  2. Select agent build and model grok-4.6 on a custom OpenAI-compatible provider (npm: @ai-sdk/openai)
  3. Send a prompt that causes a tool call (bash / read / edit)
  4. After the tool runs, a collapsible "Build · grok-4.6" block appears with the Bun/Effect stack above
Screenshot and/or share link
Image
Operating System

Windows 11 (build 26200)

Terminal

powershell7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.