Skip to main content

Sessions and activity

"Session" means different things depending on context. CortexHub tracks each separately.

Browser login session​

Your sign-in to CortexHub Cloud. Manage active sessions under Account → Sessions.

MCP OAuth session​

The live grant between an MCP app and the gateway after you tap Allow on the consent screen. Admins see connection status on agent rows; revoking disconnects the app without deleting the agent identity.

Runtime / gateway runs​

Each governed tool invocation produces spans with policy decisions, redacted arguments and results, and linked receipts. Admins review these under Sessions, Audit, and Compliance views.

Co-worker chat session (hosted co-workers)​

When you chat with your co-worker in CortexHub Cloud (the Chat tab or the mobile app), or by DMing it in Slack, each conversation is a durable thread with full message history, and its Brain updates after each completed reply. A Slack DM thread keys its own co-worker session. This is separate from the gateway audit Sessions above.

SDK session grouping and context​

Programmatic clients can send an optional Mcp-Session-Id header (or X-Mcp-Session-Id) with your end-user conversation id. CortexHub groups SDK activity into separate session rows in Cloud per chat.

Optionally forward X-CortexHub-Conversation-Title and X-CortexHub-Last-User-Message (via the Python SDK conversation_title / last_user_message arguments) so admins see why a programmatic session exists. Interactive MCP clients (Claude.ai, Cursor) do not send these headers today.

In Sessions, admins see a session narrative built from agent-stated rationales on each tool call, plus SDK context when supplied. For hosted co-worker chat, each session row also shows which browser and device the member used (for example Chrome on Android) and their IP, with hover detail matching Account → Sessions. See Sessions and attribution.

Without a session id, activity from one OAuth client and agent appears as a single SDK session stream.

Retention​

Spans and audit data are retained per your plan (typically 365 days for spans; longer for audit and receipts). Enterprise plans may negotiate extended retention.

See also​