Remove JSON export from bdg stop #157
Open
Conversation
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
sfc-gh-mochen
force-pushed
the
mochen-remove-stop-json-export
branch
from
1079a06 to
05eebff
Compare
- Remove session.json file write on stop - Remove offline session fallback from network commands - Delete unused output.ts module - Update skill to discourage premature stop calls - Remove 'save output' references from UI messages - Demote 'bdg stop' in command listings (show peek/tail first) - Update golden workflow test to use peek instead of session.json - Users should use bdg peek to inspect telemetry data
sfc-gh-mochen
force-pushed
the
mochen-remove-stop-json-export
branch
from
05eebff to
b807b13
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
session.jsonfile write when callingbdg stopsrc/session/output.tsmoduleMotivation
Claude agents were calling
bdg stoptoo frequently, ending sessions prematurely. Sincebdg peekalready provides access to telemetry data without stopping the session, the JSON export on stop was redundant and encouraged unnecessary session termination.Changes
bdg stopnow simply ends the session without writing any filebdg peekto inspect telemetry data before stopping if neededTest plan
bdg <url>→bdg peek→bdg stopworks without errorssession.jsonis created on stop