OpenCode is using CPU for doing nothing
OpenCode is reportedly using a significant amount of CPU resources while waiting for API rate limits. The application is consuming approximately 50% of a single core on an i9-14900 CPU despite being idle. This issue has been documented by a user on GitHub, raising concerns about its efficiency.
- ▪OpenCode is using around 50% of a single core on an i9-14900 CPU while idle.
- ▪The application is waiting for API limit rates, which leads to unnecessary CPU usage.
- ▪The issue was reported by a user named Jaaaky on GitHub.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/anomalyco/opencode/issues/19466 |
| Publication time | Sat, 23 May 2026 11:23:59 +0000 |
| Retrieval time | 2026-05-23T11:37:26.423Z |
| Last seen | 2026-05-23T11:37:26.423Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Ru-RcvpmExdy |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
anomalyco / opencode Public Notifications You must be signed in to change notification settings Fork 19.4k Star 164k Code Issues 5k+ Pull requests 931 Actions Projects Security and quality 2 Insights Additional navigation options Code Issues Pull requests Actions Projects Security and quality Insights {"payload":{"preloaded_records":{},"structured_data":{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"opencode is using CPU for doing nothing!","articleBody":"### Description\n\nWhile opencode is waiting for API limit rate - actually doing nothing -\n```\nResource has been exhausted (e.g. check quota).
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.