Skip to main content

A subscription keeps asking to sign in

A subscription, such as a Claude subscription, runs tasks only on a node where it is signed in. Each node keeps its own sign-in, so most of these problems come from signing in on one node while another still needs it. The model accounts are under Directory › AI Accounts.

It asks to sign in again right after you did​

You signed in on a different node. A sign-in belongs to the node it ran on and doesn't move to another. Select ▸ beside the account's name to list its nodes, and read each row. A row that still reads Login needs its own sign-in: select Login there. To sign in once for all your nodes, share sign-ins between them: see Share model-account sign-ins between nodes.

It is still settling. For a few minutes after a sign-in the account shows ◌, initializing, until a node reports it. Wait, then look again before signing in a second time.

The problem isn't the sign-in. A node row that reads Billing needs the subscription paid, and Seat means the seat is suspended. A ▲ mark or the limit hit chip means the subscription's usage limit is reached. Signing in again fixes none of these: fix them with the AI provider, or wait for the limit to reset. See Find out why a model account isn't running tasks.

The provider ended the sign-in. Signing the subscription out everywhere at the provider, or changing its password, can end every node's sign-in at once. Sign in again with Re-login: see Sign a model account in again.

If a node still asks after a sign-in that reported Re-login complete — credentials refreshed., select your initials at the bottom of the sidebar, then Support, and raise a ticket naming the account and the node.

"No node in your organization is shared with you"​

You see No node in your organization is shared with you to run this on. Ask an operator for access. when you add a subscription or sign one in.

A subscription signs in on a node, and you can use only the nodes you can reach. You reach every node with an organization role, such as Org Owner or Org Admin. With only a role on a project, you reach the nodes that hold that project's worktrees, which may be none, for example while the project is new.

To fix it, do one of these:

When the message reads Your organization has no enabled node to run this on. Ask an operator to add one. instead, your organization has no node at all, or none enabled. Add one: see Add a node.