All pages
  1. Getting started
  2. Connect machines
  3. Folders: what the building sees
  4. Views
  5. Chatting with sessions
  6. Approvals and notifications
  7. Everyday tools
  8. Agent teams
  9. Code and Git
  10. Preview on your phone
  11. On your phone
  12. Plan usage
  13. Codex
  14. Antigravity
  15. GitHub Copilot
  16. Buildings, people and roles
  17. Command
  18. Enterprise: policy, SSO and reports
  19. Your account
  20. Subscription
  21. Keyboard shortcuts
  22. Troubleshooting
Docs

GitHub Copilot

GitHub Copilot CLI (copilot) is GitHub’s terminal agent, which runs on your Copilot subscription. If the machine has copilot installed, its sessions show up in the dashboard next to Claude Code, Codex and Antigravity, with the Copilot badge. Fleetly reads the conversations Copilot saves in ~/.copilot/session-state and never reads its sign-in.

Install and sign in

npm install -g @github/copilot

To sign in, run copilot once and use /login. If the machine already has gh signed in (gh auth login), Copilot uses that, with nothing else to do. The copilot that ships inside VS Code only offers to install the CLI: install it with the command above.

What you can do

  • See the sessions, their state (working, your turn, open in a terminal or in VS Code), the conversation, the commands and the edits. Copilot chats in VS Code show up too: the new VS Code saves them in the same place as Copilot CLI.
  • Send a message to a Copilot session. Each message resumes the conversation on the same machine, and the reply shows up live. In a conversation open in the VS Code chat (experimental), the message lands there, as if you typed it (In VS Code, as yours · experimental), and its permission requests also reach the dashboard and your phone; the first answer wins. It uses an internal VS Code channel (1.143 or newer) that may change in an update: then the dashboard stops sending until Fleetly is updated, and the conversation keeps showing up.
  • Start a new session: in +, pick Copilot and, if you like, the model. With none picked, Copilot Auto chooses among your plan’s models. A model your plan doesn’t include gives a clear error.
  • Use the queue: the message is delivered when the session finishes what it’s doing.
  • Approve from the dashboard and your phone, as with Claude: in sessions Fleetly starts, each command and each edit becomes a request, and Accept automatically approves everything while it’s on. The building policy applies too. See Approvals.
  • Hand a conversation off from one agent to another: in the message box’s +, Hand off to Copilot (or, in a Copilot session, to another agent). For Copilot, the machine’s Claude Code or Codex writes the summary.

Roles and teams

In Edit roles, pick Copilot as the role’s agent, or put Copilot on a team seat, under Agent. A team can mix all four agents. See Agent teams.

In the roleIn Copilot
PromptBecomes a Copilot custom agent, for this role only.
SkillsEach becomes a SKILL.md for this role only.
ModelOne from Copilot’s list, or Auto.
Off limitsTruly refused by Fleetly, action by action: editing files, running commands or git push.

The team runs its sessions in Auto mode: commands that change something ask for approval in the dashboard and on your phone. So the team doesn’t stop and wait, turn on Accept automatically or forbid commands in the role.

Permission modes

In sessions Fleetly drives:

In the dashboardIn Copilot
Ask for approvalEach command and each edit asks for approval in the dashboard and on your phone. Reads go straight through.
Can edit filesEdits without asking; commands still ask for approval.
AutoEdits without asking and runs read-only commands right away (git status, git diff, ls, cat, grep), also chained with &&. Other commands ask for approval, as does anything with ;, |, > or $.
Plan onlyReads and proposes the plan: Fleetly refuses edits and any command that isn’t a read.

With no answer in 15 minutes, the request is denied. Fleetly never pre-approves everything in Copilot, and it changes nothing in sessions you open in a terminal: approvals apply only to the ones the dashboard drives.

What isn’t possible yet

  • Messaging a session open in a terminal (interactive copilot): the dashboard refuses, because Copilot would mix both conversations into the same file. Reply in the terminal, or close copilot there and continue from the dashboard. In the VS Code chat, the message goes in through VS Code itself (on a VS Code version Fleetly doesn’t know yet, the dashboard doesn’t send).
  • Approving terminal sessions from the dashboard: their requests stay in the terminal, and the building policy doesn’t apply to them.
  • Older VS Code chats, from before it saved them alongside Copilot CLI, don’t show up.

The estimated cost uses each model’s API price (GPT, Claude, Gemini). On a Copilot subscription, what counts is your plan’s premium requests, which Copilot shows.

Didn’t find what you were looking for? Write to admin@fleetly.tools.