Bump agent-session-kit to 0.6.3 - #7
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Aug 31, 2026
Merged
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
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
Auspex was pinned to
0.6.1, two releases behind. This branch was opened by the dailybump-agent-session-kitworkflow and had not been turned into a pull request; it is worth landing rather than letting it age, because one of the two releases fixes a crash in exactly the shape Auspex runs.0.6.3 —
SO_NOSIGPIPEon every MCP socket descriptor. A peer vanishing between poll and write raisedSIGPIPEand killed the host process with no crash report. The kit's release note describes the symptom as "a menu bar host's recurring silent exits after hours of uptime". Auspex is a long-running MCP server, so it is squarely in the blast radius. The listening descriptor, accepted descriptors, and the stdio bridge's connect descriptor now carry the flag, so a write to a departed peer fails withEPIPEand the ordinary teardown path runs.0.6.2 — AntiGravity turn dating.
agy~1.1.18 stopped writing per-turn wall time and writes an elapsed offset instead; the reader now resolves it against the trajectory's own start time.No API changes — pin bump only, plus the matching row in
AGENTS.md.Test plan
swift build: clean.swift test: 1320 tests in 146 suites green, run five times. (One earlier run flaked while other builds were competing for the machine and did not reproduce.)Follow-up
A later bump takes this to
0.7.0, which splits the kit into peer Swift and Rust implementation lanes. That change keeps every product name, path, and import identical for Swift consumers — verified by building this package against it — so it is a separate mechanical bump rather than part of this fix.🤖 Generated with Claude Code