Sessions, turns, and attempts
A new attempt never means a new prompt, so Opengeni can recover a turn after a worker dies without repeating it.
The event log
Every session event is stored in Postgres with a sequence number. Clients read it two ways:- Replay: fetch events after a sequence.
- Stream: subscribe over Server-Sent Events. The SDK resumes by sequence after a drop and fills gaps from replay.
Sending input
- Send appends a prompt. If a turn is running, the message queues behind it. Queued messages stay editable and reorderable until they start.
- Steer moves your message to the front, and the agent reads it within seconds without stopping work in progress. If the agent is still writing its answer, that answer is cut short (what it had finished stays) and the agent starts again with your message. Short tool calls finish first; long waits on commands or other sessions return early and the work keeps running in the background. Several Steers sent close together are read together, in order. To stop the current work outright, use Pause or Cancel (API callers can also pass
interrupt: truetosteerQueueItem). - Pause and Resume hold and release the session.
- Cancel stops the session and its children for good.
busySend option.
If the session is waiting on you for an approval or a question, Send replaces that wait with your new prompt.
Attached context
A session can carry repositories, uploaded files, workspace documents, selected tools, and Skills. If you omit the tool list, the session uses the workspace default.Artifacts
The workspace Artifacts page collects Sites, documents, spreadsheets, presentations, images, and published files, with filters and search. A session’s Artifacts panel shows the outputs of that conversation. In the panel, click an image or file to view it large, then flip through the listed artifacts with the arrow buttons or the Left and Right arrow keys. Zoom an image with Cmd or Ctrl and plus or minus, a pinch, or the zoom buttons; click it to switch between fitted and actual size. Spreadsheet artifacts are editable in place: enter values or formulas, paste a range, and drag row or column header boundaries to resize them. Changes use the same live workbook in the session panel and full artifact view. Saving runs in the background; read-only access disables editing and resizing. The agent publishes the files it means to deliver; files it only writes to disk stay in the sandbox. Images, video, audio, and PDFs preview in chat. Other formats download.Child sessions
An agent can spawn child sessions for parallel or delegated work. Children are ordinary sessions. When one finishes, its final answer is delivered to the parent’s next turn.Visibility
Sessions in a shared workspace are visible to its members. An organization owner can let members create Only me sessions. Personal workspaces belong to one person.Connected accounts
Open Connectors in the composer to choose which connected accounts the agent may use. Each account is marked Only me or This workspace. Add accounts from the connector’s Capabilities page. Personal accounts belong to whoever sends the message, even in a shared session; other participants can’t use them by replying. Scheduled tasks use their owner’s accounts. If you attach several accounts, say which one to use for actions that send or change data.Agent access in product integrations
agentAccess controls which other sessions an agent can reach in its workspace:
The stricter side wins, and children can only narrow their parent’s scope. This does not hide sessions from workspace members; your backend still authorizes each user’s requests.
The chat API defaults to private chats with
agentAccess: "session" (chats: "shared" uses "workspace"). Raw session creation defaults to "workspace". Access and Knowledge scope are set when a conversation is created. See Users, tenants & privacy.
Browsing and archiving
The sidebar groups sessions by project or creator. Active hides archived sessions; All shows them in a collapsed Archived folder. Archiving offers Undo for a few seconds, and you can restore later from Archived.Model settings
Follow-ups without an explicit choice reuse the model, reasoning effort, and speed of the latest turn. Child sessions inherit the parent’s model and reasoning effort but start at Standard speed. Subscription accounts belong to the organization and can be made available to everyone, selected workspaces, or selected people. Automatic selection prefers eligible shared accounts and keeps the selected account while its prompt cache is warm. Choosing an account changes the session’s preference; it never gives already-accepted background work access to another person’s account. If you own a personal subscription and are also an organization administrator, its Models account page offers Share account. Choose which workspaces may use it and explicitly confirm sharing. This makes it organization-managed without changing its credentials or conversation history. Other administrators cannot share your personal account for you. Consumer plans may limit use to the account holder. Codex, Claude and SuperGrok share account selection and capacity recovery. Cross-provider fallback requires an administrator-enabled policy, an exact configured model mapping, and a compatible conversation. Codex conversations using remote compaction remain Codex-only; deployments must separately activate cross-provider serving before those policies take effect.Voice input
Voice input in workspace settings sets the default transcription provider. Automatic transcription fallback tries another configured provider when the preferred one fails; that provider’s billing applies. Your recording is kept while transcription retries.Fast code search
When your deployment offers it, Fast code search in workspace settings gives agents acode_search tool that returns the most relevant source passages for a question about a codebase, in one call. It applies to sessions created after you turn it on.