---
id: post/gerardorenteria-blog/13945
type: post
title: "⚙️ GitHub Copilot: Workspace-Level Control Over AI Context 🔄"
summary: GitHub Copilot allows developers to organize and control AI context at the workspace level by enabling or disabling instructions, prompts, agents, and skills per project or client through settings.json configuration. This prevents style guidelines and rules from one client or project from interfering with work on another.
tier: community
language: en
tags:
  - github copilot
  - ai context
  - workspace settings
  - configuration
  - al development
  - instructions
  - agents
  - skills
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T01:56:33.076Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 96baee78bf49a8389482b05da1b991b92e45a1f194b40f8dbaa1553b4ade51c7
evidence:
  - kind: blog
    url: https://gerardorenteria.blog/2026/03/02/%e2%9a%99%ef%b8%8f-github-copilot-workspace-level-control-over-ai-context-%f0%9f%94%84/
    title: "⚙️ GitHub Copilot: Workspace-Level Control Over AI Context 🔄"
    date: "2026-03-02"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://gerardorenteria.blog/2026/03/02/%e2%9a%99%ef%b8%8f-github-copilot-workspace-level-control-over-ai-context-%f0%9f%94%84/
    title: "⚙️ GitHub Copilot: Workspace-Level Control Over AI Context 🔄"
    date: "2026-03-02"
    commit: null
    t: null
    quote: I think that giving Copilot the wrong context is almost worse than giving it none at all.
  - kind: blog
    url: https://gerardorenteria.blog/2026/03/02/%e2%9a%99%ef%b8%8f-github-copilot-workspace-level-control-over-ai-context-%f0%9f%94%84/
    title: "⚙️ GitHub Copilot: Workspace-Level Control Over AI Context 🔄"
    date: "2026-03-02"
    commit: null
    t: null
    quote: Then, activate or deactivate each folder from the workspace's settings.json file using true or false.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "13945"
source_id: gerardorenteria-blog
source_name: Gerardo Renteria
url: https://gerardorenteria.blog/2026/03/02/%e2%9a%99%ef%b8%8f-github-copilot-workspace-level-control-over-ai-context-%f0%9f%94%84/
published_at: "2026-03-02T17:18:22.000Z"
author: Gerardo Renteria
full_text: false
words: 718
quotes:
  - text: I think that giving Copilot the wrong context is almost worse than giving it none at all.
    why_it_matters: Highlights the importance of proper context isolation to avoid confusion and incorrect suggestions when working across multiple clients or projects
  - text: Then, activate or deactivate each folder from the workspace's settings.json file using true or false.
    why_it_matters: Provides the practical mechanism for controlling which AI context Copilot accesses without removing or reorganizing files
code_objects_mentioned: []
systems:
  - development
  - copilot
versions_mentioned: []
preview:
  embeddable: true
  frame_url: https://gerardorenteria.blog/2026/03/02/%e2%9a%99%ef%b8%8f-github-copilot-workspace-level-control-over-ai-context-%f0%9f%94%84/embed/
  image: https://gerardorenteria.blog/wp-content/uploads/2026/03/designer-2.png
  image_alt: null
  image_w: 1024
  image_h: 1024
  site_name: Gerardo Rentería Blog
  favicon: https://gerardorenteria.blog/wp-content/uploads/2020/11/cropped-wolficon.jpg?w=32
  probed_at: "2026-10-07T11:51:08.205Z"
---

# ⚙️ GitHub Copilot: Workspace-Level Control Over AI Context 🔄

[Read the post](https://gerardorenteria.blog/2026/03/02/%e2%9a%99%ef%b8%8f-github-copilot-workspace-level-control-over-ai-context-%f0%9f%94%84/) · Gerardo Renteria (Gerardo Renteria) · 2026-03-02 · 718 words · tier community · reviewed (checked by Opus)

> GitHub Copilot allows developers to organize and control AI context at the workspace level by enabling or disabling instructions, prompts, agents, and skills per project or client through settings.json configuration. This prevents style guidelines and rules from one client or project from interfering with work on another.

## Key points

- Organize AI context (instructions, prompts, agents, skills) into separate folders by client, project, or purpose
- Toggle context on or off per workspace using true/false switches in settings.json
- Use diagnostics in the Chat Configure menu to verify which context Copilot is actually using
- Prevents mixing of personal preferences, client rules, and company guidelines that could create conflicts
- Example folder structure separates AL development, TypeScript, security reviews, and client-specific instructions

## Quotes

- "I think that giving Copilot the wrong context is almost worse than giving it none at all." (Highlights the importance of proper context isolation to avoid confusion and incorrect suggestions when working across multiple clients or projects)
- "Then, activate or deactivate each folder from the workspace's settings.json file using true or false." (Provides the practical mechanism for controlling which AI context Copilot accesses without removing or reorganizing files)

## Context

- Features: workspace-level AI context control, instructions organization, prompts management, agents configuration, skills management, diagnostics

Source: Gerardo Renteria, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.