As for me, chatting with agent is really annoying. I write prompt, the agent replies, I correct it, it generates code, I need to skim througt it, correct againg, again and again. There are two big problems: context polution in agent history and simply unconvenient chatting UX.
Instead of this I tried to build workflow where I do not need to chat. Actually, we already have a methodology that allows not to polute context – it called Spec Driven Development. I started to use the basic specs on the very begining of my journey with agents. But I used them in a very simple way. Firstly, I prepare a specification with an agent, and then I give it to another agent. But I still need to use a chat. Is is mostly annoying in a code review process. I need to reference some parts of code (many of them) and input my corrections into a chat window.
That's why I started to build SpecBuddy. It is a plugin for IntelliJ-based IDEs that supports simple Spec Driven Workflow – around spec itself, not around a chat. I can write documents, review them, review code, send it back to agent, and everything of it – without even a line in a chat window.
For now it works with Claude Code, Codex and OpenCode and support my own simplified spec-driven workflow, but soon OpenSpec will be supported.
If you are interesting in, please, take a look. -> https://specbuddy.dev
Top comments (0)