Say what to do when catchup itself fails - #12
Merged
Conversation
wilbeibi
force-pushed
the
skill-report-catchup-failures
branch
from
September 4, 2026 04:21
c9bf475 to
bbfb9a9
Compare
wilbeibi
changed the title
An agent that hits a catchup error has no rule for it, so it either retries blindly or reports a bug that is really a local problem — a typo, a directory with no sessions, an agent that is not installed. The skill now says to follow the recovery the error already names, lists what is local and never a bug (including a non-zero exit from fork, which is the launched agent's own status), and describes the report worth filing when nothing explains the failure: searched for duplicates, carrying no transcript text, session IDs, credentials, or home paths, and opened only when the user asks.
wilbeibi
force-pushed
the
skill-report-catchup-failures
branch
from
September 4, 2026 04:21
bbfb9a9 to
a58c45e
Compare
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
1 participant
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.
An agent that hits a
catchuperror has no rule for what to do with it. It retries blindly, or it reports a bug that is really a local problem — a typo in the agent name, a directory with no sessions, an agent that is not installed.The skill now carries the rule. Follow the recovery the error already names; catchup's messages are written to contain one. Treat as local and never a bug: a usage mistake, no matching session, an unreadable path, a missing agent binary, and a non-zero exit from
fork, which is the launched agent's own status passing through rather than a catchup failure. Everything left — a crash, a wrong answer, a failure that repeats — is worth a report, searched for duplicates first, carrying the command, the error, the expectation,catchup --version, and OS/arch, and carrying no transcript text, session IDs, credentials, or home paths. The issue is opened only when the user asks; otherwise the draft is shown.No CLI or runtime change:
SKILL.mdonly, one bullet and one trigger phrase in the description.Depends on #13, which makes the "a non-zero exit from
forkis the agent's, not catchup's" line true — before it, every such exit was reported ascatchup: exit status Nand flattened to 1.