Alternatives
Products that do what Blume.codes does
Turns coding agent sessions into better rules and skills Discussion | Link
- 1
- 2
- 3IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 4AF
Feb 2026 · github.com
- 5FC
2020 · app.showwcase.com
- 6LA
Jun 2026 · github.com
- 7CB
2021 · codeapprove.com
- 8CA
Jun 2026 · github.com
- 9AM
Jun 2026 · github.com
- 10LC
May 2026 · github.com
- 11CM
Feb 2026 · codingagents.md
- 12AR
Jul 2026 · github.com
- 13CA
Jul 2026 · codingagentsurvey.org
- 14MC
2013 · codeathing.com
- 15CF
2015 · code-fight.club
- 16MA
This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…
2025 · github.com
- 17SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 18DC
Mar 2026 · github.com
- 19LL
Jun 2026 · withlore.ai
- 20BC
We are a small group of undergrads interested in building human in the loop coding agents. We dream of a world where building complex agent workflows feels as simple and creative as playing with legos. When we were building stuff we needed a tool that made it easy to try out different code embedding models so that we could see which ones worked best in different scenarios and understand their strengths and weaknesses. So to speed that process up we made PurpleSearch an 'instant' search engine for your local codebases. This tool lets you quickly deploy any open source embedding model on…
2025
- 21SC
Apr 2026 · github.com
- 22AT
Apr 2026 · github.com
- 23CO
Jun 2026 · cate.cero-ai.com
- 24IB
Hi all, I'm sure some of the best engineers out here are having a hard time standing out nowadays. It's hard to evaluate and improve your skills, when AI is writing the code. Especially when a junior dev is sitting by your side and "accomplishing" 2x more than you. I didn't like this reality where the line between real talent and AI slop is blurring, so I decided to create a challenge, purely for the community, that is made to truly give a stage for talented devs to stand out in the age of AI. We encourage devs to bring their agents with them, because the challenge is built to not be…
May 2026 · theincidentchallenge.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →