`vulkro-sf ctx`

A code-reading server for an SFDX project, for any AI coding agent that can run a shell command. It returns just the part that answers, as numbered lines.

vulkro-sf ctx read FILE           # a small file whole, a large one as its outline
vulkro-sf ctx read FILE:NAME      # one method (FILE:Class.method works)
vulkro-sf ctx read FILE:120-180   # a line range
vulkro-sf ctx search NAME         # every definition, call and use, with its code
vulkro-sf ctx body NAME           # one Apex method and the lines that call it
vulkro-sf ctx impact NAME         # what depends on it, and the tests to run
vulkro-sf ctx check               # after an edit: what it broke
vulkro-sf ctx init                # tell the project's agents to use these

Other subcommands: callers, callees, map (the most central methods), and serve, stop, status for the background server.

search, body, impact and map read the Apex call graph, so a call such as AccountService.closeAccount(id) is tied to its method, and test classes are listed as the tests to run. A per-project background server keeps the graph warm: it starts on first use and exits after 15 idle minutes. It is offline and read-only.

ctx check reports call sites still on an old signature, removed names still used, syntax errors, and Salesforce findings (such as CRUD and FLS) on the lines you changed. vulkro-sf init --pre-commit runs it on every commit. MCP clients get the same through sf_read_code and sf_check_change.

Exit codes

Code	Meaning
`0`	Answered.
`1`	`check` found problems.
`2`	Error.

Exit codes​

Exit codes