Caldera docs
calderaapp.io

The Claude account hint

A remote session started on an agent's machine starts in the Claude account that machine is signed in to, which in a team may be one person's. So that nobody is surprised, the runtime can report which account that is, and the agent's page shows it as a hint. Nothing is decided by it: there is no gate, no quota and no restriction.

What the runtime does

The runtime reads claude auth status when it starts and every three hours. That is a local call: it makes no model request and uses no quota. It runs on a thread of its own, so a slow claude delays no report. It finds claude on PATH, or where the installer puts it (~/.local/bin, ~/.claude/local), because a systemd service starts with a short PATH. It reports

{ "account": { "org": "Example Org", "plan": "max", "email": "someone@example.com" } }

All three fields are text and optional.

What it sends

Only three keys of the output are ever taken: orgName, subscriptionType and email. They become org, plan and email. Everything else that command prints (directories, ids, anything a later version adds) never reaches the report.

It sends no field at all when

  • there is no claude on the machine's PATH,
  • the call fails or prints something other than what is expected,
  • a refresh after three hours fails (a stale account is worse than none).

Who sees it

  • The agent's page shows a line in its Runtime panel: "Runs under the Claude account ..., organisation ..., plan ...". Every workspace member sees it there.
  • The email address is personal data of a person, and it stays inside that workspace. The overview lists no address.
  • The overview shows one note only when two agents of the workspace report different organisations.

Switching it off

A manifest can switch the field off with account: false; the runtime then never asks. An agent without Claude, or where the call fails, reports nothing and the page says nothing.

Why it exists

To make a mismatch visible: an agent that runs under another organisation's account than the rest of the workspace is easy to overlook, and a remote session on that machine would start there. The hint says what is the case; deciding what to do about it stays with the people.