Draft
Conversation
gg() is designed to be always-on — it's a no-op when not activated, so there's no cost to leaving calls in production. Removing the if (dev) gate allows logs to appear when gg is enabled in Tauri builds (where there's no URL bar to append ?gg).
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.
This branch incrementally adds
@leftium/ggto Whispering across 4 commits, replacingconsole.*calls withgg()to demonstrate the integration path and unlock agent-accessible runtime logs.What each commit does
What this enables
gg()output with source locations, level filtering, and click-to-open-in-editorcurl http://localhost:1420/__gg/logsreturns NDJSON for programmatic querying (filter by level, file, message content viajq)gg()calls are always-on (no-op when not activated), so logs are available in Tauri builds without a dev serverggCallSitesPluginrewrites call sites at build time, so every log entry includes its real file path and function nameIntegration effort
The actual integration is 3 touches:
bun add @leftium/gg...ggPlugins()spread invite.config.ts<GgConsole />in root layoutAfter that, replacing
console.*→gg()is mechanical 1:1 substitution. No refactoring, no new abstractions.Next: live debug demo for #1282
The next step (not committed) is a live agent-driven debug session targeting issue #1282 (moonshine tiny model returns empty transcription). The agent will add
gg()calls to the transcription pipeline, query logs via the fileSink endpoint, and iterate — demonstrating the agent-accessible logging workflow.' | pbcopy