Repository navigation
feat(seidroid-review): drive sei-agent-driver v0.23.1 - #124
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PR SummaryLow Risk Overview The floor comment now treats v0.23.1 as load-bearing: it polls the session for up to 10s when the reply at turn-end is missing or incomplete, avoiding false no-verdict (exit 5) on claude-native when the final message lands after the turn-end edge. Callers still on v0.23.0 or below are rejected by the minimum-version gate once this workflow ships. Reviewed by Cursor Bugbot for commit 6436bea. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Clean version bump to sei-agent-driver v0.23.1: the input default, the example in its description, MIN_DRIVER_VERSION, the floor comment (now five load-bearing releases, counted correctly) and both archive sha256 pins all move together, as the file's "one release, three places" rule requires. The rollout note covers callers that pin driver-version: v0.23.0, which will fail the new floor.
Findings: 0 blocking | 0 non-blocking | 0 posted inline
Blockers
- None at the file/PR level.
Non-blocking
- None at the file/PR level.
## Summary Bumps the seidroid workflows to uci [v0.0.27](https://github.com/sei-protocol/uci/releases/tag/v0.0.27). - Reviews run on sei-agent-driver v0.23.1. It fixes the intermittent no-verdict reviews (exit 5, "the message carries no fenced json block"). The final message can reach the server after the edge that ends the turn. v0.23.0 reads the session once at that edge, so it takes an earlier progress note as the reply and fails the review. v0.23.1 re-reads for up to 10 s until the reply is a finished answer (#485). ## Change - `seidroid.yml`: the three jobs move from v0.0.26 (`0dc48cf`) to v0.0.27 (`a3e422d`). - `ai-assist.yml`: `uses:` and `uci-ref` move from v0.0.26 to v0.0.27. Between those versions only `seidroid-review.yml` changed (sei-protocol/uci#124), so `ai-assistant.yml` and its inputs are unchanged. ## Verification `actionlint` on the changed files: clean. The same bump ran on sei-chain first (sei-protocol/sei-chain#4532). Its seidroid review installed the pinned v0.23.1 binary and reached a verdict. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
## Summary Bumps the seidroid workflows to uci [v0.0.27](https://github.com/sei-protocol/uci/releases/tag/v0.0.27). - Reviews run on sei-agent-driver v0.23.1. It fixes the intermittent no-verdict reviews (exit 5, "the message carries no fenced json block"). The final message can reach the server after the edge that ends the turn. v0.23.0 reads the session once at that edge, so it takes an earlier progress note as the reply and fails the review. v0.23.1 re-reads for up to 10 s until the reply is a finished answer (sei-protocol/sei-internal-skills#485). - sei-protocol#4505 failed this way on all four reviews today. On the last one, the driver took "Self-destruct and precompile warming check out in the fork. Checking whether any trace path sets hooks…" as the reply. ## Change - `seidroid.yml`: the three jobs move from v0.0.26 (`0dc48cf`) to v0.0.27 (`a3e422d`). - `ai-assist.yml`: `uses:` and `uci-ref` move from v0.0.26 to v0.0.27. Between those versions only `seidroid-review.yml` changed (sei-protocol/uci#124), so `ai-assistant.yml` and its inputs are unchanged. ## Verification `actionlint` on both files: clean. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Summary
Drives sei-agent-driver v0.23.1. It fixes the intermittent seidroid no-verdict reviews (exit 5, "the message carries no fenced json block"). On the claude-native harness, the final message can reach the Omnigent server after the turn-end edge. v0.23.0 reads the session once at that edge. It takes an earlier progress note, or no reply, as the answer, and fails the review. v0.23.1 re-reads for up to 10 s until the reply is a finished answer (sei-protocol/sei-internal-skills#485).
sei-chain#4505 failed this way three times today. Each time, the driver took a progress note such as "Diff fully read (7629 lines). Now checking the changed code against the tree…" as the reply.
Change
One release in the three places the floor comment names:
driver-versiondefault:v0.23.0→v0.23.1. The input description's example version moves with it.MIN_DRIVER_VERSION:v0.23.0→v0.23.1. The floor comment adds v0.23.1 to its load-bearing releases.DRIVER_SHA256_LINUX_AMD64andDRIVER_SHA256_LINUX_ARM64: the v0.23.1 archives.Verification
Rollout
After merge: tag uci
v0.0.27on main. Then sei-chain moves its uci pin inseidroid.yml. A caller that passesdriver-version: v0.23.0fails the floor after it takes v0.0.27. Drop the input, or move it tov0.23.1.🤖 Generated with Claude Code