Agent Sessions
What an agent session is
Section titled “What an agent session is”An agent session is Waldo’s durable record of one run.
Use the session detail page when you want to understand:
- what was started
- which prompt parts were sent
- whether the run completed or failed
- what successful Waldo mutations happened during the session
Session summary
Section titled “Session summary”The top card shows:
- status
- model
- started time
- updated time
- OpenCode session link
This is the fastest way to confirm whether the run finished and which model it used.
Prompt parts
Section titled “Prompt parts”The Prompt Parts section shows the text parts Waldo stored for the session.
Use this section to inspect the actual instructions and attached context that were sent into the run. This is especially useful when you want to compare two sessions or debug why a session behaved a certain way.
Event timeline
Section titled “Event timeline”The Event Timeline shows successful Waldo mutations recorded during the session.
Examples include:
- businesses created or updated
- contacts created or updated
- message patterns changed
- replies or scheduled messages sent
This timeline is useful because it ties actual product changes back to the session that performed them.
When to inspect a session
Section titled “When to inspect a session”Open a session detail page when:
- a run did the right thing and you want to reuse the approach
- a run changed Waldo data and you want to confirm what changed
- you want to inspect the attached context
- you want to jump back into the OpenCode session from the stored link