Skip to content

Forward selfFetchManagedSettings in session.create#1846

Draft
joshspicer wants to merge 1 commit into
github:mainfrom
joshspicer:agents/managed-settings-forward-flag
Draft

Forward selfFetchManagedSettings in session.create#1846
joshspicer wants to merge 1 commit into
github:mainfrom
joshspicer:agents/managed-settings-forward-flag

Conversation

@joshspicer

@joshspicer joshspicer commented Jun 30, 2026

Copy link
Copy Markdown

Forward selfFetchManagedSettings in session.create

Threads an optional selfFetchManagedSettings flag from the SDK config through the session.create / resumeSession wire calls, so consumers can opt the runtime into self-fetching enterprise managed settings at session bootstrap.

  • nodejs/src/types.ts — add selfFetchManagedSettings?: boolean to SessionConfigBase.
  • nodejs/src/client.ts — forward it in the session.create and resumeSession payloads.

Purely additive and opt-in; unset behaves exactly as before. Runtime enforcement lives in the runtime PR.

Related PRs


⚠️ Draft — part of a 3-repo change (runtime + SDK + VS Code).

Add selfFetchManagedSettings to SessionConfigBase and forward it in the
session.create RPC payload. This allows hosts (e.g. VS Code AHP) to opt
the runtime into enterprise managed-settings self-fetch and enforcement.

Without this change, the field is silently dropped by the explicit field
list in client.ts and never reaches the runtime.

Requires: github/copilot-agent-runtime#agents/managed-settings-sdk-capability
@joshspicer joshspicer force-pushed the agents/managed-settings-forward-flag branch from 9fdb1a8 to ae591cc Compare June 30, 2026 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant