Agents & Machines
recheckSeatSignIn
Recheck Seat Sign In
Ask one of your machines to RE-PROBE its agent seats right now: whether the Claude, Codex and Cursor CLIs are installed, signed in, and able to complete a one-turn smoke.
Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "re-check the seats", and it calls recheckSeatSignIn.
Example call
The MCP tools/call params, with the required arguments only.
{
"arguments": {
"machineId": "<machineId>"
},
"name": "recheckSeatSignIn"
}Arguments
machineIdstringrequiredWhich machine to re-probe (machineId from listMachines).
Returns
The box resolves each seat's binary again, re-runs its authoritative sign-in checks, and runs the smoke through the same runner path a lane uses, then reports on its next heartbeat (seconds, not…
Ask for it
The Cloud routes these requests to this verb.
- re-check the seats
- my machine has codex installed but the fleet says it does not
- I just signed into Cursor
- refresh machine readiness
- why does it say the CLI is missing
Pair it with
The verbs that finish the job.
Questions
What does recheckSeatSignIn do?
Ask one of your machines to RE-PROBE its agent seats right now: whether the Claude, Codex and Cursor CLIs are installed, signed in, and able to complete a one-turn smoke. It is one of the tools The Cloud MCP server gives every connected AI.
How do I use recheckSeatSignIn from Claude or ChatGPT?
Connect your AI to The Cloud at https://mcp.thecloud.so/mcp and sign in once. Then ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "re-check the seats", and it calls recheckSeatSignIn.
Is recheckSeatSignIn safe to let an AI call?
recheckSeatSignIn changes your workspace. What an AI creates is Private until you share it.
Connect
One endpoint gives your AI this tool and every other one: connect Claude, ChatGPT, Cursor or Gemini, read what The Cloud is, or see pricing.