AI & Tech

What happened

GitHub released an August 2026 update for Copilot in Visual Studio, focusing on giving users more control over several key aspects of the tool.

The update expands control over how Copilot reasons, the models used, how teams share specialized agents, and when code reviews are requested.

Why it matters

Handing users finer-grained control means teams can align Copilot's behavior more closely with their specific workflows and quality standards.

Managing model choice and reasoning behavior could help organizations tailor AI assistance to different coding contexts and compliance needs.

Key facts

The update is dated August 2026 and applies to GitHub Copilot in Visual Studio.

It provides more control over Copilot's reasoning, model selection, team sharing of specialized agents, and timing of code review requests.

What to watch next

The blog post mentions highlights but does not detail them in the summary, so more specifics may be available in the full update notes.

Users may want to test the new controls to see how they affect daily coding and team collaboration.

Sources

• GitHub Changelog

What happened

GitHub has published its weekly release roundup for Copilot, dated August 24, detailing a new set of updates.

The changes focus on giving users more control over how Copilot operates, including support for team sessions within Slack and Teams.

Customization options are also being broadened across the Copilot app, the command-line interface, and supported IDEs.

Why it matters

These updates point to GitHub's push to make Copilot a more collaborative and adaptable tool, not just a code completion feature.

By extending team sessions to chat platforms, Copilot moves deeper into everyday developer workflows, while broader customization lets teams tailor the AI to their specific needs.

Key facts

The release is part of GitHub Copilot weekly updates for August 24.

The updates give users more control over how Copilot runs.

Team sessions are available in Slack and Teams.

Customization is expanded across the app, CLI, and IDE.

What to watch next

Future weekly releases may further refine how team sessions interact with coding projects.

Observation of how these customization options are adopted could signal the direction of Copilot's enterprise features.

Sources

• GitHub Changelog

What happened

Cloudflare has introduced BotBase for Operators, a dedicated space within the Cloudflare dashboard where bot operators can handle submissions to the company's directory of bots and agents.

The update brings submission status tracking and the ability to edit submissions after they are submitted.

A new behavior model allows operators to clearly specify how their bots consume content, improving transparency in the declaration process.

Why it matters

This gives bot operators a more structured and transparent path to getting listed, reducing friction and potential miscommunication about bot behavior.

By enabling precise declarations of content usage, the directory can become more trustworthy for users evaluating bots and agents.

Key facts

BotBase for Operators is located in the Cloudflare dashboard.

The update includes submission status tracking and submission editing.

Operators can use a behavior model to declare how their bots use content.

What to watch next

As more operators adopt the new tools, the quality and clarity of directory listings may improve, potentially shaping how bots are vetted.

Future iterations might expand the behavior model or add more submission management features based on operator feedback.

Sources

• Cloudflare

What happened

GitHub has announced that it will introduce three separate changes to Copilot policies and billing in the near future.

The company says these updates are designed to deliver a strong, consistent Copilot experience for users.

GitHub is asking users to review the changes to understand how they might be affected.

Why it matters

Because Copilot is widely used by developers, any shift in policy or billing could have a broad impact on workflows and costs.

The emphasis on consistency suggests GitHub is aiming to unify how Copilot is offered and billed across different user segments.

Key facts

GitHub is making three separate, upcoming changes to Copilot policies and billing.

The changes are intended to provide a strong, consistent Copilot experience.

Users are encouraged to review the upcoming updates to see what may impact them.

What to watch next

GitHub has not yet disclosed specific details about the three changes, so further announcements are expected.

Users should monitor the official GitHub changelog for detailed information as the updates roll out.

Sources

• GitHub Changelog

What happened

GitHub has expanded enterprise managed settings with a new option for plugin marketplaces. Administrators can now turn on automatic updates per marketplace rather than applying a blanket policy.

The feature works by setting autoUpdate: true on an extraKnownMarketplaces entry. Once enabled, supported clients automatically check the marketplace and apply updates on their own.

Why it matters

This gives enterprise administrators a more granular way to keep plugins current without manual overhead, while still controlling which marketplaces are allowed to update automatically.

It can reduce the risk of outdated plugin versions across managed environments, since supported clients take care of the checking and updating process once the setting is enabled.

Key facts

Enterprise managed settings now support autoUpdate for plugin marketplaces.

Individual marketplaces can be opted into automatic updates by setting autoUpdate: true on an extraKnownMarketplaces entry.

Supported clients automatically check the marketplace and update when autoUpdate is enabled.

What to watch next

Admins may want to test the new setting in a controlled environment to see how supported clients behave once autoUpdate is enabled.

It will be worth watching for any expansion of autoUpdate capabilities to other marketplace-related settings or client types.

