Chief + Copilot: Better Together

At a glance

What is Chief?

Chief is an AI-native agent manager. It sits above coding agents like Claude Code and Codex and handles everything between "here's what I want" and "here's the shipped result" — planning what to build, figuring out what comes next, dispatching agents across your portfolio, and reviewing output before it ships.

Copilot meets you where you already work: completions as you type, chat in the editor, an agent you can assign a GitHub issue to, and a reviewer on your pull requests. Chief covers what sits above that — deciding what the next five issues should be, running them across every repo you own, and checking the results.

Chief uses a BYOA (bring-your-own-agent) model. You connect the coding agents you already pay for — Claude Code, Codex, Qwen Code, OpenCode, or Kimi Code — and Chief dispatches them. Your Copilot setup stays exactly as it is.

How Chief and Copilot fit together

1. Copilot assists the work you do; Chief manages the work you delegate

Copilot is at its best when you're in the loop: completing the function you're writing, answering a question about this file, or taking a well-scoped issue and turning it into a pull request.

Chief is for the work above that. Give it a goal and it plans the milestones, dispatches a coding agent for each one, and reviews the result against acceptance criteria. You keep Copilot for the hands-on moments; Chief keeps the delegated backlog moving.

2. Plan complex goals once, execute in one shot

Copilot's coding agent works one issue at a time. For a large feature, you still write the issues, decide the order, and notice when a dependency was missed.

Chief provides structured one-shot execution. Give it "implement Stripe billing with usage metering and team plans" and Chief decomposes it into dependency-aware milestones — the schema migration before the API endpoints, the webhook handler before the billing page. Each milestone has acceptance criteria and a review gate. You approve the plan once; Chief executes the entire sequence with checkpoints you can inspect.

3. Proactive management instead of a queue of issues

Copilot waits for an assignment. Between issues, nothing happens until someone writes the next one.

Chief is proactive. It analyzes project state, understands what's been completed, what's blocked, and what's ready to start — then proposes the next milestones. When morning milestones ship, Chief has already figured out the afternoon's priorities. You make decisions; Chief drives the pace.

4. Scale across every repository

Copilot's coding agent operates per repository. Five repos means five independent queues with no shared awareness of what's in flight.

Chief manages agents across all your projects simultaneously. Dispatch Claude Code to three repos and Codex to two more, and see all progress in one dashboard. Chief tracks what's in flight everywhere and sequences cross-project dependencies. Your output multiplies with each project you add — without multiplying your management overhead.

5. Mix the right agent for each task

Copilot lets you pick among several models, but the work still runs through Copilot's own agent.

Chief's BYOA model lets you mix coding agents per task. Use Codex where it shines and Claude Code where Opus excels, or bring Qwen Code, OpenCode, or Kimi Code for the jobs they fit best. Chief manages all of them from a single interface, routing the right agent to the right milestone.

6. Quality gates at two stages

Copilot code review comments on pull requests once they exist. Chief reviews earlier: every milestone is checked against its acceptance criteria before the result is surfaced to you. Copilot's review still runs on the pull request afterward. Two layers of review, at two different stages, with you handling only the decisions that need human judgment.

When to add Chief

Add Chief to your Copilot workflow when:

• You want to scale across repositories. Chief lets you manage agents across your entire portfolio from one dashboard — not one issue queue per repo.
• You want one-shot execution of complex goals. Give Chief a goal, approve the plan, and it executes the full milestone sequence with checkpoints and review gates.
• You want proactive management. Chief figures out what to work on next based on project state — you stop being the one writing every issue.
• You want to mix agents. Route Claude Code, Codex, and other agents to the milestones each handles best, managed from a single interface.
• You're on a team. Unified visibility shows what every agent is doing across every project.
• You want quality gates at scale. Chief reviews agent output against acceptance criteria before it hits your inbox.

Chief doesn't replace Copilot — it adds the planning and portfolio layer that an in-editor assistant was never meant to be.

Getting started in 5 minutes

Already using Copilot? Adding Chief takes minutes, and nothing about your editor or GitHub setup changes.

1. Sign up for Chief — free trial, no credit card.
2. Connect your coding agents — Claude Code, Codex, Qwen Code, OpenCode, or Kimi Code via BYOA. No additional agent costs.
3. Import a project — give Chief a GitHub repo URL. It builds project context automatically.
4. Set a goal — describe what you want accomplished in plain language.
5. Approve the plan — Chief proposes milestones with acceptance criteria. Review and approve.
6. Watch it execute — Chief dispatches agents with the right context, runs the full plan, and reviews the output. Copilot code review still runs on the pull requests you open.

Your Copilot workflow stays the same — it just gains a manager above it.

FAQ

Is Chief a replacement for GitHub Copilot?

No. Copilot assists you in the editor and on GitHub; Chief manages coding agents across your portfolio. They're different layers — one helps you write, the other decides what gets built next and runs the agents that build it.

Does Chief dispatch Copilot's coding agent?

Not today. Chief dispatches Claude Code, Codex, Qwen Code, OpenCode, and Kimi Code through its BYOA model. Copilot's coding agent stays yours to assign from GitHub.

Do I need Copilot to use Chief?

No. Chief is editor-agnostic and dispatches coding agents in the background. If you already have Copilot, keep it; if you don't, Chief works on its own.

How is Chief different from assigning issues to Copilot?

Assigning an issue to Copilot runs one well-scoped task and opens a pull request. Chief plans the issues in the first place — decomposing a goal into dependency-aware milestones — then dispatches, sequences, and reviews them across every repo you own.

Can I keep using Copilot code review?

Yes. Copilot reviews pull requests; Chief reviews each milestone against its acceptance criteria before the work reaches you. They operate at different stages and don't interfere with each other.

How does Chief decide what to work on next?

Chief maintains persistent project context — completed milestones, in-flight work, project goals, codebase state. It uses this context to proactively propose the next milestones. You approve or redirect; Chief drives the pace.

Does Chief need access to my GitHub organization?

Chief imports projects from GitHub repo URLs and dispatches agents that run on your own machine. Your Copilot seats, organization policies, and repository permissions are unaffected.