Sessions
Open in product: preshos.com/agent-ops/sessions
A session is one bounded run of agent work: a goal, a scope, a transcript of actions, and an outcome. Sessions are the unit of work on PRESHos Platform. Members meet it as a thread — thread is the UI name, session is the storage and API name for the same run. The scope comes from the environment and agent picked at the start; everything after that happens inside the session shown here.
An open session shows three things at once. The transcript records the exchange: goal, agent actions, drafts, and decisions. The preview pane renders what the agent produces, such as a page or file, in a reviewable form. The reply box below keeps the agent moving with follow-ups.
Risky actions pause inside the session at the approval gate. The gate shows what the agent wants to do, on what, and why. The session proceeds or stops that line of action based on the decision, and both outcomes are recorded.
- Read the transcript as it goes. Catching drift at step 3 beats unwinding it at step 30.
- Question scope drift immediately. If there is no good answer tied to the goal, stop and rescope instead of approving through it.
- Prefer drafts as the default output. A draft under review beats an execution nobody asked for.
- Reply to steer, not to chat. Each message should move the goal, clarify scope, or answer the agent’s question.

Inside a session
Section titled “Inside a session”- Threads: the message-and-action line carrying the goal.
- Thinking: the visible reasoning behind agent actions.
- Working folder vs artifacts: scratch space against reviewable outputs.
- Plugins in session: how tools and skills get invoked while work runs.
Closing a session: checklist
Section titled “Closing a session: checklist”- State the result in one sentence. If that is not possible, the session was too broad.
- Confirm the record: attempted, approved or denied, changed, all present under the right org scope.
- Note friction with examples: repeated approvals on routine steps, missing tools, confusing scoping. That feedback goes to the tenant admin or builder.
- One goal per session. A second task means a second session.
What next
Section titled “What next”- Working with sessions: the full how-to on goals, scope, transcripts, and outcomes.
- Approving agent actions: the checks behind every allow or deny.
- Starting a session: agent and environment selection for the next one.

