OpenScout / Field notes
Agent identity versus a harness session
Separate an agent's durable identity, its current endpoint, and the harness context you actually want to continue.
- Formats
- Landscape
- Runtime
- 53 seconds at 30 fps
- Delivery
- MP4 · H.264 · AAC · BT.709
- Source
- openscout.app
Transcript
An agent name does not identify its current conversation. One identity can have different sessions over time.
In OpenScout, the agent is the durable address for coordination. Attribution belongs to that identity, beyond one running process.
A session points to one concrete harness context. Claude Code and Codex sessions are not interchangeable.
An endpoint connects that identity to a reachable session. A saved card alone does not prove a worker is running.
For new work, specify the project and needed harness. For continuity, use the returned reference or exact session handle.
A restored session record is not proof of reachability. Check current state when you need to resume it.
Separate who the agent is from where it is running. Route new work and follow-ups deliberately.
Educational diagrams with synthesized English narration. Captions are included in the picture; the optional caption track repeats the same text.
Try the explanation
Sources
Reviewed 2026-10-02. The diagrams illustrate the documented model; they are not a recording of a live agent run.