Skip to content

fix: spend guard warns by default and stops false refusals; server-linked threads open and mark unread - #139

Merged
nullStack65 merged 3 commits into
release/native-0.1.10from
fix/spend-guard-flag-remote-open
Nov 20, 2026
Merged

nullStack65 merged 3 commits into
release/native-0.1.10from
fix/spend-guard-flag-remote-open

Conversation

@nullStack65

@nullStack65 nullStack65 commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

Two fixes Kameron asked for on 2026-11-20, against the release line.

1. Session spend guard (idle-spend guard from CLO-922)

  • Default sessionSpendGuard.mode is now flag (warn only). enforce stays a setting. Live settings on all five machines were already hot-patched to flag; this makes it the default for new installs.
  • False "$50 no linked pull request" refusals: other-agent input (subagents, compaction) was priced as uncached input, but the ledger adds cache reads into that figure, so a 24-lane turn counted $89 instead of about $14. Pricing now uses the main agent's cache mix in the same turn. Refusal text says "since its last linked pull request or file-changing turn" when a pull request exists.
  • Restart continuations are 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 original message's source (originCreationSource).
  • With the default now flag, the refusal of automated launches on untitled threads is also off by default, since it only applies in enforce mode.
  • The origin walk follows both restart and usage limit continuation links.
  • Regression tests: other-agent cache-mix pricing, linked-PR wording, origin-source chain, and a restart continuation of a web turn passes at the ceiling while one of an MCP turn is still refused.

2. Remote threads blank pane and mark unread (server-linked environments, CLO-963)

  • A thread listed only through a server link has no connection in the device catalog. ThreadRouteView waited 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.
  • Mark unread looked the thread up among catalog shells only and silently did nothing. It now falls back to the sidebar's linked shell.
  • Tests: readLinkedSidebarThreadShell.

Not a protocol or migration mismatch: the older omarcy-desktop build is not the cause of the blank pane.

Deploy: fleet

🤖 Generated with Claude Code

nullStack65 and others added 2 commits November 20, 2026 09:47
…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>
@coderabbitai

coderabbitai Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

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>
@nullStack65
nullStack65 merged commit fff16cc into release/native-0.1.10 Nov 20, 2026
3 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant