Use case
C# software engineers, when having a coding agent refactor, rename or modify a symbol, need the full set of reference locations for that symbol across the project before deciding the change scope and handing it to the agent.
Engineers use the IDE's Find Usages or text search to locate references themselves, then paste or relay the results to the coding agent by hand, or let the agent grep and audit the output manually.
Coding agents default to text search (grep) for references, which misses overloads, generics, partial classes and conditional compilation, so changes land in the wrong places or miss some, forcing engineers to audit and rework afterwards.
xOcto's call
Demand is evidenced
The trend is that coding agents increasingly need compiler-level semantics rather than text search alone; an entry point is existing codebases in strongly typed languages such as C# and Java, starting with teams doing large-scale refactors. Pricing is not disclosed.
Reason to use it
Why users would choose it
Inference: versus manual Find Usages plus relaying, it delegates reference resolution to deterministic tree-sitter AST parsing, so the agent can query and cite graph positions directly, removing the step where engineers filter search results and relay them one by one; running locally with code never leaving the machine is an extra reason for teams wary of code leakage. No usage data or customer feedback is public, so sustained adoption cannot be confirmed.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Investigate further. Inference: versus manual Find Usages plus relaying, it delegates reference resolution to deterministic tree-sitter AST parsing, so the agent can query and cite graph positions directly, removing the step where engineers filter search results and relay them one by one; running locally with code never leaving the machine is an extra reason for teams wary of code leakage. No usage data or customer feedback is public, so sustained adoption cannot be confirmed.
Entry and what to borrow
The trend is that coding agents increasingly need compiler-level semantics rather than text search alone; an entry point is existing codebases in strongly typed languages such as C# and Java, starting with teams doing large-scale refactors. Pricing is not disclosed.