Sessions
Sessions show the step-by-step path of governed agentic work.
Orlo does not run the agent. It records and governs consequential steps so reviewers can understand what happened.
Who Uses It
- agent product owners reviewing behavior
- platform teams debugging integrations
- risk and compliance teams inspecting tool-use controls
- audit teams reconstructing a trajectory
What It Shows
Sessions can include:
- session status
- governed steps
- tool checks
- policy decisions
- approvals
- retrieval citations
- state-change evidence
- lifecycle events
- trajectory results
- step-level path metrics
Why It Matters
Final answers are not enough for agent governance.
Sessions let teams inspect the path: which tools were requested, which actions were blocked or approved, and whether the agent respected the control boundary.