github / github/copilot-cli

`store_memory` fails in v1.0.81 prereleases: `Instance id is required`

Aperta
#4,535 8 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

area:context-memory
Lingua principale
Shell
Stelle
11.2k
Fork
1.9k
Merge medio
14h 16m
PR unite (30g)
6

Descrizione

[From Femi's agent: GPT-5.6 Sol]

Summary

store_memory fails consistently in Copilot CLI 1.0.81 prereleases because the native memory writer is invoked without a required instance ID:

[DEBUG] [rust:copilot_runtime::tools::api::memory] Storing user memory with subject: "agent selection"
[ERROR] [rust:copilot_runtime::tools::api::memory] Failed to store memory: Instance id is required.

The failure occurs locally in the same millisecond as invocation, before the memory writer makes an HTTP request. The tool surfaces only the generic message Unable to store memory: an unexpected error occurred.

Version evidence

Observed across local Copilot session logs:

CLI version Successful writes Instance id is required failures
1.0.79 5 0
1.0.81-3 0 5
1.0.81-4 0 5
1.0.81-5 0 3

There were no memory-write attempts available for 1.0.80 or 1.0.81-0, so the precise first broken build is not yet isolated. The regression is confirmed between 1.0.79 and 1.0.81-3.

In 1.0.79, the writer opened a connection to api.enterprise.githubcopilot.com and returned Memory stored successfully. In 1.0.81-3 through 1.0.81-5, the Rust path rejects the operation immediately with the missing instance-ID error.

Reproduction

  1. Run Copilot CLI 1.0.81-5 in a GitHub-hosted repository.
  2. Invoke store_memory with a valid user-scoped payload:
{
  "scope": "user",
  "subject": "agent selection",
  "fact": "Never use Gemini models as subagents.",
  "reason": "This is a durable model-selection preference that applies across repositories and future delegated tasks.",
  "citations": "User input: \"new rule. never use gemini as a subagent for anything\""
}
  1. Observe the generic tool failure. With debug logging enabled, the underlying error is Instance id is required.

The same underlying error has occurred across unrelated subjects and multiple fresh sessions. Memory enablement and retrieval still work; only writes fail.

Expected behavior

The memory is sent to the service and persisted, as it was in 1.0.79.

Actual behavior

The native memory writer rejects the operation before sending it because its instance ID is missing.

Environment

  • macOS Darwin, arm64
  • GitHub-hosted repository with a valid origin
  • Authenticated GitHub/Copilot account
  • Memory enablement check: enabled
  • Affected builds: 1.0.81-3, 1.0.81-4, 1.0.81-5
  • Last locally verified working build: 1.0.79

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Parti dal punto di ingresso store_memory e dal percorso nativo Rust di scrittura della memoria descritto nei log di debug. Confronta il comportamento funzionante di 1.0.79 con quello delle versioni da 1.0.81-3 a 1.0.81-5, concentrandoti su come viene fornito l'ID dell'istanza prima della richiesta HTTP. Il lavoro è completato quando le memorie valide associate all'utente vengono nuovamente persistite senza l'errore Instance id is required.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
rust
Ambito
backend
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Attiva
Chiarezza
Abbastanza chiara
Idoneità per principianti
48/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.