Disconnect

pithy dashboard disconnect --env prod --yes

Deletes the registration. Every control-plane route on that environment goes back to answering controlplane/not_connected, which is where it started.

The row goes first

Revoking us is the wider version of this act, rotating and revoking a key is the narrower one, and connecting an environment is how to come back.

Then the management client is told, as a courtesy that cannot fail the command.

That ordering is the whole design. A dashboard that is down must not be able to keep a credential alive. If notifying were required, an outage on their side would mean you could not revoke — which is exactly backwards, because an outage on their side is one of the reasons you might want to.

dashboardNotified in the output says whether they were told. It never gates the revocation.

--local skips the call entirely

pithy dashboard disconnect --env prod --yes --local

Delete the row and tell nobody. Use it when the client is unreachable, when you do not want to wait, or when you would simply rather not.

The effect on your Worker is identical either way: the authority was always the row.

Re-running it is not an error

removed comes back false and the command exits 0. There is nothing to clean up and nothing to be confused about.

What it does not delete

Your data. Nothing here touches your users, purchases, audit events or anything else. It removes a credential’s registration.

Your audit trail. Everything that management client did is still recorded, under its own actor kind. That is usually the reason you are disconnecting, so removing the record with the access would be exactly wrong.

The capability. The seam stays composed and stays denying. Re-connecting later is one command.

Reconnecting

pithy dashboard connect --env prod

A fresh keypair, a fresh grant, a fresh row. Nothing survives a disconnect — which is the difference between this and revoking a key.

Verifying it worked

pithy dashboard status --env prod

connected: false. That is the shipped, denying state, and it is what a Worker that has never been connected reports too.

You can also watch it from the other side: every pane in the dashboard fails immediately, because the authority was your Worker all along.