Sessions

A session is one conversation with an agent, as a voice call or a text chat. A run in the web app and a call from a phone or glasses are the same kind of session, and each one leaves a written transcript your team can read.

Privacy

WorldAgents never records the audio or video of your sessions. The microphone and the camera are used live, to run the conversation, and are not kept.

What a session keeps is in writing: the transcript, and a timeline of what happened, such as the tools the agent called, the objects it recognized, and what its triggers decided. A picture is kept only when someone attaches one, or when a tool the agent uses has to save one to do its job, such as taking a photo.

The Privacy Policy has the full detail.

While a session runs

Choose Run on an agent in the web app. Talk to it, or open the Chat panel and type.

The menu on the stage opens two more views of the same session:

  • Inspector shows what the agent is working from: its instructions, what the camera recognized, where it places you on the map, which triggers acted and why, and its tools.
  • Events lists what happened, in order.

Review with AI ends the run and hands the session to Builder. Builder reads the transcript, says what it would change, and asks before changing anything.

Read past sessions

An agent's card shows how many sessions it has had. Choose Sessions in the card's menu to list them, each with its date, the device it ran on, and how many messages and tool calls it had.

Open a session to read the conversation with everything around it: tool calls, recognition, triggers, and errors. You can filter by kind, download the session, or delete it. A deleted session is gone for good.

Every member of an organization can read and delete its agents' sessions. Builder and a connected assistant can read them too, which is how they find out what went wrong before suggesting a fix.

Technical reference

Exact names, paths, values and limits, for developers and AI assistants.

  • An agent's sessions are at /org/<organization id>/agents/<agent id>/sessions, and one session at /org/<organization id>/agents/<agent id>/sessions/<session id>.
  • A session keeps the agent configuration it started with. A change to the agent shows in its next session.
  • Only the person who started a session can talk in it. Other members can read it.
  • A session with a public agent, started by a visitor who is not signed in, belongs to the agent's organization and is listed with its other sessions.
  • Connected assistants and Builder read sessions with read_sessions: pass an agentId to list sessions, then a sessionId to read one transcript. They cannot start a session.
  • How many sessions an organization can run at once depends on its plan.