Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Plan history loses its Versions tab when the agent changes directory into another git repo between submits

Aperta
  • Qualcosa non va?
#2,197 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@backnotprop ci sta già lavorando.

Dal 26/10/2026.

  • #2199 di @backnotprop — aperta
  • #2205 di @aomalov — aperta

Valutazione

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

Direzione di ricerca

Start with server/index.ts and trace how startPlannotatorServer detects the project and saves plan history. Then read the Claude Code plan launch path in apps/hook/hooks/mod/controller.ts and the classic PermissionRequest hook to see which session directory information is available. Done means consecutive submits stay in the same history chain after the agent changes directories, so the Versions tab and diff remain available.

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

Descrizione

bug
What happened?

When the agent changes directory into a different git repo between two plan submits, the Versions tab disappears and there is no diff. The revised plan is correct and the earlier version is still on disk; they just land in two different history projects, so the UI sees a chain of length 1.

Concretely: a Claude Code session started in a workspace repo (workspace) whose subfolders are separate git clones. The first submit went to history/workspace/<slug>/001.md. Before the resubmit, the agent ran cd service-a (a nested clone) in its shell, and the second submit went to history/service-a/<slug>/001.md. The session record for the second review shows "project": "service-a".

Root cause: the history project is detected from the process cwd at every submit.

packages/server/index.ts (startPlannotatorServer):

project = (await detectProjectName()) ?? "_unknown";
historySlug = resolveHistorySlug(project, slug);
const historyResult = saveToHistory(project, historySlug, plan);

detectProjectName() defaults to process.cwd() and returns the basename of git rev-parse --show-toplevel. The plan CLI inherits whatever directory the session is in at that moment:

  • the Claude Code mod launches plannotator claude-mod-plan without a cwd or PLANNOTATOR_CWD (apps/hook/hooks/mod/controller.ts, launch)
  • the classic PermissionRequest hook runs plannotator in the session's current directory

So a shell cd mid-session (common in multi-repo workspaces and monorepos with nested clones) changes the project key, getNextVersionNumber returns 1 in the fresh directory, previousPlan is null, and the Versions gate never opens. The code-review paths already prefer PLANNOTATOR_CWD; the plan paths ignore it.

This is the same class of bug as #1679 (history key not stable across a resubmit), on the project half of history/{project}/{slug} rather than the slug half.

Suggested fix

  1. Name the history project from the session's project root rather than the current directory: $.session.root() in the mod (a shell cd does not move it), CLAUDE_PROJECT_DIR in the classic hook.
  2. Pin a plan's project per (session, date-free slug) on its first save, so /cd or a worktree move mid-plan still continues the same chain.

Other agents (OpenCode, Pi, Codex, Gemini, Copilot, Droid, Vibe) are unaffected.

Plannotator version

plannotator 0.28.31

OS

macOS

Agent

Claude Code

Where did it happen?

Plan review

Lingua principale
TypeScript
Stelle
8.7k
Fork
649
Merge medio
4h 9m
PR unite (30g)
448

Preparare l'ambiente

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 backnotprop/plannotator

Tutte le issue di backnotprop/plannotator

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.