Sources

• GitHub Changelog

What happened

GitHub announced today that it is gradually rolling out enforcement of a global model policy for generally available GitHub Copilot models.

The policy was first announced in July as a default for Copilot Business and Copilot Enterprise plans.

Why it matters

This move likely gives organizations a more predictable, standardized way to manage which AI models are used across their Copilot deployments.

Enforcement could mean tighter governance and fewer surprises for enterprises relying on Copilot for development workflows.

Key facts

The policy applies to generally available GitHub Copilot models.

It covers Copilot Business and Copilot Enterprise plans.

Enforcement is rolling out gradually starting today.

What to watch next

How the gradual rollout proceeds and when full enforcement is reached.

Whether organizations gain new controls or visibility into model selection as the policy takes effect.

Sources

• GitHub Changelog

What happened

The GitHub Blog has published a new tutorial aimed at developers who are new to the GitHub Copilot app.

The post walks through using the Copilot app to automate the triage of Dependabot pull requests, a task that often comes with managing library updates.

According to the post, keeping libraries up to date can be tedious, and the Copilot app is presented as a way to handle that repetitive work.

Why it matters

Dependency updates arrive regularly, and triaging each pull request by hand can eat into a developer's day. Automating this with the Copilot app could free up time for more productive work.

For beginners, learning to offload routine maintenance tasks to an assistant tool is a practical first step toward more efficient workflows.

Key facts

The guide is titled 'GitHub Copilot app for Beginners: Automate Dependabot pull request triage.'

The post is published on The GitHub Blog.

The Copilot app can handle repetitive tasks like Dependabot pull request triage.

Managing library updates is described as tedious.

What to watch next

The full tutorial is available on The GitHub Blog for those who want to follow along.

Developers may look for more beginner-focused guides on automating other GitHub workflows.

Sources

• GitHub

What happened

GitHub has rolled out a change that lets enterprise owners grant GitHub Apps access to enterprise billing data.

When creating or configuring a GitHub App, owners can now select the enterprise billing permission and choose the relevant settings.

This gives approved apps the ability to work with billing information inside the enterprise, as permitted by the owner.

Why it matters

The new permission expands what GitHub Apps can do within an enterprise, opening the door to custom integrations that rely on billing data.

It gives enterprises a formal, controlled way to let apps pull billing information instead of relying on manual exports or separate tools.

Because the access requires an explicit owner grant, it preserves oversight over sensitive financial data.

Key facts

GitHub Apps can now access enterprise billing data.

Enterprise owners can grant this access when creating or configuring a GitHub App.

The enterprise billing permission is a new selectable option for GitHub Apps.

What to watch next

Developers may begin building apps that use enterprise billing data for reporting, budgeting, or resource tracking.

Enterprises will need to decide which apps receive this new permission and how to manage the associated security risks.

GitHub may extend similar permissions to other enterprise-level data in future updates.

Sources

• GitHub Changelog

What happened

GitHub published a blog post detailing the lessons learned from evaluating large language models (LLMs) for real-world secret scanning.

The post focuses on the evaluation process before deploying LLMs in production environments.

Why it matters

Evaluating LLMs before production is critical to ensure they perform reliably in real-world applications, especially for security-sensitive tasks like secret scanning.

The lessons shared can guide other organizations in developing robust evaluation frameworks for their own LLM deployments.

Key facts

The evaluation was conducted for real-world secret scanning.

The post is from the GitHub Blog.

What to watch next

Future posts or updates from GitHub on their LLM evaluation methodologies.

How other companies adopt similar evaluation practices for their AI systems.

Sources

• GitHub

What happened

GitHub has announced the general availability of its rule insights dashboard, which is now accessible at both the repository and organization levels.

The dashboard provides a visual, high-level overview of how GitHub evaluates and enforces rules within a repository.

Why it matters

This feature gives developers and administrators a clearer, more intuitive way to understand rule enforcement, potentially simplifying compliance and governance.

By offering this visibility at both repository and organization levels, GitHub enables more effective management of coding standards and security policies.

Key facts

The rule insights dashboard is now generally available.

It is available at both the repository and organization levels.

It provides a visual, high-level view of how GitHub evaluates and enforces repository rules.

What to watch next

Watch for further enhancements to the dashboard, such as more detailed analytics or integration with other GitHub features.

Organizations may adopt this tool to streamline rule management and improve oversight.

Sources

• GitHub Changelog

What happened

GitHub has announced the general availability of the Customize tab in the GitHub Copilot app.

This new tab aims to make Copilot more useful by integrating with the tools, knowledge, and workflows that teams already use.

The Customize tab brings MCP (Model Context Protocol) support, as mentioned in the official summary.

