mirror of
https://github.com/hanzoai/mcp.git
synced 2026-10-15 12:30:12 +00:00
Hanzo CI/CD / test (linux-amd64) (push) Skipped
Hanzo CI/CD / test (linux-arm64) (push) Skipped
Hanzo CI/CD / test-advisory (push) Skipped
publish / publish (push) Successful in 57s
Hanzo CI/CD / test-amd64 (push) Successful in 10m22s
Hanzo CI/CD / cicd (push) Successful in 1m40s
CI/CD / cicd (push) Successful in 12m7s
A desktop app starts hanzo-mcp with no environment of its own, and `hanzo login` never writes an apiKey into ~/.hanzo/config.json, so on a fresh machine every Kai and Enso call answered NO_API_KEY. With no key set, hanzo-mcp now asks the hanzo CLI beside it (or at hanzo.sh's install path) for the login's token, `hanzo auth token`, and keeps it for five minutes. Never a hanzo found on PATH: the Hanzo IDE package installs /usr/bin/hanzo, which opens its window on any arguments. Claude-Session: https://claude.ai/code/session_01M8RoubcPN71KgJuZ8LdBUL