Investigate conversation recovery after folder renames in Codex and Claude Code

Aperta
  • Qualcosa non va?
#61 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
devtools

Direzione di ricerca

Start from the Claude Code session-storage and /cd docs and the Codex codex resume --all and --cd docs linked in the issue, then reproduce on a disposable project: create a conversation, record its session id and path, rename the folder, and check resume in each interface. Done means a per-interface verdict (automatic, manual recovery, or unresolved) plus a reviewed backup-and-recovery procedure. The active repository folder must not be renamed or real session storage changed during validation.

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

Descrizione

Problem

Renaming or moving a local project folder can make existing coding-agent conversations disappear from the project history or prevent those conversations from resuming in the correct directory.

Jérôme reports experiencing this problem with another folder. The affected folder, application, version, and exact symptoms have not yet been recorded. This is an actual user report, not only a hypothetical concern about this repository.

Desired answer

Establish what happens in the installed versions of Codex and Claude Code, and provide a tested procedure for recovering existing conversations and preserving continuity when a project folder moves or is renamed. Distinguish command-line applications, desktop applications, and editor integrations; success in one interface does not prove success in another.

Documentation and reported failures

Claude Code documents project-directory session storage, moving an individual session with /cd, and finding a session across projects with claude --resume <session-id>:

https://code.claude.com/docs/en/sessions#sessions-in-other-worktrees-and-projects

Codex documents codex resume --all, choosing the current or saved directory when resuming, and an explicit --cd directory override:

https://learn.chatgpt.com/docs/developer-commands?surface=cli

These commands provide individual-session recovery routes. They do not establish that a filesystem rename automatically migrates all project history, memory, permissions, or application configuration.

Reported failures in the upstream repositories are evidence of problems in the reported versions, not proof of current behaviour in Jérôme's installed versions:

Investigation and validation

  1. Record the affected interfaces and installed versions, and obtain the missing details of Jérôme's existing affected folder before attempting recovery there.
  2. Use a disposable project in each actual interface Jérôme uses. Create a representative conversation with an identifiable fact and a file operation, and record its session identifier and original absolute path.
  3. Close the sessions, rename the disposable project folder, and record whether the conversation remains visible and resumable.
  4. Test the documented recovery procedure. Verify the conversation retains its earlier context and file operations use the new directory.
  5. Restart the application and verify that the recovered conversation remains discoverable and resumes in the new directory.
  6. Check separately what happens to other conversations, project memory, permissions, configured paths, and linked Git worktrees where applicable. Do not generalize a single recovered conversation to the entire project.
  7. Record raw output or exact visible messages, versions, steps, results, and remaining limits. Distinguish hidden history from deleted transcripts and from failure to resume.

Deliverables and acceptance criteria

  • A clear answer for each tested interface: automatic preservation, supported manual recovery, or unresolved failure.
  • A reviewable recovery and migration procedure, including backup and rollback steps before changing real session storage.
  • A tested answer for the already affected folder once its identity and symptoms are established.
  • Explicit evidence boundaries: documentation, upstream reports, local reproduction, and successful local recovery.
  • No renaming of the active repository folder or rewriting of real conversation storage as part of preliminary validation.

Related repository rename

This investigation informs the existing repository rename request:

Lingua principale
Nessun dato sulla lingua
Stelle
1
Fork
0
Merge medio
7m
PR unite (30g)
17

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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.

Altre issue di jeromeetienne/coding_agent_plugin

Tutte le issue di jeromeetienne/coding_agent_plugin

Issue simili

Altre issue su DevTools

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.