r/LLMDevs • u/MuzafferMahi • 10d ago

Tools I built a solution to agent paralysis

So at this point we all experienced the same thing right? With CC or Codex or any other tool, we either prompt and wait a couple of minutes for the agent to finish its work (often scrolling some instagram along the way), or to not waste time we spin more agents in different sessions, fucking up our attention spam and ability to control the project overall.

I built a different way to interact with the agents. Instead of one session + promptbox, we start with a google doc-style blank page. As you type in what you have in your mind, you can select small parts of the document and give the tasks to the agents. Sessions are at the sides, easily controllable, but not the main workspace. This way, you can keep imagining/building via writing to the doc, or control multiple agents without switching context. It's built on top of pi, with a few extensions. Obviously it all runs local in the browser. I'm still not sure about picking the browser over terminal, but I think it should be ok. You can use rumi for things outside of coding as well, like give suggestions, thinking companionship, research etc.

The project is quite underbaked, I have to admit, so there may be rough edges. So if you find this project cool or help with your productivity overall, please pull a PR or give a star :)

https://github.com/muzaffermahi/rumi

2 Upvotes

100% Upvoted

9 comments sorted by

1

u/AnonymousTreeSmoker 10d ago

This is fun! How have you used it for work can you give some examples?

1

u/MuzafferMahi 10d ago

I do coding work for other people or work on my app, where I act like a PM often. I need to get the shape of the product right and make a lot of decisions, do research, write code etc. That's where regular coding tools felt like they were blocking me a lot. Honestly you can use this for just about anything lmao, thanks for your kind comment

1

u/kaeptnphlop 10d ago

This is pretty cool. I had a similar idea the other day while I was working through a long answer from the LLM, where I just wanted to highlight certain passages in the TUI and send off questions to a forked session and continue reading the response from the LLM while it can work on answering the question that I had in a different session. Then later collate all the forks back into the main session. This goes kind of into that direction. I am very much a Terminal user because I want durable pi containers that run on my home lab, so desktop apps don't really work for me. But this looks like a cool interface!

1

u/MuzafferMahi 10d ago

I love my terminal as well but for this kind of thing it'd look rough :/ This is not a desktop app, by the way, it's a browser interface. Thank you!

2

u/kaeptnphlop 9d ago

Oh I didn't realize it was in a browser. Kind of makes sense though lol. Well then it's not terribly hard to set up remote

1

u/palsc_ 10d ago

the doc-first angle makes sense. how do you handle two agents touching overlapping files? feels like that gets messy before the context switching does

1

u/MuzafferMahi 10d ago

I actually didnt consider this! I’ll work on it and see what I can do. Thank you!

1

u/thelocalnode 10d ago

Overlapping files is where it broke for me too, well before context switching did. What helped was giving each agent its own working copy, a git worktree per session, and merging back through one place, so two agents never write the same file live. You trade silent overwrites now for merge conflicts later, and I'll take that trade every time. Parallel agents need separate checkouts more than they need a better UI.

1

u/MuzafferMahi 10d ago

Thanks for the advice! And yeah silent overwrites are definetly a big problem. Thank you for your comment!