Repository navigation
Open
Labels
agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDsOne or more coding-agent tasks currently claim this issue; see claim comments for task IDsfeature:teamready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent
Description
Parent: hub #4138 (spec #4137 + Bot access amendment of 2026-11-15, ADR-0336). Blocked by: #4143 (merged), #4145.
Implements the Bot access model recorded on spec #4137 (2026-11-15). Replaces the earlier audience-containment design.
Behavior
- Principal. Every Bot has one principal (its owner). Its effective access = principal's access ∩ the principal's restrictions on it; the Owner and holders of all-Bots management may restrict any Bot further. It changes the moment the principal's access changes. Audited private-content viewing (M11) is never available to Bots.
- Read / in. A Bot can read any Channel its principal can access (subject to the "may join Channels I'm in" switch). It can write only in Channels it was added to. No silenced state.
- Visibility.
private(only the principal may DM it or add it) orpublicwith an audienceeveryone | roles(roleIds) | members(humanIds)(who may DM it and add it to Channels). Making a Bot public or widening its audience requires the create public Bots permission. Shrinking it shows a preview; afterwards outsiders' DMs are read-only and the Bot leaves Channels it no longer qualifies for. - Switches (per Bot, set by its principal): proactive DMs to its audience (members can opt out per Bot); may join Channels the principal is in (default on). Adding a Bot to a Channel requires the adder's
addBotsright there, the principal's access to that Channel, and the switch on. - Channels. Anyone in a Channel may @ a Bot that is in it. No co-occupancy block for sensitive Bots; whoever adds it decides.
- DMs. One DM per (Human, public Bot); the principal cannot read other Humans' DMs with it except via M11.
- Bot–Bot. Private Bots may message and delegate to public Bots their principal can reach; public Bots cannot proactively reach private Bots.
- Shared Bots' Memory lives in a shared space whose audience matches (M6), apart from the grantable files folder; public Bots are managed by their principal and holders of all-Bots management. Binding a Bot to an external IM App requires being its principal plus
bind-external-im. - Role Policy stays advisory (existing evaluator, given to the Bot with the speaking Human's identity and roles).
Acceptance
- A Bot never reads a Channel its principal cannot; it loses read and write the moment the principal is removed or loses the granting role.
- Only allowed people can DM or add a Bot, per its visibility and switches; refusals are coded and shown in UI and CLI.
- Each Human's DM with a public Bot is private to them.
- A private Bot can delegate to a public Bot; the reverse is refused.
- Making a Bot public without the permission is refused.
- CLI
--asparity; real-Host verification with two members.
Metadata
Metadata
Assignees
Labels
agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDsOne or more coding-agent tasks currently claim this issue; see claim comments for task IDsfeature:teamready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agent
Activity
DoodleBears commentedon Nov 14, 2026
Scope addition (Vain, 2026-11-14): Bot visibility also supports specific members (
{ kind: 'members', humanIds }), alongside roles and shared-with-everyone, matching the shared-space audience options from M6, so an owner can choose exactly which members may DM a Bot or have it join Channels with them.DoodleBears commentedon Nov 14, 2026
Human decisions (Vain, 2026-11-15) for Role Policy:
[Bob · Finance, Intern]). A role's full policy text is attached to the envelope of the first message in the Session where that role appears; a changed policy is re-attached (with its revision) on the next message carrying that role, and the latest revision wins. A Bot tool returns a named Human's roles and the resolved Allow/Deny for a policy topic, for on-demand checks (especially in group Channels).DoodleBears commentedon Nov 15, 2026
Agent work claim
codex/local/01a1e0ec-da95-72e1-b965-20fe01d14b28(not a DSH Session)claude/4150-bot-visibilityfix(team): preserve proactive DMs to the Bot principal
DoodleBears commentedon Nov 15, 2026
Agent work outcome
codex/local/01a1e0ec-da95-72e1-b965-20fe01d14b28(Codex implementation sub-agent).claude/4150-bot-visibilityin feat(team): Bot visibility, shared Bots and Role Policy (M7) #4258.requireProactiveexempts the current persisted owner. Both explicit sends andstartHumanDminherit the exemption, including after transfer. Non-principal audience/switch/opt-out checks remain enforced.--maxWorkers=2): 748 files passed, 5 skipped; 8,137 tests passed, 23 skipped, zero failures. The known local simultaneous-retirement failure did not reproduce.DoodleBears commentedon Nov 15, 2026
Agent work claim
codex/local/01a1e126-1b1c-7b13-a959-717240df07d0(not a DSH Session)claude/4150-bot-visibilityfix(client): keep Bot access and Role Policy conflicts in step with t…
fix(client): apply each Bot switch result to its own switch
DoodleBears commentedon Nov 15, 2026
Agent work outcome
codex/local/01a1e126-1b1c-7b13-a959-717240df07d0(Codex implementation sub-agent).841a32e1a3dd5e54139e9ffa08ec5dc1360f5c98, branchclaude/4150-bot-visibility; committed with HUSKY=0 and explicit paths only. No push.fix(team): enforce M7 participant and speaker policy boundaries
DoodleBears commentedon Nov 15, 2026
Agent work claim
codex/local/01a1e194-9964-7e61-80d0-476b88e05a48(not a DSH Session)claude/4150-bot-visibilityDoodleBears commentedon Nov 15, 2026
Agent work outcome
codex/local/01a1e194-9964-7e61-80d0-476b88e05a48(Codex implementation sub-agent).4c0af8e1f614d2ee0c75d373a84ff403ab227584; branchclaude/4150-bot-visibility. Committed with HUSKY=0 and explicit paths, required trailers included. No push; PR feat(team): Bot visibility, shared Bots and Role Policy (M7) #4258 remains at 841a32e.fix(team): preserve participant access across runtime and DM actions