Agents & Machines
reportPresence
Report Presence
Names your own presence node in the user's Agents panel.
Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "presence enrichment", and it calls reportPresence.
Example call
The MCP tools/call params, with the required arguments only.
{
"arguments": {
"sessionKey": "<sessionKey>"
},
"name": "reportPresence"
}Arguments
deviceLabelstringoptionalWhat this device is called on the node: e.g. "This device". Optional: omit it and the node is labelled from the surface (e.g. "claude-code session").endedbooleanoptionalSet true when this session is OVER (the chat was closed or archived, the seat is shutting down). The node leaves the Agents roster immediately instead of lingering until it ages out. Nothing is deleted: reporting the same sessionKey again…focusstringoptionalOne-line current focus, like a remote agent's status: e.g. "Orchestrating the build crawl". Optional: omit it and the node keeps its last focus (or a neutral "Working" on first report).kindstringoptionalThis local node's kind: "session", "subagent", or "builder". Omit to keep backward-compatible top-level session behavior.modelstringoptionalThe provider-native model id this session is running on: e.g. "claude-opus-4-8", "gpt-oss:20b". Shown on your node in the Agents view, humanized to a model chip ("Opus 4.8"). Omit when there is no model to report.parentSessionKeystringoptionalStable sessionKey of the local lead that orchestrates this node. Omit for a top-level session.projectstring | objectoptionalThe project this session is working in, derived from your current working directory (the panel never sees the user's disk, so report it). Accepts a bare name ("the-cloud"), an owner/name string ("tekalabs/the-cloud"), or a { label, repo?…projectIdstringoptionalTag this session to a Cloud Project (its projectId) so teammates in a Space the project is shared with see this live session in their Agents view: the same Space-visibility a dispatched agent gets. You must be a member of the project's…rolestringoptionalYour self-declared signing role: the third axis of the role · model · surface signature (surface + model are already reported above). e.g. "Ora GUIDE". Never the owner's name for AI-authored work. Omit to read under the plain "Ora"…sessionKeystringrequiredStable id for this local session: use the SAME value every turn so re-reports update one node instead of creating duplicates.statusstringoptionalAlias for focus: a status line lands on the node's focus instead of being dropped. Prefer focus; status is accepted for callers that speak it.surfacestringoptionalWhere this session runs. Omit it and the node KEEPS the surface it last reported; a node that has never named one reads as "claude-code", the local Ora case this tool reports. Name your ACTUAL editor when you are in one ("cursor",…
Returns
The registry does not declare a return shape.
Ask for it
The Cloud routes these requests to this verb.
- presence enrichment
- add my identity chips
- local subagent visibility
Pair it with
The verbs that finish the job.
Questions
What does reportPresence do?
Names your own presence node in the user's Agents panel. It is one of the tools The Cloud MCP server gives every connected AI.
How do I use reportPresence 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 "presence enrichment", and it calls reportPresence.
Is reportPresence safe to let an AI call?
reportPresence 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.