Skip to content

feat: share new chats with the organization, groups, or users - #42

Open
bpmct wants to merge 3 commits into
mainfrom
feat/share-with-organization
Open

feat: share new chats with the organization, groups, or users#42
bpmct wants to merge 3 commits into
mainfrom
feat/share-with-organization

Conversation

@bpmct

@bpmct bpmct commented Sep 11, 2026

Copy link
Copy Markdown
Member

Chats created by background workflows are owned by the bot token, so the link they post answers "Chat not found" for everyone else. New share-with-organization, share-with-groups, and share-with-users inputs (all off by default) grant read access on a newly created chat, so people can follow the agent's reasoning, not just its verdict. First use is doc-check, where the docs team wants to open a review and see how it got there.

Generated by Coder Agents on behalf of @bpmct.

Chats are owned by the coder-token holder, so the chat-url the action
posts answers "Chat not found" for everyone else. share-with-organization
grants the chat's organization read access on creation, off by default.
One sharing module resolves the share-with-* inputs to the UUIDs the ACL
API requires and sends a single PATCH. Names resolve through the users
and groups endpoints, UUIDs pass through, and the token owner is dropped
because the API rejects a self-share.
@bpmct bpmct changed the title feat: share a new chat with its organization on request feat: share new chats with the organization, groups, or users Sep 11, 2026
@bpmct
bpmct requested a review from mafredri September 11, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant