fix: format crumb data on same line as message#17
Merged
Conversation
Data was printed on a new line, making log output harder to scan. Now prints on the same line with breakLength: Infinity to prevent node inspect from wrapping.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
myftija
approved these changes
Mar 11, 2026
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
2 participants
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
webapp:llm-pricing loaded models from db +353ms { count: 145 }breakLength: Infinityonutil.inspectto prevent Node from wrapping the data objectConsoleSink(stderr output) andformatCrumbPretty(CLI tail/query output)Test plan
pnpm buildpassesAGENTCRUMBS=1and verify crumbs print on a single lineagentcrumbs tailandagentcrumbs queryalso show single-line output