Releases

CLI releases

Tagged Waypoint releases publish the local server and CLI through npm and as a checksummed GitHub Release archive. The curl installer is recommended for agent workflows: it verifies the archive and installs the CLI and bundled Waypoint skill together.

npm is an alternative for registry-managed global packages. It installs the CLI only; add the Waypoint skill with the separate Skills CLI command shown in Installation.

curl -fsSL https://waypoint.logbookfordevs.com/install.sh | bash
# npm alternative: install the CLI and skill separately
npm install --global @logbookfordevs/waypoint
npx skills@latest add logbookfordevs/logbook-waypoint --skill waypoint --global

Update the installation you already use

Run waypoint update for an installed CLI. It updates through the original npm or GitHub channel and refreshes the Waypoint skill too; GitHub installs respect a saved --skip-skill choice. Then run waypoint restart and waypoint status so the running server uses the updated installation.

An older npm updater may not refresh the skill on its first upgrade to this behavior. Run the separate Skills CLI command from Installation once if your skill remains old; later waypoint update runs refresh it.

Manage the store extension through Chrome’s extension updates. For an unpacked source build, rebuild, reload it in chrome://extensions, and refresh your app tab. If Waypoint reports a compatibility mismatch, update the server and extension before retrying the workflow.

waypoint update
waypoint restart
waypoint status

Stop using Waypoint

Run waypoint stop to stop the local server. Remove its MCP entry from each agent where you configured it, and remove the browser extension through Chrome when you no longer need annotation tools.

For npm installations, use npm uninstall --global @logbookfordevs/waypoint. The GitHub installer’s --unlink option removes its managed launcher; it is not a full data wipe. Review and delete unwanted Annotation history through Data & Storage before removing the tools you use to access it.

Browser extension availability

The supported browser extension is available from the Chrome Web Store. Source builds remain available for contributors and local extension development.

Follow GitHub Releases for CLI versions and the repository documentation for development builds.