Selvedge vs Wasted Cycles

A local MCP server that AI coding agents (Claude Code, Cursor, Copilot) call as they work, logging the why behind every change into a SQLite file under .selvedge/ next to...

A local-first wall-clock profiler for coding agents and GitHub Actions. Find the machine time blocking progress.

About Selvedge

A local MCP server that AI coding agents (Claude Code, Cursor, Copilot) call as they work, logging the why behind every change into a SQLite file under .selvedge/ next to your code. Selvedge is a git blame for the why, a local MCP server your agent (Claude Code, Cursor, Copilot) calls as it works, recording the intent behind each change in the moment it makes it, not reconstructing it from the diff afterward.

About Wasted Cycles

A local-first wall-clock profiler for coding agents and GitHub Actions. Find the machine time blocking progress. Wasted Cycles, find machine time blocking agent work Skip to content. See how much agent time goes to builds, tests, CI, containers, packages, sub-agents, and repeated work, then fix the largest machine stall first. Wasted Cycles measures elapsed time, keeps human wait outside the metric, and gives you a small ranked list instead of a speculative ROI number. Read existing Codex, Claude Code, Cursor, and Grok Build traces in place.