Skip to content

Omit the routine Stop link when the status line shows it - #96

Merged
crizCraig merged 5 commits into
mainfrom
feat/stop-link-when-no-statusline
Nov 21, 2026
Merged

crizCraig merged 5 commits into
mainfrom
feat/stop-link-when-no-statusline

Conversation

@crizCraig

@crizCraig crizCraig commented Nov 21, 2026 •

Copy link
Copy Markdown
Owner

The Stop hook omits the routine MemTree link when a recent ccc statusline render acknowledged the current tree URL or the session’s stable URL. Without a matching render in the last 60 seconds, Stop prints the link when due. First-tree announcements, compression notices, warnings, MessageDisplay output and the exit link keep their existing behavior.

Print and non-TTY launches disable the status-line file cache at startup. Interactive launches enable it only when auto-install is on and the resulting settings include ccc’s status line. Model calls still warm the background tree lookup and do zero heartbeat or .url filesystem work. Desktop and direct MCP also run without the interactive status line.

Known limitations

  • ccc checks the status-line configuration at startup. If you configure it mid-session, Stop continues to print the link when due. The next ccc session picks up the new configuration.
  • When two terminals resume the same Claude session, they share a heartbeat. A render in one terminal can suppress the routine Stop link in the other.
  • A custom status line can pipe ccc statusline through a filter that truncates or removes the URL. The renderer records its heartbeat before the filter runs, so Stop can omit a link the user never saw.

Verification

The CLI regression test sends three model calls per launch. It checks for zero status-link file operations in non-TTY, -p, -pc, auto-install-off and unconfigured sessions, and verifies that a configured interactive status line still receives the URL. A proxy regression test verifies that Stop skips an expired lookup when links are off and there is no active status line. Proxy tests cover the Stop fallback and suppression, link refresh, and trailer placement.

Local npm test runs with NO_COLOR=1 and FORCE_COLOR=1 each had 1,747 passes, 21 skips and the same ten baseline failures. Committed dist/ matched a clean build byte for byte.

Also accepted (Codex r5 P2s, both need non-default settings)

  • With CCC_MEMTREE_LINK=off plus CCC_STATUSLINE_REFRESH=1 and a custom status-line script that calls ccc statusline, no automatic link is shown (the user turned the link off).
  • With no status line and CCC_MEMTREE_LINK=off, model calls can still trigger the periodic tree-link lookup.

crizCraig and others added 5 commits November 20, 2026 21:09
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
@crizCraig
crizCraig merged commit 6a5dab7 into main Nov 21, 2026
20 of 21 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