Repository navigation
Conversation
Muse 1.4.4 rejects `continue` in PreToolUse hook output ("unsupported
`continue` in output of PreToolUse hook output") and records the hook as
failed on every tool call; T3 shows each as a failed item. With no output
Muse applies its normal approval, which is what the pass-through meant.
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.
Problem
Muse Code 1.4.4 checks PreToolUse hook output and rejects
continuethere.hooks/recall-approve.jsprints{"continue": true, "suppressOutput": true}for every tool that isn't one of Supermemory's read-only recall tools, so since 1.4.4 every tool call records this hook as failed:The tool call itself still runs, but the session log has a failed hook run per tool call, and hosts that show hook runs (T3 Code, for one) list each as a failed item. Session start, prompt recall and capture are unaffected.
Change
For tools other than the recall tools, the hook now prints nothing and exits 0. That is what the pass-through meant: no decision, so Muse applies its normal approval. The allow path for
search_memoryand the other read-only tools is unchanged (hookSpecificOutputwithpermissionDecision: "allow"and a reason), and Muse 1.4.4 accepts it. The error paths print nothing too.Tests
node --test test/unit.mjs: 7 pass (Node 24, Windows). The existing "does not auto-allow writes" case now expects empty output instead ofcontinue: true; it fails onmain.muse plugins validate .passes on Muse 1.4.4.I run the same hook change on top of #2's branch (which doesn't touch this file) on four machines (Windows, macOS, two Linux). In real Muse 1.4.4 sessions with tool calls,
recall-approvenow completes, and session start, recall and capture still complete. Before the change each tool call logged the error above.This is independent of #2: it changes different code, and the two only meet in
test/unit.mjs, in different places (a test merge of both branches is clean).🤖 Generated with Claude Code