Repository navigation
Check in on a thread every 30 minutes while it says something is running - #218
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yobazy
added a commit
that referenced
this pull request
Nov 13, 2026
…nning elsewhere finishes "Needs you: Nothing until it finishes" with a verdict saying the run is in progress counted as asking you something, so a run started on the PC showed in Decisions as if you hadn't started it. Uses the same running verdict check-ins (#218) watch for. "Nothing yet, but…" still asks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yobazy
added a commit
that referenced
this pull request
Nov 13, 2026
… you (#221) From a marked moment (2026-11-13 07:37): a thread that had started a run on the PC still showed in Decisions with its old "Paste this to start it" card, as if nothing had been sent. Two causes, two commits: 1. **Decisions missed the new reply.** It re-reads a thread only when its status changes. The turn that started the run (a "! cmd", then a quick reply) never moved the status, so the card from before stayed. Decisions now re-reads its listed threads, and any that moved in the last six hours, when it opens and every minute while it's open. A replayed moment's thread (`scripts/drive replay`) now reads in Decisions too. 2. **The new reply counted as a decision anyway.** Its Needs you was "Nothing until it finishes. I'm watching the run…" with the verdict "🟠 Keep open: round four is running". A Needs you that starts with "Nothing"/"None" (with no "but"/"unless" in that sentence) no longer counts while the verdict says something is running, the same check the 30-minute check-ins (#218) use. "Nothing yet, but confirm the API key" and "Nothing until you've tried it" still ask. The thread stays in Follow up, and check-ins keep asking it for status every 30 minutes. ## Before / after Browser mock with the moment's own transcript stood in for a thread, in Decisions: | Before | After | |---|---| |  |  | Also checked in the mock: with only the transcript up to the start-command reply, the thread shows (correct); the next reply landing with no status change leaves it showing; `recheck()` takes it off. The PC sandbox couldn't show it: its fake threads sit as Working, so none reach Decisions. ## Checks - `npm run build && npm test` pass. One run hit the existing timing test "answers read in linear time" (over 200 ms while the Mac was busy); it passed on three reruns. - No Rust changes, so cargo was not run. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <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.
From a marked moment: work an agent starts on
pc(a tmux run that takes hours) leaves its thread Done with "🟠 Keep open: round 3 is running onpc", and the only way to see progress was to type "status" into it by hand.What changes
● Checking in · next in 27m, which you click to stop. Any other 🟠 verdict offers Check in every 30m to turn it on by hand. The choice is per thread and kept across launches.followUpgets abackgroundoption that attaches behind the current view, so what you're looking at doesn't change.running…with that verdict, andVITE_CHECK_IN_MS=60000shortens the wait in a dev build.Seen working (PC sandbox)
Clicked off, it offers to turn back on:
With
VITE_CHECK_IN_MS=60000, the check-ins reached the agent once a minute. The fake agent never changes its verdict, so they kept coming. This shot has the first, longer wording of the prompt:Checks
npm run build && npm test(625 pass, including the newtests/checkin.test.mjs);cargo fmt --check,clippy -D warningsandcargo testpass.Not tried on a real Claude thread yet. Each check-in is a normal agent turn, so a 4-hour job costs about 8 short turns.
🤖 Generated with Claude Code