Repository navigation
fix(opencode-claimant): post the launch agent-note via gh (#6257) - #6271
Conversation
…ueue signal Every launch in the first live fires recorded a spurious agent-note failure: post_agent_note shelled to repo-queue signal --worker opencode-claimant --kind agent-note:v1, but signal is the queue-poke verb and rejects --worker - it was never a note path. The note is prompt.md step 4e: a gh comment on the tasks issue/PR carrying the agent-note:v1 marker (the format the launch driver used for the first 29 binds). post_agent_note now parses the ref from the task dedupe key, resolves the repo from the queue, and posts via gh issue/pr comment; a task with no ref is a quiet no-op. poll.py and claimant.pys candidate records now carry dedupe_key + title so the ref survives discovery (previously only progress.issue_number, which handoffs never set - always null).
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. |
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
Fourth step of the #6257 binding-rate fix. The launches themselves worked after #6263/#6268/#6270 (26 tasks bound across three verification fires), but every launch recorded a spurious "agent note failed": post_agent_note shelled to
repo-queue signal --worker ... --kind agent-note:v1. signal is the queue-poke verb (bundle continuation), rejects --worker in that position, and was never a note path.The note is prompt.md step 4e: a gh comment on the task issue/PR carrying the agent-note:v1 marker - the format the ad-hoc launch driver used for the first 29 binds. Now: ref parsed from the task dedupe key tail (issue:N / pr:N), repo resolved from the queue, posted via gh issue/pr comment with the note file written under the claimant state dir (same as the driver). No ref = quiet no-op, not a failure.
poll.py + claimant.py candidate records now carry dedupe_key + title (the note needs them; progress.issue_number, the previous source, is never set by handoffs and was always null).
Proven live before merge: a verification fire launched 9 tasks with zero note failures; note-10460.md written by the patched code and the matching agent-note:v1 comment with the exact bound session id read back from issue #6164 via the API.
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.Summary by CodeRabbit