Skip to content

Remove success field from logging-set-level JSON output#48

Merged
jancurn merged 3 commits intomainfrom
claude/fix-logging-set-level-dsREp
Mar 8, 2026
Merged

Remove success field from logging-set-level JSON output#48
jancurn merged 3 commits intomainfrom
claude/fix-logging-set-level-dsREp

Conversation

@jancurn
Copy link
Member

@jancurn jancurn commented Mar 8, 2026

Summary

Simplified the JSON output format for the logging-set-level command to align with the project's convention of using exit codes to indicate errors rather than including a success field in the response.

Changes

  • Removed the success: true field from the JSON output of setLogLevel() command
  • Updated output format from {"level":"<level>","success":true} to {"level":"<level>"} for consistency with project conventions
  • Simplified the formatOutput() call by removing unnecessary object properties

Details

The change reflects the project's design principle that command success/failure should be communicated through exit codes rather than response body fields. This makes the JSON output cleaner and more consistent across the CLI interface.

https://claude.ai/code/session_01TaCYsayZaZcijd3K2QZXVo

claude and others added 3 commits March 8, 2026 22:17
Remove the `success: true` field from `logging-set-level` JSON output,
aligning it with the project convention of indicating errors via exit
codes rather than wrapping responses in a success field.

https://claude.ai/code/session_01TaCYsayZaZcijd3K2QZXVo
The bridge was not registering a handler for LoggingMessageNotification,
so server log messages were silently dropped. Register the handler on
the SDK client after connection and broadcast to IPC clients, making
logging-set-level actually observable in the interactive shell.

https://claude.ai/code/session_01TaCYsayZaZcijd3K2QZXVo
@jancurn jancurn merged commit 83e349f into main Mar 8, 2026
6 checks passed
@jancurn jancurn deleted the claude/fix-logging-set-level-dsREp branch March 12, 2026 14:17
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.

3 participants