Why it matters

The Customize tab addresses a common challenge: making AI assistants work seamlessly within existing development environments.

By allowing customization, teams can tailor Copilot to their specific needs, potentially improving productivity and adoption.

The integration with MCP suggests a move towards more standardized and flexible AI tool integrations.

Key facts

The Customize tab is now generally available in the GitHub Copilot app.

The feature is designed to work with the tools, knowledge, and workflows your team already relies on.

The announcement was made on the GitHub Blog.

What to watch next

Look for how teams adopt the Customize tab and what customizations they find most valuable.

Watch for further enhancements to MCP integration and its impact on Copilot's capabilities.

Observe user feedback and potential updates to the Customize tab based on real-world usage.

Sources

• GitHub Changelog

What happened

GitHub has introduced a new feature that allows repository maintainers to block a user directly from a security advisory page.

This capability is available for public repositories owned by either an organization or a personal account.

The feature aims to streamline the moderation process by integrating user blocking into the advisory workflow.

Why it matters

This update simplifies the moderation experience for maintainers, enabling them to take action against disruptive users without leaving the advisory context.

By reducing the steps needed to block a user, it helps maintainers respond more quickly to potential security threats or harassment within their projects.

The integration into security advisories underscores GitHub's commitment to providing robust tools for community management.

Key facts

Users can now be blocked directly from a security advisory page.

This feature applies to public repositories owned by organizations or personal accounts.

The change brings a streamlined moderation experience to security advisories.

What to watch next

It will be interesting to see if GitHub extends this blocking capability to other parts of the platform, such as issues or pull requests.

The impact on community moderation workflows and response times for security incidents will be worth monitoring.

Sources

• GitHub Changelog

What happened

GitHub has updated its rulesets feature to allow push rules to include path exceptions.

With this update, you can configure a push rule to apply to all file paths in scope, except for specific paths you choose to exempt.

The feature is now available in public preview.

Why it matters

This gives repository administrators finer-grained control over where push rules apply, enabling them to enforce policies more precisely without blocking legitimate changes to certain files.

By exempting specific paths, teams can avoid unnecessary friction in workflows that involve generated files or directories that should not be subject to the same rules.

Key facts

Push rules in rulesets now support path exceptions.

Path exceptions allow a rule to apply everywhere in scope except for chosen paths.

The feature is in public preview.

What to watch next

Watch for broader availability of this feature as it moves from public preview to general release.

Look for documentation updates and examples on how to effectively use path exceptions in rulesets.

Sources

• GitHub Changelog

What happened

GitHub announced a new plugin for its Accessibility Scanner that aims to ensure alt text is genuinely accessible, not just passing automated checks.

The plugin was developed to address the gap between automated validation and real-world accessibility, as automated checks often miss nuanced issues.

The announcement was made on the GitHub Blog, detailing the plugin's purpose and functionality.

Why it matters

Automated accessibility tools are valuable but have limitations; they can't fully assess the quality or context of alt text, which is crucial for screen reader users.

This plugin represents a step toward more meaningful accessibility practices, encouraging developers to consider the user experience beyond compliance.

It highlights the ongoing need for human judgment in accessibility, even as automation improves.

Key facts

GitHub built a plugin for its Accessibility Scanner to improve alt text quality.

The plugin aims to ensure alt text is actually accessible, not just passing automated checks.

The announcement was published on the GitHub Blog.

What to watch next

Will this plugin set a precedent for other accessibility tools to incorporate more nuanced checks?

How will developers adopt this plugin and what impact will it have on accessibility practices?

Could this lead to broader discussions about the limits of automated testing in accessibility?

Sources

• GitHub

What happened

Cloudflare announced that its blog now runs on EmDash, a move intended to demonstrate the capabilities of its own stack under real-world, high-traffic conditions.

The migration involved rigorous performance stress tests, careful routing of production traffic to ensure safety, and a complete redesign of the frontend experience.

Why it matters

By dogfooding EmDash on a high-profile property like the Cloudflare Blog, the company showcases the platform's ability to handle massive scale, which could build confidence among potential enterprise customers.

The stress-testing and safe traffic routing highlight a disciplined approach to migration, offering a blueprint for other organizations considering similar transitions.

Key facts

The Cloudflare Blog was migrated to EmDash.

The migration included stress-testing performance, safely routing production traffic, and redesigning the frontend.

The goal was to prove the stack at massive scale.

What to watch next

Observers will likely monitor the blog's performance and uptime post-migration for any signs of issues, which would reflect on EmDash's reliability.

The redesign may set a new visual standard for Cloudflare properties, and other teams might adopt EmDash if the migration proves successful.

Sources

• Cloudflare

What happened

