Vihren Atlas

agentSideEffects.ts ×2

Code frontier

unlabeled · c_e0b3075263bc

3 tests · 49442 LOC · 290 files · introduces 0 tests · 19 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
3 ranges19 lines · 2 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
5010 ranges49442 lines · 290 files · Browse complete extent
All tests (intent)
3 testsBrowse complete intent

Neighbourhood graph

The orange circle is the focus. Violet and green circles are every ancestor and descendant, broader and narrower, at any distance; blue squares and pink diamonds are the introduced files and exact introduced tests of every visible concept, not only the focus's. Arrows point from broader to narrower concepts and bridge only concepts omitted from this view. Undirected links show source or test introduction. Concept and file size follows LOC; exact test nodes use test-count units.

Introduced files, introduced tests, and structurally relevant concept specialization

In the embedded map, ordinary wheel input scrolls the page; use the visible controls to zoom and drag to pan. Open the full-screen map for canvas navigation: wheel pans, Ctrl/Command plus wheel zooms, and arrow keys pan when this region is focused. On touch screens, open the full-screen map to pan or pinch. If JavaScript or WebGL is unavailable, use the native relationship evidence on this page.

Graph controls are ready.

Interactive rendering requires JavaScript and WebGL. Use the native relationship evidence on this page while the interactive map is unavailable.

Native relationship evidence

Every exact file and test below is linked only from the concept that introduces it.

Introduced tests

Every collected test enters the hierarchy at exactly one concept.

No tests are introduced at this concept. Its intent tests are introduced by other concepts.

Introduced code

Every collected source range enters the hierarchy at exactly one concept.

2 files ranked by introduced lines: 19 introduced LOC across 3 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

src/vs/platform/agentHost/node/agentSideEffects.ts 17 introduced LOC · 2 ranges

Open complete file

1321 }
1322 case ActionType.SessionConfigChanged: {
1323 > // Persist merged values so a future `restoreSession` can re-hydrate agentSideEffects.ts
1324 > // the user's previous selections (e.g. autoApprove).
1325 > const sessionState = this._stateManager.getSessionState(channel);
1326 > const values = sessionState?.config?.values;
1327 > if (values) {
1328 > this._persistSessionFlag(channel, 'configValues', JSON.stringify(values));
1329 > }
1330 > if (this._worktree && sessionState?.lifecycle === SessionLifecycle.Creating) {
1331 const sessionId = AgentSession.id(channel);
1332 const isolation = values?.[SessionConfigKey.Isolation];
1337 }
1338 }
1339 > // This case is reached only for client-dispatched config changes agentSideEffects.ts
1340 > // (a user picker edit); internal server-side writes use
1341 > // `dispatchServerAction` and never land here. So the provider can
1342 > // forward a live, session-mutable change (e.g. Claude's
1343 > // `permissionMode`) to its running SDK without re-entering its own
1344 > // tool callbacks.
1345 > this._options.getAgent(channel)?.onSessionConfigChanged?.(URI.parse(channel), values ?? {});
1346 > break;
1347 > }
1348 case ActionType.ChatToolCallComplete: {
1349 if (!chatChannel) {
src/vs/platform/agentHost/test/node/mockAgent.ts 2 introduced LOC · 1 range

Open complete file

160 readonly onSessionConfigChangedCalls: { session: URI; values: Record<string, unknown> }[] = [];
161 onSessionConfigChanged(session: URI, values: Record<string, unknown>): void {
162 > this.onSessionConfigChangedCalls.push({ session, values }); mockAgent.ts
163 > }
164
165 async getSessionMessages(session: URI): Promise<readonly Turn[]> {

Direct hierarchy

Parents

Children