Every connected integration can be shared as a whole. For example, you can share an entire ChatGPT, Claude, Gemini, Perplexity, or Manus integration — this is not limited to coding-agent sources. You can also share one individual conversation or session from any integration without sharing everything else in it.
Only coding-agent integrations add a repository-level option. For sources such as Claude Code, Codex, OpenCode, Cursor, Pi, and Antigravity, you can share selected repositories instead of the entire integration.
| Scope | Available for | What becomes readable |
|---|---|---|
| Whole integration | Every integration | All synced conversations or sessions in that connected account or source |
| Selected repositories | Coding-agent integrations | Sessions associated with only the repositories you select |
| Individual session | Every integration | One conversation or agent session; its parent integration and sibling sessions stay private |
Use the narrowest scope that matches the work you want another person or team to see.
Share a whole integration
- Open the integration's Share control in Library
- Choose the whole integration
- Select Personal access for one person or choose a team audience
- Save
Share selected repositories from a coding-agent integration
- Open the coding integration's Share control, or open Settings → Teams when adding it to a team
- Expand the source to see its repositories
- Select the repositories you want to share
- Choose a personal or team audience and save
Share one session from any integration
- In Library, right-click any conversation and choose Share; alternatively, open the conversation or agent session
- If you opened it, click Private or Share
- Add a personal or team audience
- Copy the private link and send it to the recipient
Manage from the CLI
The Nessie CLI can inspect, add, change, and remove private grants for whole integrations, selected coding-agent repositories, and individual sessions. For example:
nessie sharing add— share a whole integration with a team--team --audience everyone nessie sharing add— share selected coding-agent repositories--team --scope repos --repo github.com/org/repo nessie sharing add— share one session directly outside a team--audience user --email person@example.com
Use nessie sharing get to inspect grants and nessie sharing remove to revoke them. See the CLI reference for the complete audience, scope, and removal options.
What happens in each scenario
| Starting share | Action | Result |
|---|---|---|
| Whole integration | Unshare one repo | That repo becomes an exception. Other repos stay shared, and repos added later still inherit the integration share. |
| Selected repos | Unshare one repo | The selected set narrows. If it was the last selected repo, that audience loses the integration grant entirely. |
| Whole integration or repo | Unshare one session | Only that session is excluded. Its parent and sibling sessions stay shared. |
| Excluded repo or session | Share it again | The exception is cleared or a direct grant restores that item, without exposing unrelated siblings. |
| Private integration | Share one session | That session becomes readable on its own; the parent integration and its other sessions remain private. |
Repo and session access is additive across personal, team, and parent grants. Removing one grant does not make an item private when another grant still covers it.
Recipients and their agents can search and read the resulting session scope through MCP or the CLI with owner and access-path provenance. A directly shared session may appear as a transcript root rather than an integration root.
In the CLI and MCP, you can scope search to specific repos. From a coding session, nessie grep "query" --repo . restricts results to the current git repo; agents can also pass canonical repo keys to narrow a search to shared repos.