Repository navigation
release: v0.11.2 — pi session resume + scoped follow-ups - #44
Merged
Merged
Conversation
Builds on @shellus's pi work (#43, commits f727ba4..afc2c09, authorship preserved) and scopes it to a clean pi-only release. Kept from #43: - pi resume by id (pi --session '<id>'), verified against pi-mono source - keep every session per project selectable - pi prompt summaries + full History parity - CACHE_VERSION 5 (one-time rescan on upgrade) Follow-ups in this commit: - revert the default-to-cwd search query: it changed no-arg behavior for every agent and re-introduced the cwd special-casing removed in v0.11.0 - bound pi parse_session with a 512 KiB read budget so the forced cold rescan can't stall on multi-MB transcripts (mirrors read_head_tail) - restore the Kiro resume-latest note on Agent::Kiro::resume_cmd - regression test for the byte-budget cap Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on @shellus's pi work in #43 (already merged to main, commits f727ba4..afc2c09, authorship preserved) and scopes it into a clean pi-only release.
Kept from #43 (verified)
pi --session '<id>'. Verified against the pi-mono source (resolveSessionPath,packages/coding-agent/src/main.ts): a bare id with no//\/.jsonlis prefix-matched against the session store, and since agf wraps resume ascd '<project_path>' && pi --session '<id>', pi resolves it locally and resumes directly (no fork prompt). Confirmed on pi 0.53.0.CACHE_VERSION5 — one-time rescan on upgrade.Follow-ups in this PR
$PWDwhenagfran with no query. That changed no-arg behavior for every agent (empty list in non-project dirs) and re-introduced the cwd special-casing deliberately removed in v0.11.0 (the cwd-match sort boost made time-sort look broken). Deferred to a future opt-in setting.pi parse_sessionwith a 512 KiB read budget — collecting every prompt requires reading the whole JSONL, but pi transcripts can reach several MB and theCACHE_VERSIONbump forces a cold rescan for everyone on upgrade. The read loop now stops after 512 KiB (header is line 1, always captured), mirroringread_head_tail(added v0.10.1 after large Claude logs stalled the TUI).kiro-cli chat --resumehas no per-session flag; note moved ontoAgent::Kiroinresume_cmd.Test plan
cargo fmt --all --checkcargo clippy --all-targets -- -D warningscargo test— 31 passedcargo build --release;agf listworks across agents;agf --version→ 0.11.2resume_cmdunchanged