Skip to main content
GitHub Copilot comes with Mains. Sign in during onboarding or open Settings → Copilot to inspect the account and bundled runtime. You need a GitHub account with access to Copilot. Signing into Mains’s GitHub issue connection or the gh CLI does not sign into Copilot.

​
Runtime and models

The bundled runtime requires no separate CLI installation. Bundled updates arrive with the app; Settings reports which runtime is in use. Choose an available model and supported effort or fast options in the composer. Each conversation retains its own settings. Copilot currently supports Code in Mains.

​
Approvals

Permission requests appear in the conversation. Mains also handles Copilot questions and plan-exit requests where the runtime provides them. Use the composer’s supported permission choices for that conversation. Package additions can be checked through the dependency guard before shell execution.

​
Skills and agents

Settings links to agent definitions and skills. Copilot’s configured skill directories include:
  • ~/.claude/skills/, shared with Claude.
  • ~/.copilot/skills/ for user skills.
  • .github/skills/ in the working directory for project skills.
Skills use folders containing SKILL.md. Copilot does not currently expose Mains’s skill picker or plugin marketplace. Runtime discovery can still load the configured skills.

​
Continue a conversation

Copilot supports continued sessions. It does not expose the fork action in Mains. Agent shell output and delegated tool activity appear in the transcript. The manual terminal remains a separate shell session.