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

Duplicate Remote CLI session entries on github.com/copilot for a single desktop chat

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

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
cli, desktop, observability

Direção de pesquisa

The issue describes duplicate session entries in the GitHub Copilot web interface for a single desktop chat. Start by examining the session registration and synchronization logic between the desktop app and the cloud service. Look for where session IDs are generated and logged. Check the agent session listing API endpoint and the data flow that creates 'Remote CLI session' entries. Determine what 'done' looks like by verifying a single desktop chat produces only one corresponding web entry.

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

Descrição

Short summary

A single desktop chat appears to produce duplicate entries under Agent sessions on github.com/copilot, labeled Remote CLI session. This has occurred for multiple chats.

Affected version or release

Desktop app version not collected. Please advise which app/CLI diagnostics would help identify the affected build.

Installation context

GitHub Copilot desktop app on Windows, with remote sessions viewed at https://github.com/copilot in Chrome. Exact Windows and Chrome versions were not collected.

What happened?

The user repeatedly sees duplicate remote session entries. A screenshot supplied privately shows two entries with the same chat title, both labeled Remote CLI session and both displaying the same relative age (14m).

Read-only observations from this report's investigation:

  • The app's session/chat listing contains only one chat for the title duplicated in the screenshot.
  • A separate cloud session-history query found two other pairs of records: within each pair, the summary and creation timestamp are identical, but the session IDs differ.
  • In one pair the last-updated timestamps differ; in the other they are identical.

These observations are consistent with duplicate cloud session records, but do not establish the root cause or prove that the underlying agent task executed twice. The cloud history results did not include the most recent screenshot sessions, so the historical record pairs are supporting evidence, not a confirmed ID mapping for the screenshot.

Steps to reproduce

Observed workflow (not yet a deterministic reproduction):

  1. Use a chat in the Copilot desktop app.
  2. Open https://github.com/copilot and inspect Agent sessions.
  3. Observe multiple Remote CLI session entries corresponding to what appears as a single chat in the desktop app.

The user reports this happens repeatedly across chats. Whether reconnecting, restarting, or renaming is involved has not been established.

Expected behavior

One logical chat/session should have one remote session entry, unless a distinct session is explicitly created. If multiple entries are intentional, the UI should explain their relationship so they are not mistaken for duplicate sessions or duplicate execution.

Additional context

Observed on September 23, 2026. Please investigate session identity mapping, registration/synchronization, and deduplication between desktop chats and the web Agent sessions list; these are investigation suggestions, not confirmed causes.

Submitted at the user's explicit request. Private chat contents, titles, account/local paths, raw session IDs, and the original screenshot have intentionally been omitted from this public report. Debug logs have not been collected or uploaded.

Linguagem predominante
Sem dados de linguagem
Estrelas
2.2k
Forks
176
Nenhum PR com merge em 30d

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/app

Todas as issues de github/app

Issues semelhantes

Mais issues de CLI

Receba novas issues na sua caixa de entrada

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