Skip to content

fix(hooks): don't emit a second JSON object on Qoder report-only /pon…#617

Open
adiraj66132 wants to merge 1 commit into
DietrichGebert:mainfrom
adiraj66132:fix/qoder-double-json
Open

fix(hooks): don't emit a second JSON object on Qoder report-only /pon…#617
adiraj66132 wants to merge 1 commit into
DietrichGebert:mainfrom
adiraj66132:fix/qoder-double-json

Conversation

@adiraj66132

Copy link
Copy Markdown

…ytail

On Qoder there's no SessionStart, so UserPromptSubmit does double duty: it reports the current mode for a bare /ponytail, and it also emits the full ruleset. Both paths wrote a JSON object to stdout, so the hook output was two concatenated objects — unparseable, and the ruleset the user actually wanted never made it through.

Skip the report-only confirmation on Qoder; the ruleset block already covers it. Other hosts are untouched. Added a regression test asserting a single parseable JSON object for that case.

…ytail

On Qoder there's no SessionStart, so UserPromptSubmit does double duty: it
reports the current mode for a bare `/ponytail`, and it also emits the full
ruleset. Both paths wrote a JSON object to stdout, so the hook output was two
concatenated objects — unparseable, and the ruleset the user actually wanted
never made it through.

Skip the report-only confirmation on Qoder; the ruleset block already covers
it. Other hosts are untouched. Added a regression test asserting a single
parseable JSON object for that case.
@adiraj66132
adiraj66132 force-pushed the fix/qoder-double-json branch from b549224 to fbb21ce Compare July 19, 2026 15:11
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