Skip to content

Agent Ops

Agent Ops is the session runtime: the surfaces where agent work happens live. A session — called a thread in the UI — opens here, runs under an environment policy, pauses for approvals when actions carry risk, and closes with a recorded outcome. Everything in this section describes that happening work — not the configuration behind it.

Open in product: preshos.com/agent-ops

Agent Ops is the session runtime: the surfaces where agent work happens live. A session — called a thread in the UI — opens here, runs under an environment policy, pauses for approvals when actions carry risk, and closes with a recorded outcome. Everything in this section describes that happening work — not the configuration behind it.

The overview lists open sessions with goal, environment, and status per row. Each row opens the session it names: transcript, preview, and reply box for that run. Sessions close with a recorded outcome; the list keeps what is running and what already closed.

  • One goal per session; a second task means a second session.
  • Scope comes from the environment and agent picked at the start.
  • Risky actions pause at the approval gate inside the session.
Agent Ops overview: open sessions with goal, environment, and status per row
  • Agents: the configured inventory behind sessions — agents, environments, models, tools, skills, plugins, MCP, memory, providers, and knowledge.
  • Automations: scheduled and connector-driven work that fires without a live session.
  • Approvals: the human gate — queue, artifact review, and the allow/deny record.
  • Settings: tenant identity, membership, and security around all of the above.

The console scopes the work (environment, agent, work item). The session does the work under the environment policy. The gate pauses risky actions for a human decision. The outcome keeps the record. One goal per session; a second task means a second session.

New to sessions? Start with Your first session, then run day-to-day with Working with sessions.