Working with sessions

A session is one bounded run of agent work inside an environment: a goal, a scope, a transcript of actions, and an outcome. Sessions are the unit of work on PRESHos Platform. Run them well and governance mostly takes care of itself.

Anatomy of a good session

Element	Good	Smell
Goal	One sentence, verifiable result	“Look into…” or three goals at once
Environment	Matches the task’s systems and risk	Nearest or default environment regardless of task
Scope	Named systems, named exclusions	“Everything I can see”
Transcript	Read as it goes, question drift early	Skimmed at the end
Outcome	Recorded, one-line result you can defend	Closed tab, outcome unknown

Before you start: checklist

• Right tenant. Hostname matches the org whose work this is (org_id scoping starts here).
• Right environment. Its context covers your systems and its policy fits the risk.
• One goal. Written down, verifiable, scoped to the environment’s tools.
• Reversible first. Prefer reads and drafts; know which step would need approval.

While it runs

• Read the transcript as it goes. Catching drift at step 3 beats unwinding it at step 30.
• Question scope drift immediately. Ask why it is looking at system X. If there is no good answer tied to your goal, stop and rescope. Do not approve your way out of a misscoped session.
• Treat drafts as the default output. A draft you review beats an execution you did not ask for. Prefer tools that propose over tools that apply, and gate the apply step.

Run each session this way: start from one bounded goal, keep checking the transcript, continue while it stays on track, stop and rescope if it drifts. Route risky actions through an approval decision. Close with a recorded outcome.

After: close the loop

1. State the result in one sentence. If you cannot, the session was too broad.
2. Confirm the record. Attempted, approved/denied, changed, all present under the right org scope.
3. Note friction. Repeated approvals on routine steps, missing tools, confusing scoping: this is feedback for your admin or builder, with examples.

Session hygiene

• One goal per session. Starting a second task means starting a second session.
• Name sessions so future-you finds them (goal plus date beats “session 12”).
• Denials are outcomes, not failures. A denied action that should not have been proposed is a learning signal, so report it.
• Never share session URLs across tenants as if they were portable: records belong to their tenant and org scope.

When sessions go wrong

Symptom	Likely cause	Fix
Agent cannot reach a system	Tool or connector not provisioned for this environment	Check the environment’s tool list; ask admin (code is not connected)
Everything needs approval	Policy stricter than the workload needs	Report pattern to admin with examples
Nothing needs approval on risky work	Policy looser than it should be	Stop, report immediately, do not exploit it
Agent wanders off-goal	Goal too broad or wrong environment	End session, narrow goal, restart

More: User troubleshooting. Approval decisions in depth: Approving agent actions.