@mjovanovictech Your coding agent burns ~4,000 tokens answering one structural question and almost none of it is reading logic. It's grep, wrong file, grep again, then scrolling Program.cs for the DI registration
csmesh collapses that into one command 94ms. 73 tokens
@vrapolinario Your coding agent burns ~4,000 tokens answering one structural question and almost none of it is reading logic. It's grep, wrong file, grep again, then scrolling Program.cs for the DI registration
csmesh collapses that into one command 94ms. 73 tokens
https://t.co/B4Ho27ZhcT
@dotnet Your coding agent burns ~4,000 tokens answering one structural question and almost none of it is reading logic. It's grep, wrong file, grep again, then scrolling Program.cs for the DI registration.
csmesh collapses that into one command. 94ms. 73 tokens.
https://t.co/B4Ho27ZhcT
@davidfowl Your agent didn't burn 5,000 tokens understanding your code.
It burned them LOOKING for it.
And swapping grep for a "real" tool doesn't fix it. Call hierarchy, LSP references, tree-sitter graphs โ they all stop at the same wall.
https://t.co/B4Ho27ZhcT
Your agent didn't burn 5,000 tokens understanding your code.
It burned them LOOKING for it.
And swapping grep for a "real" tool doesn't fix it. Call hierarchy, LSP references, tree-sitter graphs โ they all stop at the same wall.
The wall is indirection. ๐งต
#csharp#dotnet
Your agent didn't burn 5,000 tokens understanding your code.
It burned them LOOKING for it.
And swapping grep for a "real" tool doesn't fix it. Call hierarchy, LSP references, tree-sitter graphs โ they all stop at the same wall.
The wall is indirection. ๐งต
#csharp#dotnet
dotnet tool install --global CsMesh
csmesh index
csmesh skill --install
Last line writes native rules for Claude Code, Cursor, Windsurf, Cline, Copilot, Codex, Gemini. Your agent starts reaching for it unprompted.
C#/.NET. Native AOT. MIT.
https://t.co/B4Ho27ZhcT
Your agent didn't burn 5,000 tokens understanding your code.
It burned them LOOKING for it.
And swapping grep for a "real" tool doesn't fix it. Call hierarchy, LSP references, tree-sitter graphs โ they all stop at the same wall.
The wall is indirection. ๐งต
#csharp#dotnet
The [di-bound] tag is the point. Two classes implement that interface; one is a test fake. csmesh ranks the one the container actually resolves.
And --budget is a hard cap. Too big? Exit 2 with a narrower query suggestion. It never floods your context.