session
An MCP session — a client connected, made some calls, disconnected. One node per unique client+project+branch combo, updated on reconnection.
| Metadata | Value |
|---|---|
| Plural | sessions |
| Subtitle field | client |
| Identity | client, projectId, gitBranch |
Fields
Section titled “Fields”| Field | Type |
|---|---|
client | string |
projectId | string |
gitBranch | string |
sessionType | string |
startedAt | datetime |
endedAt | datetime |
messageCount | integer |
tokenCount | integer |
Relations
Section titled “Relations”| Relation | Target |
|---|---|
participant | actor |
folder | folder |
Prior art
Section titled “Prior art”External standards this shape draws from or aligns with. See Shape design principles for how prior art informs shape design.
- Model Context Protocol (MCP) session — Direct source. Our client/sessionType come from MCP’s client/transport concepts (STDIO, HTTP+SSE).
- OpenTelemetry Spans (root span ≈ session) — Our startedAt/endedAt/messageCount/tokenCount align with span lifecycle + attributes in a trace context.
- OpenID Connect Session Management 1.0 — Classical web-session model. Our participant ≈ authenticated subject; projectId/gitBranch are AgentOS-specific scoping.
Skills that produce this shape
Section titled “Skills that produce this shape”- cursor —
op_list_sessions,op_backfill_session,op_get_session