--- title: Delivering controlled and concentrated context | daily.dev description: Stack Overflow announced its October release for Stack Internal and Stack Internal Community. New 'Scopes' create permission-governed context layers so teams... canonical: https://daily.dev/posts/delivering-controlled-and-concentrated-context-xywr8mvkw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Delivering controlled and concentrated context | daily.dev og:description: Stack Overflow announced its October release for Stack Internal and Stack Internal Community. New 'Scopes' create permission-governed context layers so teams... og:url: https://daily.dev/posts/delivering-controlled-and-concentrated-context-xywr8mvkw og:image: https://api.daily.dev/og/posts/XywR8Mvkw.png og:image:alt: Delivering controlled and concentrated context og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Delivering controlled and concentrated context **[Stack Overflow Blog](https://daily.dev/sources/stackov)** · 5 min read · 0 upvotes · 0 comments ## Summary Stack Overflow announced its October release for Stack Internal and Stack Internal Community. New 'Scopes' create permission-governed context layers so teams and AI agents only see relevant knowledge. A GitHub connector now ingests issues, pull requests, and docs into the verified knowledge layer while preserving GitHub access controls. Organizations can connect apps and MCP clients using service accounts instead of personal tokens. A new validation API lets teams monitor and sync validated knowledge back to sources like Confluence. Stack Internal Community adds animated GIFs, obsolete-post reasoning, and moderator tools. The release cites survey data: 75% of developers spend over 5 hours a week searching for information, and 79% discover critical context after they have already started a task. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are Scopes in Stack Internal and what do they do? Scopes are context layers in Stack Internal that let organizations shape knowledge into focused, permission-governed spaces. They control what knowledge is included and who can access it, delivering concentrated context to both humans and AI agents without noise or unauthorized exposure. Users can switch between project, team, or department scopes, or direct an AI agent to query a specific scope through the Model Context Protocol (MCP) server. _Teams scoping AI agent context by project or permission can compare approaches like this on daily.dev._ ### How does the Stack Internal GitHub connector handle access permissions? The GitHub connector enforces source-level permissions, preserving existing GitHub access controls for both humans and AI agents. It ingests engineering knowledge from org-owned code discussions, including issues, pull requests, and repo documentation, directly into Stack Internal's verified knowledge layer, automatically capturing high-signal decisions without manual upkeep. _Developers wiring repo knowledge into AI workflows can track connector permission models on daily.dev._ ### Why should service accounts be used instead of personal tokens for connecting apps to internal tools? Service accounts give applications a stable identity and standard OAuth flow instead of relying on personal tokens or shared user accounts. In Stack Internal, each service account is bound to one workspace with its own permissions, credentials, and auditable identity, letting security teams manage lifecycles while safely integrating Stack knowledge into enterprise-agent workflows. _Security teams weighing service accounts versus personal tokens can follow this trade-off on daily.dev._ ## Similar posts on daily.dev - [Anyone can start building verified knowledge with Stack Internal](https://daily.dev/posts/anyone-can-start-building-verified-knowledge-with-stack-internal-ndieqptvl) · Stack Overflow Blog · 0 upvotes · 0 comments - [Stack Overflow expands Stack Internal to give AI agents ‘trusted’ enterprise knowledge](https://daily.dev/posts/stack-overflow-expands-stack-internal-to-give-ai-agents-trusted-enterprise-knowledge-utxwinujn) · InfoWorld · 0 upvotes · 0 comments - [Your trusted knowledge layer: Introducing Stack Internal's new platform experience](https://daily.dev/posts/your-trusted-knowledge-layer-introducing-stack-internal-s-new-platform-experience-djz1x2uey) · Stack Overflow Blog · 1 upvotes · 0 comments - [2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence](https://daily.dev/posts/2025-8-release-introduces-stack-overflow-internal-the-next-generation-of-enterprise-knowledge-intel-27ikdaqid) · Stack Overflow Blog · 0 upvotes · 0 comments - [The end of Stack Overflow as you know it](https://daily.dev/posts/the-end-of-stack-overflow-as-you-know-it-7kw72dxy3) · LeadDev · 0 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#productivity](https://daily.dev/tags/productivity), [#mcp](https://daily.dev/tags/mcp), [#rag](https://daily.dev/tags/rag) [View this post on daily.dev](https://daily.dev/posts/delivering-controlled-and-concentrated-context-xywr8mvkw) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Delivering controlled and concentrated context","url":"https://daily.dev/posts/delivering-controlled-and-concentrated-context-xywr8mvkw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/delivering-controlled-and-concentrated-context-xywr8mvkw"},"datePublished":"2026-10-28T15:20:22.420Z","dateModified":"2026-10-28T15:28:33.352Z","description":"Stack Overflow announced its October release for Stack Internal and Stack Internal Community. New 'Scopes' create permission-governed context layers so teams...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/928246377970107fa314560afe99fde7?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/928246377970107fa314560afe99fde7?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Stack Overflow Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Stack Overflow Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/003e14873238469caea60ebdd34508ae","url":"https://daily.dev/sources/stackov"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/delivering-controlled-and-concentrated-context-xywr8mvkw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,productivity,mcp,rag","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Stack Overflow Blog","item":"https://daily.dev/sources/stackov"},{"@type":"ListItem","position":3,"name":"Delivering controlled and concentrated context"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/delivering-controlled-and-concentrated-context-xywr8mvkw#faq","mainEntity":[{"@type":"Question","name":"What are Scopes in Stack Internal and what do they do?","acceptedAnswer":{"@type":"Answer","text":"Scopes are context layers in Stack Internal that let organizations shape knowledge into focused, permission-governed spaces. They control what knowledge is included and who can access it, delivering concentrated context to both humans and AI agents without noise or unauthorized exposure. Users can switch between project, team, or department scopes, or direct an AI agent to query a specific scope through the Model Context Protocol (MCP) server. Teams scoping AI agent context by project or permission can compare approaches like this on daily.dev."}},{"@type":"Question","name":"How does the Stack Internal GitHub connector handle access permissions?","acceptedAnswer":{"@type":"Answer","text":"The GitHub connector enforces source-level permissions, preserving existing GitHub access controls for both humans and AI agents. It ingests engineering knowledge from org-owned code discussions, including issues, pull requests, and repo documentation, directly into Stack Internal's verified knowledge layer, automatically capturing high-signal decisions without manual upkeep. Developers wiring repo knowledge into AI workflows can track connector permission models on daily.dev."}},{"@type":"Question","name":"Why should service accounts be used instead of personal tokens for connecting apps to internal tools?","acceptedAnswer":{"@type":"Answer","text":"Service accounts give applications a stable identity and standard OAuth flow instead of relying on personal tokens or shared user accounts. In Stack Internal, each service account is bound to one workspace with its own permissions, credentials, and auditable identity, letting security teams manage lifecycles while safely integrating Stack knowledge into enterprise-agent workflows. Security teams weighing service accounts versus personal tokens can follow this trade-off on daily.dev."}}]} ```