anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Implement MCP progress notifications #1392

New Issue
Closed
opened 2026-02-16 17:30:46 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 17:30:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @xhuw on GitHub (Aug 20, 2025).

Originally assigned to: @thdxr on GitHub.

https://modelcontextprotocol.io/specification/2025-03-26/basic/utilities/progress

I am writing am MCP server and the UI in opencode is underwhelming. It would be great if my mcp could use the "progress" notification to drive better user feedback. A widget which shows the latest feedback message and progress value would suffice. My MCP runs long running bash commands. So I expect my progress message would contain the last 20 lines of output or similar and expect the latest progress message to override the last one.

Not sure how many MCPs use progress, but its in the spec so it would be nice to see it in opencode

Originally created by @xhuw on GitHub (Aug 20, 2025). Originally assigned to: @thdxr on GitHub. https://modelcontextprotocol.io/specification/2025-03-26/basic/utilities/progress I am writing am [MCP server](https://github.com/xhuw/async-bash-mcp) and the UI in opencode is underwhelming. It would be great if my mcp could use the "progress" notification to drive better user feedback. A widget which shows the latest feedback message and progress value would suffice. My MCP runs long running bash commands. So I expect my progress message would contain the last 20 lines of output or similar and expect the latest progress message to override the last one. Not sure how many MCPs use progress, but its in the spec so it would be nice to see it in opencode
yindo closed this issue 2026-02-16 17:30:46 -05:00
yindo commented 2026-02-16 17:30:47 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Aug 20, 2025):

kinda interesting didn’t know that was part of the spec haha

@rekram1-node commented on GitHub (Aug 20, 2025): kinda interesting didn’t know that was part of the spec haha
yindo commented 2026-02-16 17:30:47 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1392
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?