Agents

copilot

Run multiple Copilot CLI sessions at once.

Copilot CLI can already keep several sessions running. Here are its own commands for starting, switching and splitting them, and how Starkomand puts every session in view at once, each in its own terminal, signed in as you.

v1.0.8 · Mac and Windows · 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.

Four ways to run several sessions.

Three are built into Copilot CLI. The fourth puts every session in view at once.

  1. Several sessions in one CLI

    Start a named session with copilot --name "checkout refactor", add more with /new, and switch from the sidebar (← on an empty prompt) or the Sessions tab (/session). A session you switch away from keeps running, with its own working directory, approvals and mode.

  2. Pick a session back up

    copilot --continue reopens your most recent session, copilot --resume lets you choose one and copilot --resume="checkout refactor" opens it by name. Inside the CLI, /resume opens the same picker and /rename names the session you are in. Quitting the CLI stops its local sessions.

  3. Split one task with /fleet

    /fleet followed by your goal lets Copilot break the task into parts and run them as parallel subagents inside your session; /tasks shows what is running. The subagents share one folder with no file locking, so give each its own files.

  4. See every session side by side

    In Starkomand each Copilot session is its own real terminal window on one Mac canvas, so you watch them all work instead of switching between them. Each starts signed in as you, and the next window can be Claude Code or Codex.

To run it on GitHub instead. /delegate, or a prompt that starts with &, hands the work to Copilot cloud agent, and its sessions show up in the Sessions tab.

Commands from GitHub’s guide to multiple sessions and its /fleet post, read on 25 October 2026.

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, GitHub 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.

How Starkomand compares with other ADEs.

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.

What is the difference between /fleet and several sessions?

/fleet splits one task across subagents inside a single session; they share its folder and the session coordinates them. Separate sessions are separate conversations, each with its own working directory, approvals and mode, so they suit unrelated jobs.

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.8 · Mac and Windows · no account