Skip to content

Releases: haplollc/Vesalius

Release list

Vesalius 2.1.0

Choose a tag to compare

@jaredcassoutt jaredcassoutt released this 23 Oct 21:06

Two commands from nothing to answers, and a way to see whether Claude is using it.

brew install haplollc/tap/vesalius
vesalius setup
  • vesalius setup connects Claude Code for every project, and Codex when its command line is installed. It also
    lets Claude Code run the read-only tools without asking, checks that the server answers, and indexes the repository
    you're in. --dry-run shows the plan and --undo reverses it. It never writes to your repository, CLAUDE.md or
    hooks.
  • vesalius doctor starts the server the way Claude Code would and checks every link from the command to the
    index, printing a fix for anything that's off:
    • the registration and connection;
    • the server's tool list;
    • which repository it serves and how fresh that index is;
    • when it was last called over MCP.
  • vesalius stats shows what Claude asked: calls per tool, answer sizes, typical answer time, and how many
    completeness checks passed. It reads a local tally that records, per call, the repository path, the tool, and the
    answer's size and time. It never records questions, symbols or code. VESALIUS_STATS=off stops it.
  • Every tool declares the full set of MCP annotations. Read-only was already declared; 2.1.0 adds
    non-destructive, idempotent and closed-world.
  • vesalius --help groups the commands by what they're for.

What Claude sees is unchanged from 2.0.0: the same five tools, descriptions, server instructions and answers. The
benchmark was run on 2.0.0.

Download: vesalius-2.1.0-macos-arm64.tar.gz is one binary for Apple silicon, macOS 15 or later.
SHA-256: 337872c55c3ba2dcb2a10f1e06ade7abce1b32a98186e5953c2d9f8d654413a9. A copy downloaded in a browser is quarantined by macOS; Homebrew's copy isn't. To build from source instead, see the README.