Repository navigation
1.49.0: the job records only stretch the Background listing's cache, never replace the command - #71
Closed
writingdeveloper wants to merge 1 commit into
Closed
writingdeveloper wants to merge 1 commit into
writingdeveloper wants to merge 1 commit into
Conversation
…they never replace the command The v1.49.0 release run failed its Windows journeys: the cockpit-tools harness answers `claude agents --json` from a fake claude over an isolated HOME with no ~/.claude/jobs records, and the new listing took "no records" as "no sessions" and never asked. The same would hit a Claude Code that keeps its records elsewhere. Records unchanged since the last listing — including none at all — now mean the last answer holds for up to five minutes; a change runs the command at once; the first listing always runs. At rest that is one process per five minutes instead of one per 30–120 s, with no assumption about where the records live. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LdbKDr2tTfCLAZv7WbV8kX
writingdeveloper
added a commit
that referenced
this pull request
Oct 28, 2026
…they never replace the command (#71) The v1.49.0 release run failed its Windows journeys: the cockpit-tools harness answers `claude agents --json` from a fake claude over an isolated HOME with no ~/.claude/jobs records, and the new listing took "no records" as "no sessions" and never asked. The same would hit a Claude Code that keeps its records elsewhere. Records unchanged since the last listing — including none at all — now mean the last answer holds for up to five minutes; a change runs the command at once; the first listing always runs. At rest that is one process per five minutes instead of one per 30–120 s, with no assumption about where the records live. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LdbKDr2tTfCLAZv7WbV8kX
Owner
Author
|
Squash-merged to main as 4865f40; v1.49.0 re-tagged on it and the Release workflow runs from the tag. |
writingdeveloper
deleted the
fix/bg-listing-records-only-stretch-cache
branch
October 28, 2026 02:51
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.
The v1.49.0 Release run (40622219006) failed its Windows "failure and recovery journeys": the cockpit-tools harness answers
claude agents --jsonfrom a fakeclaudeover an isolated HOME that has no~/.claude/jobsrecords, and the new listing in 1.49.0 took "no records" as "no sessions" and never asked. A Claude Code that keeps its records elsewhere would have hit the same.Records unchanged since the last listing — including none at all — now mean the last answer holds for up to five minutes; a change runs the command at once; the first listing always runs. At rest that is one process per five minutes instead of one per 30–120 s, with no assumption about where the records live. Release notes adjusted; the unit test now states the new rule.
The
v1.49.0tag (which pointed at the failed run's commit, with no assets published) is re-created on main after this merges.🤖 Generated with Claude Code
https://claude.ai/code/session_01LdbKDr2tTfCLAZv7WbV8kX