Agent Context Is the Small Dev Tool Fixing the One Thing Every AI Coder Gets Wrong
Agent Context launched on Product Hunt today. It's a free VS Code extension by Gareth Marland that does one dead-simple thing: attach external project folders as clean references inside your workspace without contaminating your git repo. Your AI coding tool sees them. Your commits don't.
Why this matters. Every AI coder has the same workflow hack β you want Cursor or Claude Code to see how a similar feature was done in another codebase, so you copy-paste the files into a scratch folder, hope you remember to exclude them from commits, and pray. Or you open a second VS Code window and tab between them. Both suck. Agent Context just makes the other folder visible to the LLM context layer while keeping it out of the file tree your team works on.
The bet is that context quality is the #1 determinant of AI coding output quality. Anyone who's watched Claude Code rewrite a function correctly when it has access to the calling code, then watched it guess badly when it doesn't, knows this already. Marland is selling a micro-product that eliminates one specific friction in that loop. Free on the VS Code Marketplace, MIT-ish on GitHub.
This is what the tail end of the agent-tools ecosystem looks like right now. The Anthropics and OpenAIs build the models. The Cursors and Windsurfs build the IDEs. A long tail of single-maker utilities file off the remaining rough edges. Agent Context is a textbook entry in that tail β small surface area, one thing done well, free, ships today. It either gets acquired into a bigger tool or stays a forever-useful utility.
https://marketplace.visualstudio.com/items?itemName=dotstorming.agent-context
← Back to all articles
Why this matters. Every AI coder has the same workflow hack β you want Cursor or Claude Code to see how a similar feature was done in another codebase, so you copy-paste the files into a scratch folder, hope you remember to exclude them from commits, and pray. Or you open a second VS Code window and tab between them. Both suck. Agent Context just makes the other folder visible to the LLM context layer while keeping it out of the file tree your team works on.
The bet is that context quality is the #1 determinant of AI coding output quality. Anyone who's watched Claude Code rewrite a function correctly when it has access to the calling code, then watched it guess badly when it doesn't, knows this already. Marland is selling a micro-product that eliminates one specific friction in that loop. Free on the VS Code Marketplace, MIT-ish on GitHub.
This is what the tail end of the agent-tools ecosystem looks like right now. The Anthropics and OpenAIs build the models. The Cursors and Windsurfs build the IDEs. A long tail of single-maker utilities file off the remaining rough edges. Agent Context is a textbook entry in that tail β small surface area, one thing done well, free, ships today. It either gets acquired into a bigger tool or stays a forever-useful utility.
https://marketplace.visualstudio.com/items?itemName=dotstorming.agent-context
Comments