Skip to content

Team group: assign PRs to members’ Bots (GitHub truth, group as write entry) #427

Open

Description

@hsliuustc0106

Child of #149. Related: #349, #55, #408, #51.

Scenario (first slice)

Several people’s Bots join one team group. A team admin assigns a PR to someone’s Bot from the group. People should not have to edit GitHub by hand.

Design choice: C′

  • Source of truth: GitHub PR assignee / labels.
  • Write entry: the team group. Admin says “give PR #N to @person’s Bot” → FlyBot updates GitHub assignee/label, then that Bot may work.
  • Read path: Bots and the group follow GitHub state (webhook preferred over poll). Group also broadcasts progress and the conclusion.
  • Not chosen for Now: chat-as-board only (A), or a separate task-card system as truth (B).

Acceptance

  1. Admin assigns in the group → PR on GitHub shows the matching assignee (or agreed label).
  2. Only the assigned person’s Bot picks up that PR; others do not race it.
  3. Reassign in the group updates GitHub and the previous Bot stops / unlocks ([Team] Recover task handoffs without duplicate work #55 / RFC: multi-Bot × GitHub — PR budget, task lock, decision card (not a new Git) #408).
  4. Progress and final conclusion are visible in the group thread; GitHub remains the audit trail for who owns the PR.

Out of scope

Full Magpie-style routing UI; personal-edition complexity; replacing Git.

Open questions

  1. Assignee = human GitHub user, or a Bot identity / label such as bot:<name>?
  2. Who may reassign: team admin only, or also the current owner?
  3. Stuck Bot: timeout then auto-release, or admin-only reclaim?

Process: OpenCode + Codex review.

Activity

  1. added
    enhancementNew feature or request
    area:socialFriends, invites, grants, Bot Social
    area:automationScheduled tasks and automation
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    on Oct 19, 2026
  2. Birfy commented on Oct 20, 2026

    @Birfy
    Collaborator

    Triage: needs-human because this is team-via-groups work — it needs the multi-human team mode (#16 closed as Option B; #149, #51 and #57 are still open and not shipped).

    Per AGENTS.md, team-via-groups items wait for the owner's go-ahead and cannot be agent-ready. Nothing is implemented here yet.

  3. Birfy commented on Nov 6, 2026

    @Birfy
    Collaborator

    Written-by: Chief

    #149 的子单。team mode 按 docs/subsystems/team.md 仍是 disabled,解锁口子卡在 #58 的两真人试点;在那之前本单只挂着——不问、不动、不标 agent-ready。

  4. Birfy commented on Nov 14, 2026

    @Birfy
    Collaborator

    Written-by: Chief

    team-via-groups 簇:按 docs/subsystems/team.md,team mode 仍是 disabled,解锁口子卡在 #58 的两真人试点。本轮不动工、不提问;整簇(#51、#149、#427、#55、#56、#57)的状态统一记在 #58 的 2026-11-13 那条上。

  5. Birfy commented on Nov 19, 2026

    @Birfy
    Collaborator

    Written-by: Chief

    现状:team mode 在 docs/subsystems/team.md 里默认 disabled,仓库里没有解锁点;本条属于 Team 簇(#51 #55 #56 #57 #58 #149 #427),簇内七条共享同一个前置条件。

    决定(2026-11-19,Chief 自决,不再回来问 owner):整簇冻结到解锁点。解锁点写死为三条同时成立:① docs/subsystems/team.md 里的 team 开关有真实入口;② 双人 pilot(#58)有一份可复现的验收记录;③ 权限面(#51 的 per-Bot grants)已经在 main 上。

    在那之前:不派实现、不切刀、不重复提问;本簇的 needs-human 标签保留,等解锁点到了再逐条转 agent-ready。

    (本条是 #149 的子项,冻结理由同上。)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:automationScheduled tasks and automationarea:socialFriends, invites, grants, Bot SocialenhancementNew feature or requestneeds-humanThe agent loop stopped; a person must decide (reason in the last comment)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions