Skip to main content

CLI / install issues

b1e55ed: command not found

Most installs place the binary in ~/.local/bin.
1

Confirm the binary exists

2

Fix PATH for the current shell

3

Make PATH permanent

4

Reinstall (last resort)

uv: command not found

uv is used by the installer/tooling. It is also typically installed into ~/.local/bin.

API auth failures (401)

Symptoms:
  • API calls return 401 with auth.* error codes
  • CLI commands that talk to the API fail with auth errors
Fix by setting the API token in config or env.

Set via YAML

Set via environment variable

Then restart the API.

Kill switch active (HTTP 423)

When the kill switch level is > 0, POST /brain/run is blocked and returns 423 (kill_switch.active).

Check current level

Reset to level 0

Only reset after you understand why it fired (daily loss, portfolio heat, crisis threshold, or drawdown).

Database / event store issues

Verify integrity (hash chain)

If integrity fails, treat it as a stop-the-line moment until you understand the failure.

Rebuild projections

If projections look wrong after a manual repair or crash:

Identity / forge issues

Forge not finding the 0xb1e55ed prefix

This is normal: forging is a probabilistic search and can take seconds to minutes depending on CPU.
If it seems slow on a small VPS, let it run. Typical 2 vCPU shared VPS: ~30–120s.

macOS: quarantine blocks the forge binary

If macOS blocks execution due to downloaded binary quarantine:

Secrets & exposure

Worried about secrets leaking?

  • GET /api/v1/health is safe and intentionally minimal.
  • Do not expose config endpoints publicly (e.g. GET /api/v1/config) unless you understand the risk.
Recommendation:
  • bind API/dashboard to 127.0.0.1 and access via Tailscale or SSH tunnel
  • keep api.auth_token set

Logs

systemd logs

Port conflicts