Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

AHP 0.7: native resume uses a derived /chat URI instead of advertised defaultChat

Fechada
  • Algo errado?
#4,877 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
shell
Domínio
api, cli

Direção de pesquisa

Comece pelo caminho nativo de retomada/anexação e compare o recurso solicitado com SessionState.defaultChat. Use a definição AHP de SessionState e as referências buildChatUri/buildDefaultChatUri do VS Code para reproduzir uma URI anunciada que seja diferente de /chat. Está concluído quando um caso de regressão verificar que a retomada solicita o recurso anunciado e não mantém um endereço derivado obsoleto.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

triage

Summary

The experimental native AHP client can discover an existing session on the VS Code agent host, but resume fails at the chat resource. The failed resource has the form <sessionUri>/chat, which differs from the defaultChat advertised in that session's state.

The intended workflow is for unmodified Copilot CLI and unmodified VS Code to access one server-backed session.

Observed versions

  • Official Copilot CLI 1.0.85 stable.
  • Official standalone Copilot CLI 1.0.86-0 prerelease, not an updated payload selected by an older launcher.
  • Official VS Code Server 1.132.0, commit df53daabb18cd157bdb08c7f01c34df936cf12f4.
  • Stock VS Code 1.137.0 connects and authenticates to the same agent host. This observation alone is not a claim of complete two-client conversation compatibility.
  • The tested CLI and host negotiate AHP 0.7.0.
  • CLI AHP mode is enabled with COPILOT_CLI_ENABLED_FEATURE_FLAGS=AHP_CLIENT.

Reproduction

  1. Start the official server's native, token-authenticated agent-host listener on loopback, using the normal server entrypoint.

  2. Create a Copilot session through AHP with an explicit provider and a provider-specific session URI.

  3. Materialize the session using the host-advertised native /env diagnostic command. Confirm its completed command turn and that listSessions returns the session.

  4. Subscribe to that session and note its actual defaultChat field.

  5. Supply the authenticated endpoint privately through COPILOT_AHP_URL, then run the stock CLI in a real interactive terminal:

    copilot --no-auto-update --ahp= --resume <session-uri>

  6. Resume finds the session, but attachment fails with JSON-RPC error -32001, identifying a resource ending in /chat.

No model prompt is necessary to reach this failure. An unmaterialized provisional session is not sufficient for this reproduction: it is absent from the catalogue and causes a different, earlier not-found result.

Resource identity

The identifiers below are synthetic and normalized, not captured logs:

S = copilotcli:/11111111-1111-4111-8111-111111111111
Advertised defaultChat = ahp-chat://default/<base64url-encoding-of-UTF8(S), without padding>
Resource identified by the CLI attach failure = S + "/chat"

Both tested CLI versions fail with the same resource shape.

Expected behavior

When SessionState.defaultChat is present, native resume should use that advertised resource rather than assume a chat URI can be constructed by appending /chat to the session URI. Changes to the advertised default chat should also be handled without retaining a stale derived address.

Useful public source anchors:

Please add a native-client regression case in which the advertised chat URI differs from <sessionUri>/chat, and verify that resume follows the advertised resource.

Boundaries

The failure and advertised state were observed with the official distributions above. The exact proprietary CLI implementation responsible has not been identified from public source; this report does not claim that a particular internal function is at fault.

A separate generic session-create/URI-preservation failure exists and is being investigated independently. Provider omission alone is not established as its cause.

No credentials, real endpoints, local paths, raw logs, private project code, or real session identifiers are included here.

Linguagem predominante
Shell
Estrelas
11.2k
Forks
1.9k
Merge médio
17h 6min
PRs com merge (30d)
5

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/copilot-cli

Todas as issues de github/copilot-cli

Issues semelhantes

Mais issues de Shell/Bash

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.