Personal and team sharing make Claude Code, Codex, other CLI-capable agents, and MCP clients useful across shared work, not just your personal history.
When someone shares a source, repository, session, context, or folder with you, the readable scope becomes available through MCP and the CLI. Agents can inspect shared roots, traverse collaborative context folders, search one person's sources, read the matching transcript or context, and cite where the answer came from. Repository/session exclusions and folder overrides are enforced before results are returned.
Common workflows:
- Debug from someone else's session — search a collaborator's shared Claude Code or Codex sessions for the error, migration, or release blocker they already investigated
- Get project continuity — ask an agent to summarize what changed across shared sessions before you pick up the work
- Build launch or customer briefs — combine your own contexts with shared research, support notes, and implementation sessions, then save the result in an Editor shared folder
- Collaborate through agents — on a shared or collaboration-enrolled context, let an MCP or CLI agent update the same synchronized document that people are editing in Nessie
- Review decision history — reconstruct why an approach was chosen by searching shared conversations across owners and integrations
MCP flow:
- Call
nessie_integration_listto discover direct and team-shared roots; callnessie_team_listonly when you need team membership or team-derived resources - Call
nessie_lsto browse roots; open the Contexts root to find collaborative folders - Search with
nessie_grep, usingowner,parentId, orreposto preserve the requested scope - Read the matching node with
nessie_cat,nessie_head, ornessie_tail - Use
nessie_replace_lines,nessie_sed,nessie_tee, ornessie_mvonly where the authenticated user has Editor access
CLI flow:
- Run
nessie integration listto discover direct and team-shared roots; usenessie team listonly for team-derived access - Run
nessie lsto browse readable roots; open the Contexts root for collaborative folders - Search a shared scope with
nessie grep "query"--owner - Read the matching node or transcript with
nessie cat - Create, move, or edit caller-owned contexts only in folders where the user has Editor access
CLI and MCP can use access already granted to the authenticated user. The CLI can also create or revoke private grants with
nessie sharing; MCP grant management is not yet available.Shared workflows require Cloud Sync. If a shared source does not appear in MCP or CLI results, check that Cloud Sync is enabled and finished syncing on the source owner's device.