---
type: "post"
id: "github-copilot-cli-1-0-105-lets-users-77ef51"
slug: "github-copilot-cli-1-0-105-lets-users-77ef51"
title: "GitHub Copilot CLI 1.0.105 lets users pick Copilot Fusion High or Max from long-context sessions; Copilot SDK 1.0.28 follows"
description: "GitHub Copilot CLI 1.0.105 restores the ability to select Copilot Fusion High or Copilot Fusion Max with `/model` during long-context sessions."
retrieval_nugget: "GitHub Copilot CLI 1.0.105 restores the ability to select Copilot Fusion High or Copilot Fusion Max with /model during long-context sessions. The change is small, but it removes a workflow interruption for developers running extended terminal-agent tasks and is followed by a matching Copilot SDK snapshot update."
published_at: "2026-10-28"
updated_at: "2026-10-28"
record_date: "2026-10-28"
date_kind: "published_at"
topics: ["github"]
entities: ["GitHub","GitHub Copilot CLI","GitHub Copilot SDK","Copilot Fusion High","Copilot Fusion Max"]
related_patterns: ["harness-architecture-outlives-model-choice"]
novelty_label: "new_fact"
what_changed: "Copilot CLI 1.0.105 adds selection of Copilot Fusion High or Max from long-context sessions, with SDK 1.0.28 also released; the priors cover other model and CLI updates."
prior_refs: ["memory:f13855bc-ea29-8b4e-a10a-74c76d9cad28","memory:5e6b3d0d-e929-86f7-ab4c-ceac19d546a3"]
source_url: "https://github.com/github/copilot-cli/releases/tag/v1.0.105"
source_urls: ["https://github.com/github/copilot-cli/releases/tag/v1.0.105"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:github-copilot-cli-1-0-105-lets-users-77ef51"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/github-copilot-cli-1-0-105-lets-users-77ef51/","markdown":"https://newruntime.com/posts/github-copilot-cli-1-0-105-lets-users-77ef51.md","json":"https://newruntime.com/posts/github-copilot-cli-1-0-105-lets-users-77ef51.json"}
---

# GitHub Copilot CLI 1.0.105 lets users pick Copilot Fusion High or Max from long-context sessions; Copilot SDK 1.0.28 follows

## Retrieval answer

GitHub Copilot CLI 1.0.105 restores the ability to select Copilot Fusion High or Copilot Fusion Max with /model during long-context sessions. The change is small, but it removes a workflow interruption for developers running extended terminal-agent tasks and is followed by a matching Copilot SDK snapshot update.

## Summary

GitHub Copilot CLI 1.0.105 restores the ability to select Copilot Fusion High or Copilot Fusion Max with `/model` during long-context sessions. The change is small, but it removes a workflow interruption for developers running extended terminal-agent tasks and is followed by a matching Copilot SDK snapshot update.

## What happened

GitHub published version 1.0.105 of the `github/copilot-cli` project. The release page identifies 1.0.105 as the latest release, associates it with commit `8f18bec`, and shows the version dated October 27, 2026; the page also records publication at 00:44 on October 28. Its release notes contain one listed change: selecting Copilot Fusion High or Copilot Fusion Max through the `/model` command now works from long-context sessions.

The important detail is the scope of the fix. It concerns model-tier selection inside an already long-running session, rather than the introduction of a new model, a new agent mode, or a change to the CLI command surface. A developer using Copilot CLI can invoke `/model` to choose a model configuration. With 1.0.105, the release says that choosing the Fusion High and Fusion Max options works even after the session has accumulated long context.

That makes the release an interaction fix for a specific point in an agentic terminal workflow. Long-context sessions are where prior conversation, task state, and repository work have built up. If a user wanted one of those higher Fusion tiers after reaching that state, the release note indicates that the selection path had not worked. Version 1.0.105 removes that stated limitation. The source does not describe the prior failure mode in more detail, nor does it say whether any other model options were affected.

