WeSearch

Show HN: Wasted Cycles – Local wall-clock profiler for AI coding agents

·4 min read · 0 reactions · 0 comments · 2 views
#devops#ai#profiling#software#tools
TL;DR · WeSearch summary

Wasted Cycles is a local wall‑clock profiler that measures how much time AI coding agents spend blocked on external compute resources such as compilers, tests, CI, and containers. The tool runs without installation, accounts, or network uploads, reading existing trace files on the machine and presenting a breakdown of agent work versus blocked time. It supports multiple trace formats, classifies segments into working, blocked, and non‑counted categories, and highlights the highest‑impact bottlenecks for developers to address.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 2,958 of its stories.

Original article
Github
Read full at Github →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

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 publisherGithub
Canonical URLhttps://zozo123.github.io/wasted-cycles/
Publication timeThu, 30 Jul 2026 15:47:05 +0000
Retrieval time2026-07-30T15:48:26.475Z
Last seen2026-07-30T15:48:26.475Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClustermzIOz9eRXxju · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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

Local wall-clock profiler WASTED CYCLES Find the machines your coding agent is waiting on. A wasted cycle is time your agent spends blocked on compute it does not control — compiling, running tests, waiting on CI, provisioning containers, fetching packages, joining sub-agents. Wasted Cycles reads the traces already on your machine and shows how much of a run was that, and which machine to fix first. Time spent waiting on a person is not a wasted cycle: it is reported separately and never enters the metric. Copy $ curl -fsSL https://raw.githubusercontent.com/zozo123/wasted-cycles/main/run | sh No install, no account, no daemon, no API key, no upload. The runner downloads a checksum-verified binary into a temporary directory, runs it, and deletes it on exit.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Github.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Github