Skip to content

Hapimatic Cloud — Recovering Access (Re-authentication) ​

INFO

Hapimatic Cloud is in pilot. This page is for pilot users.

If your instance stops being able to run Claude Code — because your Anthropic credentials expired, were revoked, or your subscription lapsed — you can recover it yourself from the browser, with no SSH and no terminal on your own machine. This page explains what you'll see and what to do.

When this happens ​

Claude Code on your VM authenticates with your Anthropic account. That authorization can stop working for ordinary reasons:

  • Your OAuth token expired.
  • You revoked the token (e.g. from your Anthropic account settings).
  • Your Anthropic subscription lapsed or changed.

When that happens, your instance can no longer start Claude sessions until you reconnect.

What you'll see: "Setup Required" ​

Your instance continuously checks that your credentials are not just present but actually valid — a stored token can look present while already being revoked. It confirms validity with a live check against Anthropic (and by inspecting the token's expiry). When it finds the credentials are no longer valid, it returns your instance to the "Setup Required" state — the same page you saw during first-time setup.

Presence is not validity

Your instance does not just check that a credentials file exists — it verifies the credentials still work. This is why a revoked-but-not-yet-expired token still triggers the Setup Required state. (This behavior is delivered by issue #1004, R11.)

How to recover — from the browser, no SSH ​

Sign in ​

Open your instance URL https://<your-subdomain>.hapimatic.com and sign in with Google as usual.

Reconnect on the Setup Required page ​

You'll land on the Setup Required page. Reconnect exactly as you did the first time:

  • Web Terminal (recommended) — a terminal in the page runs claude setup-token. Sign in to your Anthropic account and paste the token back. This uses your subscription (Pro / Max).
  • API Key — paste an Anthropic API key instead.

If the underlying cause was a lapsed subscription, renew or upgrade your Anthropic plan first, then reconnect here.

Confirm you're back ​

When authentication succeeds, your instance detects it automatically and clears the Setup Required state. Start a session to confirm you're back to normal.

You never need SSH to recover

The entire recovery path runs through the web UI. You do not need to SSH into your VM or run anything on your own computer. If you are ever asked to SSH in to fix authentication, stop and check with the operator — that is not the intended path.

The self-hosted core is licensed under AGPL-3.0.