Repository navigation
bump pi deps 0.74/0.79 -> 0.84.4 - #49
Merged
Merged
Conversation
Turn errors (auth 401s, provider 5xx, malformed responses) previously
only surfaced as a single terse line in the user channel — nothing in
journalctl, nothing in the debug channel. When Pollux hit a 401 today
after the pi 0.79→0.84 bump (models.json 'env:VAR' config-value syntax
went stale), the only signal was the in-channel 'agent error' text.
Now: - installStreamingSender logs to stderr with provider/model tag when
a turn stopReason === 'error', so journalctl -u <bot> catches it
- createDebugLogger posts a copy to the debug channel with the source
message linked, matching how tool failures already surface there
Co-authored-by: Shelley <shelley@exe.dev>
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.
Bumps pi-agent-core, pi-ai, pi-coding-agent to 0.84.4.
Breaking fix: services.modelRegistry -> services.modelRuntime, .find -> .getModel.
Includes DeepSeek V4 thinking fixes. Typecheck clean, 102/102 tests pass.