Repository navigation
fix: spend guard warns by default and stops false refusals; server-linked threads open and mark unread - #139
Merged
nullStack65 merged 3 commits intoNov 20, 2026
Conversation
…a founder's resumed turn The session spend guard defaulted to enforce, so an idle thread over $50 refused every automated turn. It is an alert, so the default is now flag; enforce stays available as a setting. Two bugs made the refusals wrong. Other-agent input (subagents, compaction) was priced as fully uncached input although the process ledger adds cache reads into that number, so one 24-lane turn read $89 instead of about $14 and tripped the idle limit even on threads with a linked pull request. The refusal text also said no pull request was linked when one was. And a restart continuation is created by the server, so a founder's own "continue anyway" turn, interrupted by a restart, was refused as automated. The guard now follows the continuation chain back to the message that started it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…marked unread A thread listed only through a server link (omarcy-desktop on the laptop) has no connection in this device's catalog. Opening it left the route waiting on a shell that never loads, so the pane stayed blank and the route also started thread loads against an environment the device cannot reach. Mark unread looked the thread up among catalog shells only, found nothing, and silently did nothing. The route now shows which host owns the thread and links to connection settings, and skips the unlisted-thread load for such environments. Mark unread falls back to the sidebar's linked shell so the local unread marker is set. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Review finding: a founder's turn that hit a usage limit and was then continued by a restart was still read as automated, because the walk only followed restart continuation links. The walk now follows either link, and the restart-continuation test asserts that no refusal was recorded. Co-Authored-By: Claude Sonnet 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.
Two fixes Kameron asked for on 2026-11-20, against the release line.
1. Session spend guard (idle-spend guard from CLO-922)
sessionSpendGuard.modeis nowflag(warn only).enforcestays a setting. Live settings on all five machines were already hot-patched toflag; this makes it the default for new installs.originCreationSource).flag, the refusal of automated launches on untitled threads is also off by default, since it only applies inenforcemode.2. Remote threads blank pane and mark unread (server-linked environments, CLO-963)
ThreadRouteViewwaited forever for a shell (blank pane) and started thread loads against an environment the device cannot reach. It now shows which host owns the thread with a link to connection settings.readLinkedSidebarThreadShell.Not a protocol or migration mismatch: the older
omarcy-desktopbuild is not the cause of the blank pane.Deploy: fleet
🤖 Generated with Claude Code