Turn repeated coding-agent corrections into rules/skills

Hacker News

Share card

Turn repeated coding-agent corrections into rules/skills

Hi HN, Peder here. My cofounder and I built Blume after coding agents ate our previous startup. While building our previous product we severely struggled with agent drift. Duplicated functions, incoherent architecture and sneaky production bugs. Worst being Fable, which writes such good looking code that you almost don’t notice deviant behaviour. We tried to enforce behaviour with all the best practices: rules, skills, docs, self-verification/testing etc. But they rotted faster than a human can maintain them, and using agents directly to maintain them just leads to bloat and more drift. So that is what we set out to solve. Blume is a desktop app that sits next to Claude Code, Codex and Cursor. It reads your agents' context setup (skills, rules, docs) and local session files. When you keep correcting the same things, blume proposes updates to your rules and skills as reviewable diffs. You approve or dismiss each one. To avoid bloat we extract intent, corrections, frustrations from agent sessions and group them into clusters. And when pain/recurrence thresholds are reached, only then an agent is sent to look for improvements. Analysis runs locally on your machine, using your local Claude Code or Codex harness. Your sessions/code are never sent to blume. It is free to use, with the only “cost” being limited token spend to extract signals and creating the improvements themselves. (We plan to monetise with optional cloud agents and team features going forward). The biggest gap in the product right now is that we don't yet measure whether an accepted change actually helped, in fewer corrections or fewer tokens spent re-explaining. We're working on that and think it's a core part of the product. Would love feedback, especially from anyone who's tried to keep agent rules/skills maintained across a team. Happy to answer anything about how it works.