The vizzy CLI
The Vizzy app ships a vizzy command line tool. It uses the same engine as the app, with
no window required. It does four things:
- Render any
.vizzy.mdto images (PNG, JPEG, TIFF, HEIC, AVIF), so a coding agent can write a diagram and put the image in your repo. - Lint files for problems the renderer ignores: broken links, unsupported HTML, stray edges. You can gate CI on it.
- Control the running app: focus a node, jump to a document, open a hint, or read what a window is showing, so an agent can navigate the canvas with you.
- Publish a diagram or a whole folder to a shareable usevizzy.com
link. Sign in once with
vizzy login, then runvizzy publishfrom any script or agent.
Install the command line tool
Section titled “Install the command line tool”The CLI lives inside the app. On first launch, the app installs the vizzy launcher into
/usr/local/bin automatically if that folder is writable without admin rights. Often there
is nothing to do. Confirm it worked:
vizzy --helpvizzy version # print the installed versionIf vizzy is not found, install it explicitly:
- Vizzy ▸ Install Command Line Tool… in the app. You may be asked for your password if
/usr/local/binneeds admin rights. - Or headlessly, from a script or a coding agent. This is what usevizzy.com/prompt.md uses:
/Applications/Vizzy.app/Contents/MacOS/Vizzy install-cliinstall-cli never prompts. If the folder needs admin rights, it prints the exact
sudo … install-cli command to run and exits non-zero.
Each time you open Vizzy it re-links the installed vizzy to the running app, so moving
the app or updating it keeps the command working without reinstalling.
Open the app from the terminal
Section titled “Open the app from the terminal”Run vizzy with no subcommand to open the current folder, or pass paths to open
specific files or folders:
vizzy # open the current directory in Vizzyvizzy ~/Code/myproject # open a foldervizzy vizzy/auth.vizzy.md # open a single diagram fileThis reuses a running instance and focuses the existing window instead of launching a second copy.
Next steps
Section titled “Next steps”- Rendering to images:
vizzy render, output formats, and the agent loop. - Linting: the full rule list and how to gate CI on it.
- Controlling the running app:
focus,goto,open-hint,comment,state. - Publishing and sign-in:
vizzy login,vizzy publish, and how to publish from CI with a token.