Repository navigation
crew: take the issues handed to it on the Rinai board - #1
Merged
Merged
Conversation
A crew label on a Rinai issue hands it to this machine's crew. The daemon pulls once a minute; nothing on the web reaches it. It takes an open labelled issue only when the gh-signed-in user applied the label (GitHub's issue events), and only once, a failed plan included. The label is the go: the tickets start when planned. Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
An auto-started brief is the body and the hander's own comments, so a stranger's comment never runs unread. A take reserves its issue before the first await. Taken issues are counted per board, not per project, and a paused project is skipped. Taking the crew label off drops the handed goal's unstarted tickets. Handed is logged after the take succeeds, a failure once. The labeller is read only for issues not already on the rail, and from the last events page too. me() is cached with the token it was read with. Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
The owner's call after the second kumi review: the label brings the issue in, a human starts it. Its title, body and comments are anyone's words, so nothing auto-runs, and take back only ever drops drafts, synchronously, with no worktree to clean. A capped board read throws instead of looking like every label came off. The labeller is found walking back from the newest events page. One board failing no longer skips the others; cards() marks the rail per board like take does; the event log is read only when an unlabelled issue still has drafts. Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
Third kumi review. A taken-back goal is marked dropped once nothing of it is left, so the issue is not locked out: `yap take` or the label again brings it back. Handed goals carry a flag instead of being found in the event log. Who labelled an issue is cached per issue against its updated_at. A board that can't be read whole is logged once until it reads again. The label matches whatever its case, and an issue a `yap take` is holding is skipped, not logged as a failure. Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
# Conflicts: # src/crew.check.ts # src/server.ts
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.
The owner wants to hand a task to the crew from the Rinai board. A two-model council (Opus and GPT Sol) said the board must never be able to reach the laptop. So this is a pull: Rinai puts a
crewlabel on the issue (noxire-dev/issues#239), and the daemon goes looking for it.Crew.watchreads each registered project's board for open issues labelledcrew. It's wired inserver.ts.handed(), which returns those cards and who last applied the label (GitHub's issue events, the latestlabeled), andme(), the loginghis signed in as.yap takeis the retry.take(..., go)starts the tickets once they're planned. Reporting back is unchanged: claim, comment, In review or Blocked.Checked:
bun src/crew.check.tspasses (crew ok). The new check fails when the actor check is removed, and when the guard against retaking a failed issue is removed.tsc --noEmitis clean.me()returns noxire-dev, andhanded()finds issues-scratch #35 labelled by noxire-dev.I haven't run a crew end to end from a label.
Ceiling, noted in the code: only an issue's first 100 events are read. On a busier issue the label's actor isn't found, and it waits for
yap take.Branched from main at 8f733b6. The kumi session agreed to it being built here.
https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
Created with Claude Opus 5.5 in Claude Code.