Terminal Sessions And Transcript Behavior
Open browser terminals safely, understand reverse session flow through the agent, and know what transcript retention means operationally.
Terminal Sessions And Transcript Behavior
Terminal access is reverse-tunneled through the agent and coordinated by the API and web control plane.
Session flow
The user requests a terminal from the web UI, the API authorizes it, and the agent establishes the remote side of the session.
The operator requests a terminal-capable session from the dashboard.
The API authorizes the request against workspace access plus the current root-access policy for that node.
The agent binds the local PTY and the terminal websocket carries live IO.
Transcript chunks and session metadata are persisted for later review and lifecycle management.
Transcript model
Transcript chunks and session metadata are stored and queried separately. This allows:
- live session streaming
- later transcript review
- retention or cleanup handling without breaking active sessions
Operational implications
Terminal access is not just a websocket feature. It depends on:
- workspace scoping
- root-access policy
- agent connectivity
- realtime message delivery
Terminal failures are rarely “just websocket failures.” They are usually the product of auth, workspace access, node state, root-access policy, and transport health together.
Root Access Model And Composite Profiles
Understand how Noderax models elevated access and how composite profiles simplify repeated operational choices.
Updates Center
Understand the split Updates Center with separate control-plane and agent update surfaces, plus the freeze modal shown during control-plane apply.