Skip to content

fix: show the context notice to the user, not the model (0.0.74) - #94

Merged
okisdev merged 3 commits into
mainfrom
notice-context-to-user
Nov 14, 2026
Merged

okisdev merged 3 commits into
mainfrom
notice-context-to-user

Conversation

@okisdev

@okisdev okisdev commented Nov 14, 2026

Copy link
Copy Markdown
Owner

summary

  • the parent context advisory reached the model as hook context and told it to "prefer /compact or a fresh session before the next goal". only the user can do either, so the model relayed the advice inside its answer. 219 of 1188 recorded sessions on one host received it.
  • the notice is now a systemMessage on all three paths (fleet-posture.mjs at the prompt, and the peer and worker dispatch paths in lifecycle/tools.mjs), so the user sees one line and the model context gets nothing. claimParentContextAdvisory returns the tagged notice, and a first reading past both the threshold and 800,000 tokens shows one line instead of the same line twice.
  • orchestration.md no longer says a new goal prefers a fresh session. that sentence sat in context every turn, outside the once per threshold claim, so the model could raise it at any goal boundary. it now says the decision is the user's and the main session never recommends either unasked.
  • tests/codex-jobs-monitor.test.mjs waits for the grok observer state file before reading it. it read the file as soon as the sidecars appeared and failed 3 of 5 full suite runs with ENOENT.
  • release 0.0.74 across every plugin and the marketplace, with a changelog entry. rules-manifest.json is generated.

test plan

already verified

  • npm test on this head: 1967 pass, 0 fail, 3 skipped, three runs in a row after the monitor test fix
  • node --test tests/codex-jobs-monitor.test.mjs: 62 pass, 0 fail
  • claude plugin validate passes for codex, grok, cursor, devin, fusion, and the marketplace root

reviewer should verify

  • in a session past 250k context tokens, the next prompt shows the notice as a system line and the model's reply does not mention /compact or a fresh session

notes

  • rules checklist: one sentence is replaced. the deleted instruction ("a new goal after a heavy implementation goal prefers a fresh session") is removed on purpose, because the main session cannot act on it except by telling the user; the cost reasoning and the FUSION_PARENT_CONTEXT_ADVISORY_TOKENS threshold stay. no invariant in CONTRIBUTING.md changes.
  • deliberately not changed: the 250,000 default (reread cost follows absolute tokens, not the window) and once per threshold per session with no re-arm after compaction, which 0.0.65 chose.
  • the installed ~/.claude/rules/orchestration.md picks up the new sentence on the next /fusion:setup.

@okisdev
okisdev merged commit 5e64a75 into main Nov 14, 2026
4 checks passed
@okisdev
okisdev deleted the notice-context-to-user branch November 14, 2026 17:59
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