Repository navigation
Claude cannot resume multi-step workflows across sessions #341
Description
Problem
When resuming work in a new Claude Code session, Claude cannot locate:
- Workflow progress — which phase of a multi-step workflow (e.g., office-hours → ceo-review → eng-review → build → review → qa → ship) was completed
- Intermediate artifacts — design docs, plan files, and review results stored outside the project directory
What happened
- Running a gstack workflow cycle:
office-hours → plan-ceo-review → plan-eng-review → build → review → ship - Completed through
plan-ceo-review, next step wasplan-eng-review - Started a new session, asked Claude to resume
- Claude incorrectly reported the full cycle as complete (checked TODOS.md which had a different cycle marked done)
- Could not find intermediate artifacts until user manually pointed to
~/.gstack/projects/$SLUG/
Environment
| Item | Value |
|---|---|
| Claude Code | 2.1.81 |
| OS | WSL2 (Linux 6.6.87) |
| Shell | bash |
| Project | /home/nicezic/mygstack |
Relevant paths Claude should know about
| Path | Purpose |
|---|---|
~/.gstack/projects/$SLUG/ |
Workflow intermediate artifacts (design docs, plans, reviews) |
~/.gstack/projects/$SLUG/ceo-plans/ |
CEO review plans with status |
~/.claude/projects/*/*.jsonl |
Session logs (not parsed for continuity) |
Expected behavior
When resuming a session, Claude should:
- Check for active workflow artifacts (e.g., scan
~/.gstack/projects/for status: ACTIVE plans) - Determine the last completed phase and the next pending step
- Present the workflow progress tracker before asking "where were we?"
Possible solutions
- CLAUDE.md directive — add artifact paths so Claude knows where to look on session start
- Workflow state file — gstack skills write a
workflow-state.jsonwith current phase - Auto-memory enhancement — allow memory type for workflow checkpoints
Activity
sevastyanovio commentedon Mar 23, 2026
Related to this: PR #405 (
/meditate) adds conversation mining across past Claude Code, Codex, and Gemini sessions. The scanner discovers what files were referenced, what skills were invoked, and what work was in progress — then surfaces it in.gstack/context.mdunder "Watch These Next."It doesn't fully solve workflow resumption (that would need explicit state checkpointing), but it gives the new session enough context to know "you were working on X, using /review and /ship, touching these files" — which gets you most of the way there without new infrastructure.
time-attack commentedon Jul 15, 2026
@16francej Please close this issue as resolved. Current Context Recovery finds plans, saved checkpoints, and timeline events and tells the user which workflow step to continue. More detailed progress reporting can be tracked separately.