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

opencode serve/web long waiting time #3124

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

Originally created by @bitgineer on GitHub (Nov 25, 2025).

Originally assigned to: @adamdotdevin on GitHub.

Description

  • Fix performance issue with /session/session/:id/status endpoint taking 2.5 minutes to return 1.2MB of data
  • Add pagination to status endpoint to prevent loading entire session history
  • Implement caching for frequently accessed session status data

Issue

The /session/:id/status endpoint is extremely slow, taking 2.5 minutes to return 1.198kB of data during initial desktop client loading

Changes

  • Added pagination parameters to status endpoint
  • Implemented response caching
  • Added data limits to prevent large payloads

Testing

  • Verified status endpoint now returns in <200ms
  • Tested with large session histories
  • Confirmed desktop client loads properly

OpenCode version

1.0.107

Steps to reproduce

  1. Start 'opencode web.'
  2. open web server
  3. Wait for the Status response to load

Screenshot and/or share link

Image

Operating System

WSL

Terminal

Wezterm

Originally created by @bitgineer on GitHub (Nov 25, 2025). Originally assigned to: @adamdotdevin on GitHub. ### Description - Fix performance issue with `/session/session/:id/status` endpoint taking 2.5 minutes to return 1.2MB of data - Add pagination to status endpoint to prevent loading entire session history - Implement caching for frequently accessed session status data ## Issue The `/session/:id/status` endpoint is extremely slow, taking 2.5 minutes to return 1.198kB of data during initial desktop client loading ## Changes - Added pagination parameters to status endpoint - Implemented response caching - Added data limits to prevent large payloads ## Testing - Verified status endpoint now returns in <200ms - Tested with large session histories - Confirmed desktop client loads properly ### OpenCode version 1.0.107 ### Steps to reproduce 1. Start 'opencode web.' 2. open web server 3. Wait for the Status response to load ### Screenshot and/or share link <img width="1920" height="919" alt="Image" src="https://github.com/user-attachments/assets/f51f61fc-b2dd-4745-8d88-788812e70f83" /> ### Operating System WSL ### Terminal Wezterm
yindo added the bugweb labels 2026-02-16 17:38:45 -05:00
yindo closed this issue 2026-02-16 17:38:45 -05:00
yindo commented 2026-02-16 17:38:45 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Nov 25, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #4402: "Is opencode web broken?" - Also reports issues with opencode web functionality
  • #3853: Black screen when running opencode web with CORS/HTTPS errors - web-specific performance/functionality issue
  • #3746: "Long prompt history stalls the app, long load time" - Similar issue with loading delays and stalling behavior
  • #811: "Text rendering is VERY slow (and CPU usage is really high)" - Related to performance degradation during rendering and high resource usage

Feel free to ignore if none of these address your specific case or if this is a distinct performance regression with the status endpoint specifically.

@github-actions[bot] commented on GitHub (Nov 25, 2025): This issue might be a duplicate of existing issues. Please check: - #4402: "Is opencode web broken?" - Also reports issues with opencode web functionality - #3853: Black screen when running opencode web with CORS/HTTPS errors - web-specific performance/functionality issue - #3746: "Long prompt history stalls the app, long load time" - Similar issue with loading delays and stalling behavior - #811: "Text rendering is VERY slow (and CPU usage is really high)" - Related to performance degradation during rendering and high resource usage Feel free to ignore if none of these address your specific case or if this is a distinct performance regression with the status endpoint specifically.
yindo commented 2026-02-16 17:38:45 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Dec 16, 2025):

Closing as we've made a ton of changes since this was opened and launched our beta yesterday, let me know if you hit any issues on latest.

@adamdotdevin commented on GitHub (Dec 16, 2025): Closing as we've made a ton of changes since this was opened and launched our beta yesterday, let me know if you hit any issues on latest.
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 bug web
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#3124
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?