Add policy source tracking with metadata

[Copilot]

Policies configured on a user's machine now track their origin (account, device, or file) and associated metadata for UX purposes.

Changes

Core Infrastructure

• Added PolicySource enum (Account/Device/File) and PolicyMetadata type with source, accountSessionId, orgName, and details fields
• Extended IPolicyService with getPolicyMetadata(name: PolicyName) method
• Updated AbstractPolicyService to store and expose metadata alongside policy values

Policy Service Implementations

• AccountPolicyService: Captures account session ID and enterprise status when policies are set via GitHub Copilot account
• NativePolicyService: Tracks device policy source (Windows Registry, macOS defaults, Linux policy file)
• FilePolicyService: Records file-based policy sources with file path
• MultiplexPolicyService: Aggregates metadata from multiple policy sources
• PolicyChannelClient: Handles metadata serialization over IPC with type-safe interfaces

Developer Diagnostics

• Replaced reflection-based policy source detection with metadata system
• Added "Source Details" column to policy diagnostics table showing origin information

Example Usage

const metadata = policyService.getPolicyMetadata('PolicySettingB');
// Returns:
// {
//   source: PolicySource.Account,
//   accountSessionId: 'abc123',
//   orgName: 'Enterprise',
//   details: 'Set via GitHub Copilot account (Session: abc123)'
// }

Testing

• Added tests for account policy metadata tracking
• Added tests for multiplex policy metadata aggregation
• Added tests for metadata updates on account changes
• Tests use event-driven patterns and enum values for type safety

Original prompt

Start implementation

The user has attached the following file paths as relevant context:

• .github/instructions/learnings.instructions.md
• .github/copilot-instructions.md
• AGENTS.md

[Chronological Review: The conversation began with the user expressing a need to track how policies are set on a user's machine, specifically mentioning the defaultAccount and device policy. The user then requested to start the implementation of this tracking feature.]

[Intent Mapping:

• User requested to track WHO/HOW policies are set on a user's machine, specifically mentioning the defaultAccount and device policy.
• User explicitly stated, "Start implementation," indicating readiness to proceed with coding.]

[Technical Inventory:

• Technologies: TypeScript is being used, as indicated by the file extension and code snippets.
• Framework: The context suggests a focus on the VS Code extension architecture, particularly around policy management and user account handling.
• Architectural Decisions: The user aims to implement a feature that persists information about policy settings for UX display.]

[Code Archaeology:

• File Discussed: /Users/jospicer/dev/vscode/src/vs/base/common/policy.ts
  • Key Segment: The interface IPolicy includes a method for retrieving values based on an account.
• Current File: /Users/jospicer/dev/vscode/src/vs/workbench/api/browser/mainThreadChatSessions.ts is the active file where the user is working on the implementation.]

[Progress Assessment:

• Completed: User has outlined the requirements for tracking policy settings.
• Pending: Implementation of the tracking feature in the specified files.]

[Context Validation: All necessary context for continuing the implementation of the policy tracking feature is captured.]

[Recent Commands Analysis:

• Last Agent Commands: The user requested to start the implementation of the policy tracking feature.
• Tool Results Summary: No specific tool results were returned as the focus was on initiating the implementation.
• Pre-Summary State: The agent was actively working on the implementation in the file mainThreadChatSessions.ts when the token budget was exceeded.
• Operation Context: The commands executed were directly related to the user's goal of implementing a feature to track policy settings.]

1. Conversation Overview: - Primary Objectives: User requested to track how policies are set on a user's machine, specifically mentioning, "When a policy is configured on a user's machine, we want to track WHO/HOW it was set." - Session Context: The conversation flowed from outlining the requirements for tracking policy settings to initiating the implementation phase. - User Intent Evolution: The user transitioned from discussing requirements to actively starting the implementation.

2. Technical Foundation:

• TypeScript: Used for coding the VS Code extension.
• VS Code Extension Architecture: Focus on policy management and user account handling.

3. Codebase Status:

• File Name: /Users/jospicer/dev/vscode/src/vs/base/common/policy.ts
  • Purpose: Defines the IPolicy interface for managing policy values.
  • Current State: Relevant lines discussed include the method for retrieving values based on an account.
  • Key Code Segments: The interface includes a method that takes an account parameter.
  • Dependencies: This file is integral to the policy management system.
• File Name: /Users/jospicer/dev/vscode/src/vs/workbench/api/browser/mainThreadChatSessions.ts
  • Purpose: Active file for implementing the tracking feature.
  • Current State: User is currently working on this file.

4. Problem Resolution:

• Issues Encountered: None explicitly mentioned; focus is on implementation.
• Solutions Implemented: Not applicable yet as implementation has just started.
• Debugging Context: No ongoing troubleshooting mentioned.
• Lessons Learned: Insights will emerge as implementation progresses.

5. Progress Tracking:

• Completed Tasks: Requirements for tracking policy settings have been outlined.
• Partially Complete Work: Implementation in mainThreadChatSessions.ts is pending.
• Validated Outcomes: None yet, as implementation has just begun.

6. Active Work State:

• Current Focus: User is working on implementing the policy tracking feature in mainThreadChatSessions.ts.
• Recent Context: User requested to "Start implementation," indicating readiness to proceed.
• Working Code: No specific code snippets were modified recently as the focus was on starting the implementation.
• Immediate Context: User was preparing to implement the tracking feature when the summary was triggered.

7. Recent Operations:

• Last Agent Commands: User requested to start the implementation.
• Tool Results Summary: No specific results were returned as the focus was on initiating the implementation.
• Pre-Summary State: The agent was actively working on the implementation in mainThreadChatSessions.ts.
• Operation Context: The recent commands were executed to...

Created from VS Code.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.