Threads

Open in product: preshos.com/agent-ops/threads

A thread is the message-and-action line carrying one goal: the prompts, agent steps, tool calls, drafts, and decisions in the order they happened. Thread is the UI name — storage and the API call the same run of work a session. Either name points at the same thing: one bounded run under one environment and agent scope.

Names for the same work

Thread is what members see and open. Session is what storage and the API record. A thread reread tomorrow is the session record — nothing is lost between the two names.
Run is one attempt inside the thread: the agent tries, the transcript keeps every try, the outcome records the result.
The harness identity behind the run (Eve session) is platform-side. Members operate the thread; the harness name only matters when reading platform logs with support.

One thread, one goal

A thread starts with a bounded goal and ends with a recorded outcome. The goal does not change mid-thread; a new goal means a new thread.
Reused threads drift. Continuing yesterday’s thread for today’s task drags old context into new decisions — start fresh instead.
The thread transcript is the audit line: what was tried, what was approved or denied, what changed. It reads the same for the member, the admin, and the record.

Thread scope

The thread inherits its run target: local folder or cloud environment — runner, repository linkage, sandbox timeout, tool grants, and policy come from the session scope, not from the wording of any single message. The repository comes from the target, not the agent.
A thread that cannot reach a system is a scoping problem, not a prompt problem. Check the run target, not the phrasing.
Threads belong to their tenant and org scope. Session records are not portable across tenants.

Reading a thread: copy and timestamps

Messages carry copy and timestamp affordances: copy a message to lift its exact text elsewhere, and read the timestamp to place each turn in the run’s order. Quote the copied text and its timestamp when escalating — “the agent said X at that time” reconstructs faster than a paraphrase. Treat the product UI as the source of truth for the exact copy and timestamp controls.

Linked work beside the thread

Work attached to the thread opens as a single inspector Work item tab in the session’s right column — not a modal, not a jump to /items/workspace. One tab per thread, with Back history, widening like the Browser and document tabs. Full rule: Sessions.

What next

Projects: personal project groups — the history “+” starts a project-scoped thread carrying the canonical work item into the draft.
Sessions: the open-thread surface once work starts.
Starting a session: how the scope around a new thread gets set.
Working with sessions: running threads well day to day.