Agriware Agent Hub
Keep every team member's GitHub Copilot setup in sync — instructions, prompts, custom agents and MCP servers — pulled straight from Azure DevOps.
What it does
Agriware Agent Hub distributes shared GitHub Copilot configuration to your whole team. Instead of everyone hand-copying instruction files, prompt files, custom agents and MCP server definitions, you maintain them in an Azure DevOps repository and let the extension deliver them to each developer's machine.
Pick a profile (each profile maps to an Azure DevOps repository), and the extension:
- Authenticates with Azure DevOps using your corporate Microsoft account (with a Personal Access Token fallback).
- Downloads the repository contents over the Azure DevOps REST API — no
git required.
- Places the files in a managed local directory and registers them with GitHub Copilot.
- Keeps everything current — re-sync any time to pull the latest version.
Because it uses VS Code's built-in Microsoft authentication and read-only access, only people in your organization who can already reach the repository can pull a profile.
Features
- One-click profile sync — select a team profile and everything is downloaded and wired up for you.
- Corporate SSO — signs in with VS Code's built-in Microsoft authentication; falls back to an Azure DevOps Personal Access Token (Code · Read) when needed.
- Automatic Copilot registration — synced folders are registered with GitHub Copilot's prompt and agent file locations, and MCP server definitions are merged in automatically.
- Safe conflict handling — if you've made local changes, the extension offers to back up your existing files (timestamped) before pulling fresh ones, so nothing is lost.
- Activity Bar dashboard — a dedicated side panel shows the active profile, the local download path and a one-click Sync button.
- No git needed — downloads happen through the Azure DevOps REST API, so it works behind firewalls and on machines without git.
- Configurable — choose what to sync, where files land, and how profile switching behaves.
Getting started
- Install the extension.
- On first launch you'll be prompted to select a profile. Choose the one for your team.
- Sign in with your Microsoft account when prompted (or provide a Personal Access Token).
- The profile is downloaded and registered with GitHub Copilot automatically. That's it.
You can re-open the profile picker or trigger a sync at any time from the Agent Hub icon in the Activity Bar, or from the Command Palette.
Commands
Open the Command Palette (Ctrl+Shift+P) and type Agent Hub:
| Command |
Description |
| Agent Hub: Select Profile |
Choose or switch the active team profile. |
| Agent Hub: Sync Current Profile |
Re-download the active profile and refresh Copilot. |
| Agent Hub: Sign In |
Authenticate with Azure DevOps. |
| Agent Hub: Sign Out |
Clear your saved credentials. |
| Agent Hub: Manage Profiles |
Open the dashboard panel. |
Settings
| Setting |
Default |
Description |
agentHub.activeProfile |
"" |
ID of the currently active profile. |
agentHub.authMethod |
microsoft |
Authentication method: microsoft or pat. |
agentHub.customAgentsPath |
~/.github/global |
Local directory where profiles are downloaded. |
agentHub.mcpConfigPath |
"" |
Path to the global VS Code mcp.json. Leave blank to auto-detect. |
agentHub.removeOtherProfilesOnSwitch |
true |
Remove other downloaded profiles when switching to a new one. |
agentHub.sync |
(see below) |
Which configuration types to sync. |
The agentHub.sync object controls which Copilot config types are included:
"agentHub.sync": {
"instructions": true, // copilot-instructions.md
"prompts": true, // *.prompt.md files
"agents": false, // custom agent files
"mcpServers": false // MCP server definitions
}
How profiles work
Each profile points at an Azure DevOps repository:
- Organization — your Azure DevOps organization.
- Project — the project the repo lives in.
- Repository — the repo holding the shared Copilot configuration.
- Branch — the branch to pull from (usually
main).
Profiles are defined in the extension so administrators can curate exactly which teams appear. To add or change a profile, edit the profile list and publish a new version. The Azure DevOps repository simply needs to contain the Copilot configuration files (a .github folder is detected automatically).
Requirements
- Visual Studio Code 1.85.0 or newer.
- Access to the Azure DevOps organization and repository behind your profile.
- GitHub Copilot installed, to make use of the synced instructions, prompts and agents.
Privacy & security
- Access is read-only — the extension never writes back to Azure DevOps.
- Credentials are handled by VS Code's built-in Microsoft authentication, or stored in the OS credential store (Windows Credential Manager / macOS Keychain) when using a Personal Access Token.
- The extension only writes to your managed download directory and to GitHub Copilot's own configuration locations.
Author & support
Built by Arthur Vos for Mprise Agriware.
Found a bug or have a feature request? Please report it to Arthur Vos
© Mprise Agriware — Agriware Agent Hub
