Session cockpit (availability)
The Community binary registers an availability descriptor for the
session-cockpit API namespace. That namespace currently has zero handlers
and no interactive cockpit. Requests under /v1/m/session-cockpit receive
404 by absence. The descriptor is not one of the 32 product modules in the
catalog.
Current availability
Section titled “Current availability”| Surface | Community (this artifact) |
|---|---|
| API namespace | session-cockpit (/v1/m/session-cockpit) |
| Descriptor | olivares.session-cockpit 0.1.0 — title Session cockpit (availability) |
| Registered routes / handlers | none |
| Interactive cockpit | none |
| Declared permission | session-cockpit:availability:read (declared, not routed) |
| Lifecycle | empty (Init / Start / Stop do nothing) |
A 404 on this namespace is the expected Community answer. It does not mean the control plane failed to install.
How to diagnose absence
Section titled “How to diagnose absence”Confirm that shipped session surfaces still work:
- Live session module routes under the
sessionsnamespace — Live operation & sessions. - Console Sessions (
/sessions, also/agentops) and Work (/work) — console reference. - Official CLI lifecycle in the next section.
If those respond and /v1/m/session-cockpit is 404, the descriptor matches this
artifact.
Open capabilities
Section titled “Open capabilities”Official CLI installation, launch, observation and management remain in the open Community product:
- Live operation & sessions — live agent
sessions, timelines, provider profiles, and
live_ref. - Operate a provider session — launch Claude, Codex or Grok under a pinned official binary.
- Run Claude Code with Olivares —
AgentOps co-deployment of official
claudesessions. - Connector and PEP-hook guides (observe/govern, not session launch): Claude Code, Codex, Grok Build.
- Privileged-session recording
- Identity, permissions & governance