GitHub's Agent HQ centralizes autonomous AI agents in repos & VS Code, boosting development with secure sandboxes, LLM tasks, and marketplace integrations.

Moving from basic code completion to fully autonomous AI agents requires solid infrastructure. GitHub is addressing this with Agent HQ, a centralized hub that brings software development agents directly into the repository and VS Code. This setup cuts out the constant context-switching of juggling different development tools. These agents use large language models to break down instructions, tackle complex repository tasks, and work without needing constant human supervision.
To keep code changes safe, Agent HQ runs tasks inside temporary sandboxes. Powered by GitHub Actions, these isolated environments last only as long as the task itself, giving agents a secure space to run tests, read files, and write code on separate branches. Running these agents does use up system resources, which are tracked through AI credits and GitHub Actions runtime. Billing is based on the specific LLM architecture used and the volume of data processed.
---
target: github-copilot
---
Developers can customize how an agent behaves by dropping configuration files with a .agent.md suffix into the .github/agents/ directory. If you have older configurations using the .chatmode.md format, an automated utility in the editor can quickly migrate them.
This specific metadata configuration tells the runtime engine to execute the agent within a cloud database context instead of the local code editor.
This configuration layer also supports handoffs, meaning one agent can pass its current state and completed work to another specialized downstream agent. Once an agent outputs code, GitHub automatically runs scans to check for security bugs, exposed secrets, and vulnerable dependencies, all without needing a separate security license.
To standardize how agents talk to external tools, the platform uses the Model Context Protocol (MCP). This open standard lets agents connect directly to external databases and environments. For example, a Playwright server running over MCP can spin up a web app, click through UI elements, and take screenshots to check for visual bugs. Developers can also enforce project-wide coding standards by writing rules in a .github/copilot-instructions.md file.
GitHub also connects with Marketplace integrations, bringing partner tools like Amplitude, Endor Labs, LaunchDarkly, and PagerDuty directly into pull requests. You can trigger these integrations simply by typing specific commands in PR comments.
@amplitude Compare the retention rate of users who invite teammates during sign-up versus those who do not.
This prompt targets the right service namespace, defines the core metric, and sets up the comparison parameters so the LLM can map the request to the correct database schema.
@endor-labs Check the new dependencies in this pull request for security vulnerabilities.
This phrasing limits the security scan to newly added libraries, preventing unnecessary token usage and avoiding redundant file scans.
@launchdarkly Create a new feature flag named "optional-onboarding" and set it to target solo sign-ups.
By providing the exact name of the flag and its targeting rules, the agent can write the implementation code and commit it directly to the repository.
@pagerduty Check if this service is in a safe state for a deployment.
This command kicks off a thorough check. The integration connects the repository to its active service, reviews current incidents, looks back at the past 90 days of system history, and checks if the edited files overlap with past problem areas.
For local workflows, the October 2025 update of Visual Studio Code (version 1.106) introduces an Agent Sessions view, which splits active agent tasks into local and cloud categories. The release also brings in a Plan Agent, which maps out step-by-step strategies before modifying any code, and a /delegate CLI command to push local terminal tasks to the cloud. Down the road, developers will also be able to use the GitHub Code Quality preview tool to monitor and audit these agent sessions.
Google took Gemini to three state fairs. Reading everything else it published about Gemini that week turned out to be the more interesting story.
AI models from OpenAI & Anthropic escaped test environments, hacking real-world systems. This exposes dangerous AI safety limits & urgent need for stronger tech security.
Responsible AI requires more than rules: clear governance, data protection and human accountability are essential to building trust in both universities and the workplace.