Warn business/enterprise users about org-managed vision capabilities

[Copilot]

Business and enterprise users with disabled editor preview features now see a warning when attaching images: "Vision capabilities is managed by your organization."

Implementation

• Added check in image.tsx after vision support validation:

  if (copilotToken && !copilotToken.isIndividual && !copilotToken.isEditorPreviewFeaturesEnabled()) {
    // Show org-managed warning
  }

• Warning rendered as omitted reference, matching existing vision unsupported pattern
• Unit tests verify condition logic (business/enterprise user + disabled preview features)

Original prompt

Implement this plan

[Chronological Review: The conversation began with the user requesting a warning message to be displayed when a user on a business or enterprise SKU has editor preview features disabled and attaches an image to their prompt. The user specified that the warning should state, "Vision capabilities is managed by your organization," and referenced existing implementation for similar warnings. The user then requested to implement this plan, indicating a desire to move forward with the coding task.]

[Intent Mapping:

1. User Request: "If a user is on a business or enterprise sku and has editor preview features disabled and attaches an image to their prompt I want to show a warning that says 'Vision capabilities is managed by your organization'."
2. User Request: "Look at the implementation for the warning shown when a user attaches an image when the model doesn't support vision for reference."
3. User Request: "Implement this plan."]

[Technical Inventory:

• Technologies: The conversation involves a codebase related to the "vscode-copilot-chat" repository, likely using JavaScript or TypeScript for implementation.
• Frameworks: The implementation may involve UI frameworks for displaying warnings (e.g., React).
• Architectural Decisions: The warning mechanism needs to be integrated into the existing chat functionality, ensuring it triggers under specific conditions.]

[Code Archaeology: No specific files or functions were mentioned in the recent exchanges, but the user referenced existing implementations for warnings related to image attachments.]

[Progress Assessment: The user has outlined a clear requirement and is ready to implement the warning feature. No coding has been completed yet, as the user just requested the implementation.]

[Context Validation: The user’s request for a warning message is clear, and they have provided specific conditions under which it should be displayed. The reference to existing implementations indicates that the user expects a similar approach.]

[Recent Commands Analysis:

• Last Agent Commands: The user requested to implement the warning feature based on their specifications.
• Tool Results Summary: No tool results were returned as the conversation focused on user requests and intentions.
• Pre-Summary State: The agent was actively preparing to implement the warning feature when the token budget was exceeded.
• Operation Context: The commands executed were directly related to the user’s goal of enhancing the chat functionality with a specific warning mechanism.]

1. Conversation Overview: - Primary Objectives: The user requested a warning message for users on business or enterprise SKUs with disabled editor preview features when they attach an image, stating, "Vision capabilities is managed by your organization." - Session Context: The conversation flowed from outlining the requirement to requesting implementation, indicating a clear path toward coding the feature. - User Intent Evolution: The user’s needs remained consistent, focusing on implementing a specific warning feature based on existing functionality.

2. Technical Foundation:

• Core Technology: The project is related to the "vscode-copilot-chat" repository, likely involving JavaScript or TypeScript.
• Framework/Library: Potential use of UI frameworks for displaying warnings, though specifics were not mentioned.
• Architectural Pattern: The warning mechanism needs to integrate with existing chat functionalities.

3. Codebase Status:

• No specific files were discussed, but the user referenced existing implementations for warnings related to image attachments.

4. Problem Resolution:

• Issues Encountered: None reported yet, as the implementation phase has not begun.
• Solutions Implemented: No solutions have been implemented yet.
• Debugging Context: No ongoing troubleshooting efforts were mentioned.
• Lessons Learned: No insights have been documented as the conversation is still in the planning phase.

5. Progress Tracking:

• Completed Tasks: No tasks have been completed yet.
• Partially Complete Work: The user has outlined the requirement and is ready to implement the warning feature.
• Validated Outcomes: No features have been confirmed working through testing yet.

6. Active Work State:

• Current Focus: The user is focused on implementing a warning feature for image attachments.
• Recent Context: The last few exchanges involved the user specifying the warning message and conditions for display.
• Working Code: No specific code snippets were discussed recently.
• Immediate Context: The user was preparing to implement the warning feature when the summary was triggered.

7. Recent Operations:

• Last Agent Commands: The user requested to implement the warning feature based on their specifications.
• Tool Results Summary: No tool results were returned as the conversation focused on user requests.
• Pre-Summary State: The agent was actively preparing to implement th...

Created from VS Code.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.