You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2ea40b5
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: src/vs/sessions/contrib/providers/remoteAgentHost/REMOTE_AGENT_HOST_SESSIONS_PROVIDER.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ In the Agents Window, renaming a discovered sandbox session updates its owning M
30
30
31
31
In the Agents Window, opening or restoring a sandbox chat starts connecting or waking its environment in the background by default. Disabling `chat.agentHost.cloudSandbox.autoConnectOnOpen` leaves the environment disconnected until the user starts composing or explicitly connects. Both provider open preparation and content activation honor this preference; it does not cancel existing connections or prevent explicit attempts. Provider open preparation starts the connection without blocking, including for cached chats that skip content activation. Chat content activation shares that attempt and serves cached or recorded history independently. A history-backed content provider retains the session resource and chat model through its first live attachment; later live snapshots promote recorded history in place. Recorded peer and subagent transcripts follow the requested chat identity. Later live-provider replacement retains the existing reload lifecycle.
32
32
33
-
Normally interactive chats retain an editable local draft after their saved input has loaded. Connection progress and live-content failures remain hidden until the user types, pastes, or attaches context; input joins the existing attempt rather than starting another. Failed attempts retain the draft and require explicit Retry. Sending waits for the live chat model, and session settings wait for the authenticated connection. Archived and host-read-only chats remain read-only. Connecting never submits a draft automatically. The Editor Window retains its online-only connection-on-open policy without an offline-draft handoff.
33
+
Normally interactive chats retain an editable local draft after their saved input has loaded. Connection progress and live-content failures remain hidden until the user types, pastes, or attaches context; input joins the existing attempt rather than starting another. Failed attempts retain the draft and require explicit Retry. Sending waits for the live chat model, and session settings wait for the authenticated connection. Archived and host-read-only chats remain read-only. Connecting never submits a draft automatically. The Editor Window retains its online-only connection-on-open policy, but keeps offline drafts editable while sending is unavailable.
34
34
35
35
The window's Mission Control API service owns a bounded, account- and task-scoped memory cache of replayed history, independent of chat model disposal. Cached previews refresh silently. If recorded retrieval fails and live content cannot replace the preview, the existing status banner offers Refresh, which retries only the history API without waking compute or replacing the model. Connection feedback takes precedence when interaction requires it. Missing or incomplete refresh data cannot erase an already displayed transcript; authorization loss or a missing task instead surfaces the access error. Live attachment preserves cached data only when the transcript matches; differences and observed live changes invalidate it, and superseded in-flight reads cannot refill it. Authentication changes, feature teardown, task removal, and service disposal clear the relevant cache and cancel pending reads. Concurrent readers share a task read with independent cancellation. The cache stores neither credentials, raw event streams, nor live models, and survives neither restart nor account changes.
0 commit comments