Add feature to share chat with anyone in the tenant - #859
Merged
Merged
Conversation
chiragjn
requested review from
bhaveshpatel640,
debajyoti-truefoundry,
heerambavi1998,
sr07asthana and
thesujai
as code owners
September 23, 2026 11:24
🦋 Changeset detectedLatest commit: bfe4d9f The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
chiragjn
marked this pull request as draft
September 23, 2026 11:24
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
chiragjn
marked this pull request as ready for review
September 24, 2026 06:21
chiragjn
force-pushed
the
cj-add-tenant-level-share-session
branch
from
September 24, 2026 06:21
6fac847 to
a6b56a5
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a6b56a5. Configure here.
heerambavi1998
approved these changes
Sep 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes AGE-2357
Note
Medium Risk
Expands who can read session content within a tenant when
sharedis enabled; write/stream/download paths are intentionally unchanged but mis-set sharing could expose sensitive transcripts.Overview
Adds a
sharedflag on agent sessions so the owner can expose read-only conversation access to anyone in the tenant.Owners set
sharedvia session PATCH (defaults to false on create; existing rows stay private after migration). When shared is true, GET session, list/get turns, and list session/turn events succeed for any tenant subject—not only the creator or named-agent managers. Updates, turn creation, subscribe, and sandbox file download still require the original access rules (creator-only where applicable today).Persistence spans in-memory, Postgres, and SQLite stores; OpenAPI, route docs, and TS/Python SDKs are regenerated to surface
sharedonSessionandUpdateSessionRequest.Reviewed by Cursor Bugbot for commit 29e3108. Bugbot is set up for automated code reviews on this repo. Configure here.