Repository navigation
Open
10 / 1210 of 12 issues completedOpen
10 / 1210 of 12 issues completed
Copy link
Labels
feature:teamready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agentscope:hubParent coordination map or epic; not a standalone implementation sliceParent coordination map or epic; not a standalone implementation slice
Description
Parent
Spec #4137. Parallel to the Environment hub #4109, with no shared slices.
Goal
Deliver Team mode as thirteen runnable tracer bullets. Until M12 lands, Team mode is a trial with a plain isolation notice (scope amended 2026-11-14, research PR #4182). First complete M1, then obtain Human feedback before expanding.
Execution rules
- Work the unblocked frontier and respect existing claims. This hub coordinates; it is not an implementation slice.
- Every slice ships:
- public owner/CLI parity where contracts change
- behavior regression that proves refusals as well as successes
- real Host acceptance with the Owner and two members
- performance and lifecycle guards, with resource release
- Report Web, installed Desktop and mobile results separately.
- One implementation issue and one narrow PR per slice. Publishing these tickets authorises no merge or release.
- Design docs (ADR-0336,
docs/architecture/team-mode.md, glossary) are on branchclaude/stoic-euler-25n60k, not yet onmain.
Dependency map
| Slice | Issue | Blocked by |
|---|---|---|
| M0 | #4139 Thread explicit Human context through Host methods | None |
| M1 | #4140 A member signs in on the LAN and talks in a public Channel | #4139 |
| M2 | #4141 Private Bots, per-member Tob, per-member Activity and push | #4140 |
| M3 | #4142 Host Roles, permission catalog, member and device management | #4140 |
| M4 | #4143 Channel visibility, Channel admin settings and Human–Human DM | #4142 |
| M5 | #4144 Approval masking and routing | #4141, #4142 |
| M6 | #4145 Workspace roots and audience-contained grants | #4142 |
| M7 | #4150 Bot visibility and Role Policy | #4143, #4145 |
| M8 | #4146 Mobile invitation, sign-in and self-pairing | #4140 |
| M9 | #4147 Password lifecycle, disabling Team mode, offboarding | #4142 |
| M10 | #4148 Usage per member and role model allowlists | #4142 |
| M11 | #4149 Private-content access audit and member notice | #4142 |
| M12 | #4183 Bot execution confinement on Linux Hosts | #4145 |
The initial frontier is M0, then M1. After M1, M2, M3 and M8 can proceed in parallel.
Metadata
Metadata
Assignees
Labels
feature:teamready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agentscope:hubParent coordination map or epic; not a standalone implementation sliceParent coordination map or epic; not a standalone implementation slice
Activity
DoodleBears commentedon Nov 14, 2026
Human decision (2026-11-14): new slice M13 #4187 — the built-in Member role grants only
dm.humans(nobots.create,channels.create,models.use), and Tob is Host (Owner)-only by default: members get no Tob on sign-in; existing member Tobs on test Hosts are kept as ordinary private Bots. Members reach Bots through M7 shared visibility, so M7 #4150 moves up after M6. Order: M10 → M5 → M13 → M6 → M7/M11/M12.DoodleBears commentedon Nov 14, 2026
Human decisions (2026-11-14), recorded: M14 #4188 — inviting a member into a Channel grants access regardless of visibility (Bot audience from M7 still wins). M13 #4187 adds first-run guidance (empty state → Browse channels / shared Bots, also in a Team-mode remote Host tab). M7 #4150 adds a specific-members Bot audience. Order: M10 → M5 → M13 → M6 → M14 → M7 → M11/M12.
DoodleBears commentedon Nov 14, 2026
Bot access model confirmed by Vain (2026-11-15) and recorded on spec #4137 (comment 6879444946): Bots inherit from their principal; read any Channel the principal can access, write only where added; public/private only decides who may DM or add a Bot; no co-occupancy blocks or silenced state; audited private viewing never goes to Bots; Bot creation split into private/public permissions. Rewritten: M7 #4150, M13 #4187, M14 #4188; M2 #4141 amended. ADR-0336 text is not edited yet (needs Human review).
DoodleBears commentedon Nov 14, 2026
New slice M15 #4197: a kept Team mode security scenario suite with real LLM turns (Role Policy abuse in group and DM, conflicting roles, file access via tools and bash). Blocked by M7 and M12; required for every permission-affecting PR afterwards.
DoodleBears commentedon Nov 14, 2026
Added follow-up #4200: members manage Memory of their own Bots (found while verifying M6 #4193; Memory methods are currently denied to members). To be scheduled after M6.
DoodleBears commentedon Nov 14, 2026
Tracking the #4109 review follow-ups in #4201 (desktop member sign-in plus host-client package before M8; package-boundary lint; credential storage pending Vain's call; remote settings gating with #4198).
DoodleBears commentedon Nov 15, 2026
Queued after all milestones: #4222, the IM-style workspace pass (auto-join visible Channels, no Browse modal, per-user synced sections and pins).
DoodleBears commentedon Nov 15, 2026
Infrastructure before M7: #4225, named schema migrations so parallel branches stop colliding on generation numbers. M7 (#4150) stacks on it.