A Copilot SDK release followed shortly after the CLI release. Version 1.0.28 updates the SDK snapshot to Copilot CLI 1.0.105-1, keeping the SDK’s bundled or referenced CLI state aligned with the new CLI build. For a team using the SDK to embed the Copilot agent in another application, that alignment is the relevant follow-on: the CLI behavior and SDK snapshot move together. The supplied material gives no new SDK API, feature, pricing, access condition, benchmark, or performance claim.

The release also does not announce general availability for a product, alter Copilot subscription terms, or provide a migration procedure. Its practical instruction is simply implied by the fixed path: users who need to change to Fusion High or Max in a long-context Copilot CLI session can update to 1.0.105 and use `/model` there.

## What the archive adds

This is a new fact on a known Copilot CLI story. [Discover local models in GitHub Copilot CLI](https://newruntime.com/posts/discover-local-models-in-github-copilot-cli-1b8ee0/) covered version 1.0.94-0 discovering supported models from a running local Ollama instance. [HydraFusion updates and new Max option](https://newruntime.com/posts/hydrafusion-updates-and-new-max-option-ffb3d8/) documented the earlier introduction of a Max option across Copilot surfaces; 1.0.105 concerns selecting the High and Max tiers after context becomes long.

## Trend signal

This modest release supports [Harness architecture outlives model choice](https://newruntime.com/patterns/harness-architecture-outlives-model-choice/). The useful change is not a claimed leap in model capability: it is the CLI harness preserving a model-selection control at a difficult point in the session lifecycle. The evidence is narrow, so it does not establish a broader architectural direction by itself.

## Connections to other events

The earlier local-model discovery release shows GitHub expanding the range of model choices visible in Copilot CLI. The earlier HydraFusion note shows High and Max becoming available across Copilot surfaces. This release connects those threads only at the workflow layer: it makes two existing tier choices available through `/model` when the session has long context.

## Why it matters

For builders, the value is continuity. Long-running coding-agent sessions are often where a team has accumulated the most task-specific context, so restarting merely to alter a model tier can be disruptive and can change the quality or cost trade-off of the work. This fix allows that decision to happen in the existing CLI session rather than forcing a context reset.

Teams embedding Copilot through the SDK have a second operational consideration: SDK 1.0.28 tracks the updated CLI snapshot. That does not prove an application will behave differently without testing, but it gives maintainers a clear version pair to evaluate. The release is most relevant to organizations that already use Copilot CLI for sustained agent work, rather than to teams deciding whether to adopt Copilot for the first time.

## What happens next

- **GitHub will continue shipping targeted CLI fixes that preserve controls during longer agent sessions.** (3 months, 65%). Watch for: release notes naming session-state, context, or `/model` behavior.
- **SDK releases will continue to track CLI snapshot updates closely.** (3 months, 70%). Watch for: SDK notes that explicitly reference a newer Copilot CLI build.

## Limits and uncertainty

The public release note is concise. It does not define “long-context,” specify a context threshold, explain why Fusion High and Max selection previously failed, or provide before-and-after tests. It also does not state availability requirements, subscription eligibility, pricing, regional coverage, model behavior, latency, or quality differences between the tiers. The SDK update is described as snapshot alignment; the supplied material does not establish a new SDK interface or an application-level behavior change. Teams should therefore treat this as a focused compatibility and workflow fix, not as evidence of broader Copilot capability changes.

## Skill to build now

Add a short session-transition check to the team’s Copilot CLI runbook this week. In a representative long-context task, verify that `/model` can switch to the permitted Fusion High or Max tier without restarting the session, then record the installed CLI version and the expected SDK version for embedded uses. This is a concrete compatibility check, not a performance evaluation: the release provides no quality or cost measurements to optimize against.

## Reader takeaway

Copilot CLI 1.0.105 fixes one specific friction point: Fusion High and Max can be selected with `/model` from long-context sessions. If your workflow depends on extended terminal-agent runs, update and test that path; if you embed Copilot through the SDK, assess the accompanying 1.0.28 snapshot update as part of the same version change.

## Open question

How long must a session be before the previously affected behavior appears, and do account tier or environment change which Fusion options are available? The release note does not say.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Github](https://newruntime.com/topics/github.md): Explore the github topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)