Agents

copilot

Run GitHub Copilot CLI on a canvas.

Run the Copilot agent in the terminal, several sessions at once, on one canvas with your other agents. Your GitHub sign-in, your Copilot plan, its usage in the rail.

v1.0.4 · Apple silicon · free for 3 days · no account

The Starkomand canvas with several agent windows, a hand-drawn diagram beside one of them and a browser preview beside another.

What GitHub Copilot CLI gets on the canvas.

How Starkomand launches GitHub Copilot CLI and what it can show you about each window.

Launches as copilot
Canvas tools Added with --additional-mcp-configFor that session only, through Starkomand’s stdio bridge.
Canvas instructions COPILOT_CUSTOM_INSTRUCTIONS_DIRS
Window’s back Request and turn state onlyThe CLI does not report tool steps to Starkomand.
Usage Usage ring in the railShown when your plan is metered; opt in under Settings → Usage meters.
Expired sign-in Restart other windows with ⟳ after signing in

Same for every agent. A real terminal signed in as you, diagrams and browser previews beside the window, issue notes you drop onto it, handoffs with a brief to any other agent, a spoken “done” when a turn ends, and persistent windows through Herdr.

Read from Starkomand’s launch code on 28 September 2026. Product names belong to their owners; Starkomand is not affiliated with them. Spotted a change? Tell us.

Set up in a minute.

  1. Install GitHub Copilot CLI

    Follow the Copilot CLI setup. Starkomand finds copilot on your PATH.

  2. Sign in once

    Run copilot and use /login, or run copilot login.

  3. Open it on the canvas

    ⌘-click the canvas and pick GitHub Copilot CLI. Every window you open after that starts signed in.

Worth knowing.

  • Copilot does not expand variables in an MCP URL, so its canvas tools go through the local starkomand-canvas bridge.

Questions.

Can I run multiple GitHub Copilot CLI sessions at once?

Yes. Each window runs its own copilot in a real terminal, so open as many as your plan allows, side by side or in separate workspaces, next to any other agent.

Does Starkomand change my GitHub Copilot CLI configuration?

No. The canvas server is added for that session with a flag and the instructions folder rides in the environment.

Do I need an API key for GitHub Copilot CLI?

Starkomand never asks for one. Run copilot and use /login, or run copilot login. Your plan and usage stay with the provider; Starkomand does not resell tokens.

Bring the agents you already pay for.

Every agent, every feature, free for 3 days. Your CLIs are already installed; the canvas takes a minute.

v1.0.4 · Apple silicon · no account