GitHub Copilot Projects gives coding agents persistent goals across repositories
Copilot Projects can coordinate agents, files and recurring tasks across repositories or non-code work; review and permissions remain human responsibilities.
Search
Search results for “GitHub Copilot Projects”
Find published research by company, product, platform or technology.
Showing 1–20 of 174 dossiers
SaaSCloud & InfrastructureIndie BusinessBootstrappingHostingPricing & BillingDatabases & StorageActive dossier
Neon doubles free PostgreSQL storage to 1GB per project across 100 projects
Neon now includes 100 separate free Postgres projects with 1GB each, 100 compute-unit hours per project and branching. It is a meaningful per-project allowance increase, not an unrestricted production database tier.
Claude Code Projects turns one engineering goal into parallel cloud-agent branches
The important change is not simply that Claude can run several agents. Projects now owns decomposition, shared context, branch isolation and progress coordination across full Claude Code sessions, while the trade-offs become usage burn, cloud-only execution and ordinary merge conflicts when parallel work overlaps.
GitHub Copilot SDK gains organisation-owned server-to-server authentication for agents
GitHub Apps can now authenticate Copilot SDK workloads without a user's credentials. Organisation admins control installation permissions, usage attribution and budgets.
GitHub Enterprise now offers Copilot with no extra seat fee — but no included AI credits
GitHub Enterprise customers can trade Copilot seat fees for usage-only billing. The key catch: zero included credits, staged eligibility and voluntary migration.
GitHub Copilot Fusion goes GA with multi-model routing, effort tiers and experimental local inference
GitHub's multi-model coding orchestration is now GA, with admin-controlled model pools and per-model charges. Local routing remains experimental and cloud-dependent.
GitHub Copilot adds model-judged permissions to its GA agent sandbox — with unattended-run traps
Copilot now offers model-reviewed action approvals between manual and Allow All. Unlike OS sandboxing, this probabilistic gate can approve unsafe operations; unattended CLI flags may leave unexpectedly broad permissions.
GitHub Copilot can now operate desktop apps, not just code
The useful boundary change is that Copilot can now cross from code and terminals into ordinary desktop interfaces, with per-app approval and organisation-level controls.
GitHub rewrote Copilot’s 800,000-line agent runtime in Rust with agents doing most of the coding
The useful part is not the 800,000-line headline. GitHub has published unusually detailed receipts for a production-scale agent-assisted migration: roughly $120,000 of token spend, 14.5 weeks of incremental releases, dozens of regressions, extensive compatibility tests and a workload-specific jump from 7.55 to 120 session lifecycles per second.
GitHub Copilot Auto now lets developers choose whether routing optimizes for cost or intelligence
The material change is that model routing is no longer a single opaque optimization target. Developers can now tell Copilot whether to bias Auto toward lower cost, a middle ground or higher quality while GitHub still chooses a model prompt by prompt.
Artificial IntelligenceWeb DevelopmentCloud & InfrastructureAI CodingDeployment & DevOpsDeveloper ToolsActive dossier
GitHub Enterprise Server 3.22 brings Copilot CLI into disconnected and air-gapped environments
The technical-preview feature separates Copilot CLI from GitHub Cloud for core coding, shell and repository workflows, giving regulated and isolated environments a supported agent path while leaving cloud-dependent capabilities such as GitHub-hosted model selection and web search unavailable.
GitHub Copilot code review can now approve pull requests
Copilot code review now moves from advisory assessment toward a governed merge gate. The public preview remains off by default, and GitHub’s current docs let administrators separate AI approval itself from whether that approval counts toward required-review policy.
Artificial IntelligenceWeb DevelopmentSaaSPricing & BillingAI CodingSaaS OperationsDeveloper ToolsActive dossier
GitHub Copilot is moving enterprise seats to upfront billing and longer chat retention
From September and October, Copilot Business and Enterprise seat access becomes more tightly coupled to upfront payment. A separate September 28 policy migration enables a unified Copilot experience by default, retains github.com chat data for the life of the account and changes code review’s default effort from Lite to Balanced.
GitHub Copilot turns Slack and Teams conversations into shared coding-agent sessions
GitHub Copilot can now turn Slack or Teams threads into collaborative cloud-agent sessions. Teammates can add context and steer the work in public, while repository permissions, agent budgets and optional extra PR approvals remain the main control boundaries.
VS Code’s Agent Host can now run Dev Container sessions on remote SSH, Tunnel and WSL projects
The Agent Host’s environment boundary has moved from local Dev Containers to remote development hosts, making persistent coding-agent sessions more portable across real remote projects.
Google Cloud Storage now preserves soft-deleted buckets when projects are deleted
Cloud Storage project deletion no longer necessarily destroys every soft-deleted bucket immediately. Google’s August 17 change makes bucket retention part of project-recovery behavior, affecting disaster recovery, teardown assumptions and ongoing storage cost.
Dependabot’s private GitHub Packages access is back — now as fallback authentication
The corrected rollout matters for supply-chain configuration: teams can still remove PATs for qualifying GitHub Packages, but GitHub changed the precedence model after some npm update jobs were mistakenly routed through GitHub Packages.
GitHub says agents started over 40% of September pull requests — Octoverse reveals a review bottleneck
GitHub's 2026 platform data shows agent-started PRs rising sharply. The implications concern code review, security and multi-model workflows, not proof of higher software quality.
GitHub Agentic Workflows goes GA: Markdown agents compile into guarded Actions jobs
GitHub's gh-aw reaches GA, making Markdown-defined agent jobs a supported Actions workflow pattern. Security boundaries, model costs and privileged triggers still matter.
GitHub can now require authentication for public Git clones during traffic protection
GitHub's October 19 traffic protection can make previously reliable anonymous public-repo fetches fail; the change is selective, not a blanket private-repo requirement.