You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Team mode M2: Private Bots, per-member Tob, per-member Activity and push #4141
M2 wire contract (agreed before parallel work; Claude = UI, Codex = logic)
Stacked on M1 (#4163). Independent of M3; when M3 lands, Bot creation is additionally gated by bots.create.
Ownership
PersonaBots gain owner_human_id (existing Bots migrate to local-human). In M2 every member Bot is private: only its owner (and the Host Owner, for administration in Bot settings only, not content) can list, open, DM, edit or delete it. Visibility roles/shared is M7.
Bot summaries on the wire gain ownerHumanId and owner: boolean (the caller owns it). The Owner's roster still lists only the Owner's own Bots by default.
A member Bot joins only Channels its owner belongs to; group membership and @mentions of a private Bot by anyone else are refused (bot-not-found — do not reveal existence).
Per-member Tob
Each member gets a private Tob on first successful sign-in (idempotent). Tob acts with that member's authority: it sees only that member's Bots, Channels and Activity, and its management tools refuse anything the member could not do through the Client. Tob's Host-administration tools (models, plugins, Team mode, other members, IM apps, devices, data reset) are unavailable to member Tobs (permission-required).
Per-member Activity, read state and push
humanAttention*, activitySnapshot, followActivity, channelUnreadCounts are scoped to the calling Human; Owner attention never appears for a member (fixes the M1 audit finding on humanAttentionStatus).
Push and Live Activity delivery go only to devices whose grant belongs to the Human the item is for. M8 brings member phones; in M2 prove the routing with the Owner plus a member grant fixture.
Bot Inbox stays per Bot; Source Events already carry the speaking Human (M0).
Member allowlist additions (team/member-methods.ts): own-Bot methods (bot list/get/create/delete/rename/settings the Client calls for a DM Bot, botStop, botAttention, botSessionIds for own Bots), Bot DM open/send, humanAttention, humanAttentionStatus, humanAttentionDismiss, humanAttentionDismissAll, humanAttentionIgnore, humanAttentionSnooze, activitySnapshot, followActivity, onboarding (member-scoped), and the Bot creation path. Every Bot-addressed method checks ownership; list the exact names in member-methods.ts and the claim follow-up comment.
CLI: bots list|create|delete honour the caller (--as), bots show refuses another member's Bot with bot-not-found; activity list --as <member> shows only that member's items.
Client (Claude): member New menu offers Create Bot; member sidebar shows own Bots and own Tob; Activity rail works for members; Bot settings for a member Bot; removes M1's member-only Bot/Activity suppressions where M2 enables them; empty states for members; en + zh.
Tests: Bob cannot list, open, DM, mention or add Alice's private Bot (Client, --as, and a Bot tool call); Bob's Tob cannot read Alice's content; Activity counts per member; push routed only to the owner's devices.
Merged in #4166 (2d1747902). Each member has their own Tob and private Bots, invisible to other members and the Owner's sidebar through list, get, DM and CLI --as; bots.create gates creation; attention and push are per Human. Verified on a real isolated Host with Owner + two member browsers; CI green; 8 review findings fixed with regressions.
Amended after merge by the Bot access model on spec #4137 (2026-11-15): private Bots now follow their principal (read any Channel the principal can access; write only where added; anyone in that Channel may @ them; only the principal may DM them); member Tobs are no longer created automatically (M13 #4187). Implementation of the changes lands in M13 and M7.
Activity
DoodleBears commentedon Nov 13, 2026
Agent work claim
claude/local/74a5ee4a-f6fe-4aab-870f-5e465b0b8474(not a DSH Session); Codex thread added once startedclaude/4141-private-bots(stacked onclaude/4140-team-sign-in, PR Team mode M1: members sign in over HTTPS and talk in public channels #4163; Codex sub-branchcodex/4141-logic)M2 wire contract (agreed before parallel work; Claude = UI, Codex = logic)
Stacked on M1 (#4163). Independent of M3; when M3 lands, Bot creation is additionally gated by
bots.create.Ownership
owner_human_id(existing Bots migrate tolocal-human). In M2 every member Bot isprivate: only its owner (and the Host Owner, for administration in Bot settings only, not content) can list, open, DM, edit or delete it. Visibilityroles/sharedis M7.ownerHumanIdandowner: boolean(the caller owns it). The Owner's roster still lists only the Owner's own Bots by default.bot-not-found— do not reveal existence).Per-member Tob
permission-required).Per-member Activity, read state and push
humanAttention*,activitySnapshot,followActivity,channelUnreadCountsare scoped to the calling Human; Owner attention never appears for a member (fixes the M1 audit finding onhumanAttentionStatus).Member allowlist additions (
team/member-methods.ts): own-Bot methods (bot list/get/create/delete/rename/settings the Client calls for a DM Bot,botStop,botAttention,botSessionIdsfor own Bots), Bot DM open/send,humanAttention,humanAttentionStatus,humanAttentionDismiss,humanAttentionDismissAll,humanAttentionIgnore,humanAttentionSnooze,activitySnapshot,followActivity,onboarding(member-scoped), and the Bot creation path. Every Bot-addressed method checks ownership; list the exact names inmember-methods.tsand the claim follow-up comment.CLI:
bots list|create|deletehonour the caller (--as),bots showrefuses another member's Bot withbot-not-found;activity list --as <member>shows only that member's items.Client (Claude): member New menu offers Create Bot; member sidebar shows own Bots and own Tob; Activity rail works for members; Bot settings for a member Bot; removes M1's member-only Bot/Activity suppressions where M2 enables them; empty states for members; en + zh.
Tests: Bob cannot list, open, DM, mention or add Alice's private Bot (Client,
--as, and a Bot tool call); Bob's Tob cannot read Alice's content; Activity counts per member; push routed only to the owner's devices.DoodleBears commentedon Nov 13, 2026
Codex logic task for this claim:
codex/local/01a1d729-cdcb-7e73-9369-c625a4e90635oncodex/4141-logic(gpt-6.1-sol, high).fix(client): offer members only a blank Bot to create
Preserve Owner bridge composition and close private Bot authority gaps
DoodleBears commentedon Nov 14, 2026
Outcome
Merged in #4166 (
2d1747902). Each member has their own Tob and private Bots, invisible to other members and the Owner's sidebar through list, get, DM and CLI--as;bots.creategates creation; attention and push are per Human. Verified on a real isolated Host with Owner + two member browsers; CI green; 8 review findings fixed with regressions.State: done. Claim released.
feat(client): members create Bots and see their Activity
Isolate private Bots, Tob management and Activity by Host member
Verify the explicit Bot administration argument in the RPC contract
Assert private report refusals in the Human context regression suite
Preserve live Registry delegates in member-scoped views
Attribute Group reply attention to the canonical speaking Human
Model DM membership in approval capacity fixtures
Cover every newly allowed member method and Activity frame for privacy
docs(changelog): add Team mode M2 fragment
Keep member Group reads separate from Owner management snapshots
Integrate private Bots with Host Roles and current Owner authority
Merge Codex M2 logic integrated with main (reviewed)
DoodleBears commentedon Nov 14, 2026
Amended after merge by the Bot access model on spec #4137 (2026-11-15): private Bots now follow their principal (read any Channel the principal can access; write only where added; anyone in that Channel may @ them; only the principal may DM them); member Tobs are no longer created automatically (M13 #4187). Implementation of the changes lands in M13 and M7.