Skip to content
PRESHaiPRESHaiPRESHos Platform

Starting a session

Open in product: preshos.com/agent-ops

Every session starts from the ops console with three picks: environment, agent, and work item. Those picks set the session scope before a single agent step runs, so starting well is mostly choosing well.

The session list shows past and running sessions in scope. The center composer takes one task description, with pickers for environment, agent, and work item. Open deliverables below track work already in flight — check there first so two sessions do not work the same item.

  • Agent decides who runs: prompt, model, tools, skills, and memory. Pick the agent the task needs, not the busiest one.
  • Environment decides where it runs: runner, repository linkage, sandbox timeout, GCP vars, capability restrictions, secrets, and policy. The repository comes from the environment, not the agent — wrong environment is the most common beginner mistake. Full scope split: Environments.
  • Work item attaches the session to tracked work so the outcome lands somewhere reviewable.
Agent Ops home with the session list, task composer with environment and agent pickers, and open deliverables

Starting checklist

Section titled “Starting checklist”

The composer takes one task description with pickers for environment, agent, and work item. Write the goal in one sentence, verifiable, scoped to what the environment tools can reach. Reads and drafts first — know which step would need approval before it arrives.

  • Hostname matches the org whose work this is. Same identity on another hostname is another tenant.
  • Goal written in one sentence, verifiable, scoped to what the environment tools can reach.
New session composer: task description with environment, agent, and work item pickers

The selectors name where the session runs and who runs it. Environment matches the task systems and risk; agent matches the workload. When none looks right, stop and ask the tenant admin instead of improvising.

  • Environment matches the task systems and risk. When none looks right, stop and ask the tenant admin instead of improvising.
  • Agent matches the workload. Agent Ops work goes to the Agent Ops worker or the agent the admin named.
Environment and agent selectors: execution target and configured agent picks

No environments visible means stopping and asking the tenant admin. Do not improvise around a missing environment.

What next

Section titled “What next”
  • Sessions: what the open-session surface shows once work starts.
  • Environments: the execution targets the picker offers.
  • Agents: the configured inventory the picker offers.
  • Your first session: the guided walkthrough of this exact flow.