Viktor.comAn AI coworker that actually does the work
Make Claude Code cheaper and smarter
Cuts token waste and fixes loops in agents with no change.
12 followers
Cuts token waste and fixes loops in agents with no change.
12 followers
DedrooM is a lightweight proxy that automatically: Detects and blocks repetitive failing tool calls Intelligently mutates strategies using self-healing (new approach when stuck) Compresses bloated tool outputs (70-94% reduction in many cases) Just run: Bashpip install dedroom eval "$(dedroom init)" Key Features: dedroom init -> background proxy + shell setup Self-healing -> mutations on loops Real-time dashboard + savings report Works with Claude, OpenAI, DeepSeek, Ollama, OpenCode.
how does it actually decide when to mutate vs just retry, and does that logic adapt over time or stay fixed?
@erdiakkoc Great question!
The mutation decision is based on a combination of:
Repeat count (adaptive threshold that tightens on errors)
Recent trajectory (oscillation detection)
Error signals from the tool response
When we decide to mutate, we generate 3–4 strategy variations (parameter tweak, tool swap, decomposition, rephrase) and pick the most promising one using a fast heuristic scorer (with optional local LLM judgment).
The logic does adapt over time through our learning system successful mutations are remembered per project, so similar situations get better strategies in future sessions.
Happy to share more details if you're curious!
A dashboard is great, but consider exposing the mutation rules as configurable so users can tweak the retry and strategy logic to fit their own workflows instead of relying solely on the defaults.
@berke746137 Excellent suggestion thank you.
Configurable mutation rules is high on our roadmap. Right now we ship with balanced defaults that work well for most users, but we plan to add a dedroom rules command + config file so power users can define custom strategies and priorities.
Would love to hear what kind of rules you'd want to configure.
one thing i'd love here is a way to mark certain tool calls as "expected to be expensive" so the proxy knows not to compress them. sometimes i actually need the full output for debugging and it's annoying when it gets trimmed down before i even see it.
@yarenk8za Totally valid point.
We're adding a "protect" list in the next update you'll be able to mark certain tools or patterns as "do not compress" so you always get full output when you need it for debugging.
For now, you can use dedroom doctor to see what's being compressed and adjust via config if needed.
Thanks for the feedback!