optionOS optionOS
← All updates

Open an agent link; jump to the exact session and follow the work in Cockpit

Click an https://app.optionos.app/agent?provider={provider}&session={sessionId} link shown in a conversation and optionOS opens the exact agent session: it focuses a live agent and asks for your confirmation before re…

Cockpit

Click an https://app.optionos.app/agent?provider={provider}&session={sessionId} link shown in a conversation and optionOS opens the exact agent session: it focuses a live agent and asks for your confirmation before restoring a restorable agent. This experimental link flow requires optionOS Chrome Provider to be installed and enabled when used in Chrome. The card shows its state, attached conversation context, first and latest messages, and Git changes; live file tracking is opt-in and is not the default because it is costly.

Move from the link to the card, then the full Cockpit

The three-scene tour first shows the agent link inside the conversation and the required optionOS Chrome Provider surface, then walks through twelve areas of the experimental agent card, and finally shows Cockpit’s Claude, Codex, terminal, Ghostty, and Usage counts. Transcript copy, Fork, and Compact actions are experimental. Usage is also experimental and may not be fully accurate yet.

Ghostty conversation showing the optionOS Chrome Provider surface and an agent link to a different live Codex session Agent link inside the conversationoptionOS Chrome Provider requirement
Chrome Provider requirement
This row is not an agent; it is the provider’s wake/reload surface. It shows the Chrome-side prerequisite for the link flow.
The experimental agent-link flow used in Chrome requires optionOS Chrome Provider to be installed and enabled.
Check the Chrome Provider requirement and open the agent link in 1, inspect the card’s 12 areas in 2, then continue to Cockpit session and usage counts in 3.