Cloudflare has unveiled Bot Preference Sync, a feature designed to keep your robots.txt file aligned with your chosen AI bot policies.

The tool covers policy categories for Search, Agent, and Training bots, letting site owners manage access without editing static files by hand.

Why it matters

Maintaining a robots.txt file manually can become tedious as AI bot policies evolve, and mismatches can lead to unintended crawling or blocking.

By syncing preferences automatically, this feature removes a common source of friction for publishers trying to control how AI services interact with their content.

Key facts

Bot Preference Sync is a new Cloudflare feature.

It automatically aligns your robots.txt file with your AI bot policies.

The policies cover Search, Agent, and Training bots.

It allows easy bot access management without maintaining static files.

What to watch next

See how Cloudflare integrates this sync with existing bot management controls and whether it adapts as AI bot behaviors change.

The feature may set a precedent for how other platforms simplify robots.txt maintenance in an era of expanding AI crawlers.

Sources

• Cloudflare

What happened

GitHub has rolled out an update that makes managing blocked users faster and clearer for both personal accounts and organizations.

The new tools allow users to search blocked lists by username, full name, or email, and also support sorting and pagination for long lists.

Why it matters

These features address a common pain point for anyone who maintains large numbers of blocked users, reducing the time spent scanning or manually locating a specific entry.

By making moderation lists easier to navigate, GitHub is improving the overall experience for community managers and individual users alike.

Key facts

Blocked-user management is now faster and clearer for personal accounts and organizations.

Users can search by username, full name, or email.

Long lists can be sorted and paginated.

The update was announced on the GitHub Blog on 2026-08-21.

What to watch next

This update signals GitHub's ongoing attention to moderation tools, and users may expect further refinements in how accounts and content are managed.

Sources

• GitHub Changelog

What happened

GitHub has updated its Slack integration so that the agentic capabilities of GitHub Copilot CLI and the GitHub Copilot app are now available inside Slack.

The new experience is being offered in public preview.

Users can interact with the @GitHub handle in Slack as part of the feature, according to the GitHub Changelog post.

Why it matters

Bringing Copilot's agentic skills into Slack positions GitHub's AI assistant in a space where teams already communicate and coordinate work.

By offering a public preview, GitHub is likely exploring how developers will use these AI-driven workflows in conversational settings before expanding access more broadly.

Key facts

The GitHub integration in Slack now supports agentic capabilities from GitHub Copilot CLI and the GitHub Copilot app.

The new GitHub Copilot experience in Slack is available in public preview.

Users can work with @GitHub in Slack as part of this integration.

What to watch next

More details may emerge about the specific actions users can take with @GitHub in Slack, since the announcement appears to continue beyond its opening description.

The public preview may evolve as GitHub gathers feedback and potentially expands Copilot's Slack capabilities.

Sources

• GitHub Changelog

What happened

GitHub announced a new integration that brings shared agentic work with GitHub Copilot into Microsoft Teams.

Users can transform a Teams discussion into a collaborative agent session that everyone can see and help direct.

A session is started by mentioning @GitHub in a channel, thread, or direct message.

Why it matters

This shifts GitHub Copilot from a private assistant toward a team-oriented tool where group members can jointly guide the agent.

Making the session visible to all participants encourages shared context and collective oversight of agent actions.

Key facts

The feature is described as shared agentic work with GitHub Copilot in Microsoft Teams.

A Teams discussion can become a collaborative agent session available for everyone to see and direct.

Users initiate the session by mentioning @GitHub in a channel, thread, or direct message.

What to watch next

The announcement does not provide further details on what happens after the @GitHub mention or how the session is managed.

GitHub may release additional changelog entries explaining session permissions, limitations, or collaborative controls.

Sources

• GitHub Changelog

What happened

GitHub announced the general availability of pinning saved views to the repository issues sidebar.

This feature lets users place the views they use most frequently directly in the sidebar, so they are just one click away.

The announcement was made on the GitHub Blog as part of a changelog post that also hinted at additional updates.

Why it matters

Pinning saved views reduces navigation friction for developers who constantly switch between custom issue filters and layouts.

By putting frequently used views directly in the sidebar, teams can streamline their triage workflows and save time on repetitive clicks.

The general availability status signals that the feature is now considered stable for production use across repositories.

Key facts

Pinning saved views to the repository issues sidebar is now generally available.

The feature makes saved views one click away in the sidebar.

The announcement appeared on the GitHub Blog and included the phrase 'and more'.

What to watch next

The blog post's 'and more' suggests additional changes shipped alongside this feature, but details were not provided in the summary.

Users should watch for follow-up changelog entries or documentation updates describing other enhancements in the release.

Sources

• GitHub Changelog