Help Center

Sharing Sessions from Claude, ChatGPT, the API and the CLI

Read the sessions other people shared with you, and share your own, from an AI assistant, your own code, or the terminal.

Sessions people share with you in Wave aren't stuck in the Wave app. Claude, ChatGPT, any other connected AI assistant, the Wave Developer API, and the Wave CLI can all read them. They can also share your own sessions and manage who has access, the same way you would from the share sheet.

Everything here acts as you. An assistant or a token can only reach sessions you could open yourself, and anything it shares is read-only for the people who get it.

What you can do

With sessions shared with you:

  • List them, newest first, with who shared each one.
  • Read the summary, the transcript with speakers, and the action items.
  • Get the audio or video.

With your own sessions:

  • Create an invite link, or email invites to up to 10 people at once.
  • See who has access and which email invites nobody has opened yet.
  • Cancel a pending invite, remove one person, or reset the link and remove everyone.

In Claude, ChatGPT, and other AI assistants

Once Wave is connected (Claude, ChatGPT, or any other MCP tool), ask in plain words. Behind the scenes the assistant uses four sharing tools: one lists sessions shared with you (list_shared_sessions), one shows who has access to a session of yours (list_session_access), one shares a session (share_session), and one removes access (unshare_session). To read a shared session it uses the same tools it uses for your own, pointed at the owner's copy.

Try asking:

  • "What meetings have people shared with me this week?"
  • "Summarize the meeting Sam shared with me and list the action items."
  • "Share yesterday's standup with maria@example.com."
  • "Who has access to the Q3 planning session? Remove anyone outside our company."

Sharing gives other people access to your recording, so the assistant confirms before it shares a session or removes someone, unless you've clearly asked it to. Read what it's about to do before you say yes.

In ChatGPT, sharing is a write action, so it follows the same rule as saving action items: it works in managed workspaces, and personal plans can read shared sessions but not share.

With the Developer API

Reading shared sessions uses the permissions you already know: Read Sessions, Read Transcripts, and Access Media. Sharing your own sessions needs a token with the new Share Sessions & Manage Access permission. Create or update a token on the Developer API page.

WhatRoute
List sessions shared with youGET /v1/shared-sessions
Read oneGET /v1/shared-sessions/{owner_id}/{id}
Its transcript, action items, or media.../transcript, .../action-items, .../media
Include shared ones in your session listGET /v1/sessions?include=shared
See who has accessGET /v1/sessions/{id}/sharing
Create an invite linkPOST /v1/sessions/{id}/sharing/link
Email invitesPOST /v1/sessions/{id}/sharing/invites
Cancel a pending inviteDELETE /v1/sessions/{id}/sharing/invites
Remove one personDELETE /v1/sessions/{id}/sharing/people/{recipient_id}
Reset the linkPOST /v1/sessions/{id}/sharing/link/reset

Request and response shapes are in the API reference.

With the Wave CLI

Update to the latest Wave CLI (npm install -g @waveai/cli), then:

wave shared list                                   # sessions shared with you
wave shared get <owner_id> <session_id>            # summary and details
wave shared transcript <owner_id> <session_id> --speakers
wave sessions share <id> --email maria@example.com # email an invite
wave sessions share <id>                           # print an invite link
wave sessions access <id>                          # who has access
wave sessions unshare <id> --email maria@example.com

wave sessions list --include-shared mixes shared sessions into your list and marks each with who shared it.

Limits worth knowing

  • Invite links last 30 days. Access someone has already claimed doesn't expire.
  • Up to 10 email addresses per request. Send again for more.
  • Up to 250 people per session.
  • To email invites, the email on your Wave account has to be verified. Otherwise the request is refused with a message saying so.
  • Shared sessions are read-only. An assistant or token can't edit them, change their action items, or file them into your folders.
  • Search doesn't cover shared sessions. Semantic search only looks at your own library, so ask for the shared list first and read the session from there.
  • No notifications to your code yet. Nothing tells a webhook or the event feed when someone shares a session with you. List shared sessions to check.

FAQ

Was this article helpful?

Still need help?

Email support

On this page

What you can doIn Claude, ChatGPT, and other AI assistantsWith the Developer APIWith the Wave CLILimits worth knowingFAQRelated