Coding-agent monitoring · GitHub Copilot CLI

    GitHub Copilot CLI monitoring for teams

    GitHub Copilot CLI monitoring means reading every Copilot session your team runs to find what keeps going wrong: the same failure again, instructions retyped by hand, custom instructions nobody follows, secrets in prompts. Hervé does it across the whole team, fixes the cause in your instruction files and skills, and checks the next sessions.

    Last updated

    Why one GitHub Copilot CLI session can't show you the problem

    GitHub Copilot CLI reads .github/copilot-instructions.md, the files in .github/instructions/, AGENTS.md and the skills in .github/skills/ to know how your team works. In its own docs: “GitHub Copilot can provide responses that are tailored to your personal preferences, the way your team works, the tools you use, or the specifics of your project, if you provide it with enough context to do so.”[1]

    Each developer only sees their own sessions. Nobody sees that three people hit the same wall last week, that the same instruction gets typed by hand every morning, or that a rule in copilot-instructions.md has not changed what the agent does in a month. 84% of developers use or plan to use AI tools in their development process, up from 76% a year earlier.[3] The more of the team runs GitHub Copilot CLI, the bigger that blind spot gets.

    What Hervé finds in GitHub Copilot CLI sessions

    Hervé reads every captured session across the team and groups what keeps going wrong into findings, each with how many sessions and developers it touched:

    • Recurring failures: the same mistake across sessions and developers, with the human time or tokens it cost.
    • Repeated instructions: guidance team members retype by hand that belongs in one shared rule or skill.
    • Unused instructions: sections of copilot-instructions.md and skills that no session follows or uses, but that still take up context.
    • Leaks: a secret pasted into a prompt, or printed by the agent. GitGuardian found a 6.4% secret-leak rate in public repositories using Copilot, 40% higher than the 4.6% average across public repositories.[2]

    How Hervé fixes the cause at the source

    For each finding, Hervé proposes the fix where GitHub Copilot CLI will read it next time: a change to .github/copilot-instructions.md, the files in .github/instructions/, AGENTS.md and the skills in .github/skills/. The fix is opened as a pull request on your repository, so it goes through your usual merge flow and reaches the whole team, not one developer's private memory.

    How Hervé guards the next GitHub Copilot CLI sessions

    Once a fix is merged, Hervé checks every new session against your rules and compares the before and after, so you see whether the problem stopped. You get a weekly update, and you stay in control of what the agents are told.

    How to set up GitHub Copilot CLI monitoring

    1. Install the rv CLI. Follow the one-minute setup for macOS, Linux or Windows.
    2. Enable capture for GitHub Copilot CLI. In each repository, run:
      my_repo $ rv install --agent copilot-cli

      Sessions are saved to a branch of your own repository, and the last 30 days of local sessions are backfilled by default.

    3. Have every team member do the same once. Hervé only sees the sessions it captures, so each developer runs rv install once. The first findings come in week 2.

    Common questions

    What does Hervé read in a GitHub Copilot CLI session?

    The prompts, the steps the agent took and the files it touched, from the branch rv install writes to your own repository. Hervé reads sessions and code on demand: transcripts, diffs and file contents never go into our database. We keep findings, counts and file names.

    Can't I just ask GitHub Copilot CLI to clean up copilot-instructions.md?

    You can, for one session. GitHub Copilot CLI sees what happened in front of it; it can't see that three developers hit the same wall last week, or which rules no session has followed in a month. Hervé reads every session across the team, then checks whether the fix held.

    Which files does Hervé change to fix a GitHub Copilot CLI problem?

    The ones GitHub Copilot CLI reads its instructions from: .github/copilot-instructions.md, .github/instructions/, AGENTS.md and .github/skills/. Each fix is opened as a pull request on your repository, so it goes through your usual merge flow and reaches the whole team.

    Do we have to change how we use GitHub Copilot CLI?

    No. Each team member runs rv install once. Everyone keeps using GitHub Copilot CLI, GitHub or GitLab, and your merge flow exactly as they are.

    What if the team uses more than one coding agent?

    Hervé captures sessions from Claude Code, Cursor, GitHub Copilot CLI, OpenAI Codex, and OpenCode, so a team that mixes agents is covered by the same install.

    How do we start?

    With a 6-week paid pilot for your whole team, fully refunded if we find nothing actionable. Talk to a founder to set it up; the pilot details and price are on the pricing page.

    See pilot details & pricing →

    Sources

    1. Adding custom instructions for GitHub Copilot CLI, GitHub.
    2. The State of Secrets Sprawl 2025, GitGuardian.
    3. 2025 Developer Survey: AI, Stack Overflow.

    Monitoring other coding agents

    See what your team's GitHub Copilot CLI sessions are hiding.

    Talk to a founder

    6-week paid pilot, fully refunded if we find nothing actionable.