3 ms·

Thanks. I added codex. Though, since I specifically mentioned agentic, I wanted to exclude non-agentic tools like prompt builders and context managers that you

Thanks. I added codex. Though, since I specifically mentioned agentic, I wanted to exclude non-agentic tools like prompt builders and context managers that you linked. :) Reason being: my idea of agents is to generalize well enough, so the need for workflow based apps isn't needed anymore. During discovery and planning phase, the agents should traverse the code base with a retrieval strategy packaged as a tool (embedded search, code-graphs, ...) and then add that new knowledge to the plan before executing the code changes.

paradite 1y ago
I don't think it's a black and white distinction between agentic and non-agentic tools. Not to mention tools are constantly evolving and changing. For example, Cursor a year ago was not agentic at all. GitHub Copilot only recently added agentic features. I also think the end game for an agentic tool would not an IDE, because IDE was designed for human workflows, not agents. I wrote about this topic a while ago and made a classification that's probably a bit outdated, but still relevant: https://prompt.16x.engineer/blog/ai-coding-l1-l5 https://prompt.16x.engineer/blog/ai-coding-l1-l5