To let teammates follow a local Claude Code conversation without controlling your computer, use a read-only sharing workflow. In Agent.Space, the documented Mac App workflow shares conversations from a selected folder into a Workspace while you continue operating Claude Code locally.
First check whether you want someone to watch, continue the task, or operate the computer. Those are different permissions and different workflows. This guide covers read-only viewing, with links to the other paths.
Choose the right kind of sharing
Claude's official cloud-session documentation says recipients see the latest state when opening the link, but their view does not update in real time. Sharing options also depend on the account type. Do not apply those cloud-session instructions to an arbitrary local terminal conversation.
Share a local conversation through the Mac App
The steps below follow the Agent.Space computer and cloud manual, rather than a hands-on account test. Check that your installed App exposes conversation sharing before using it for a real project.
- Check the destination Workspace. Review who belongs to it. Treat sharing into a Workspace as sharing with its members, not just the person you plan to notify.
- Find the project folder in the Mac App's Workspace folder list. Select the folder containing the local work you intend to share, not a broader directory containing unrelated projects.
- Enable conversation sharing for that folder. New local conversations can appear in the Workspace. An older conversation may also sync when you continue it locally; this is not limited to conversations created after enabling sharing.
- Continue the conversation locally and check its web view. The mirrored conversation is labeled “Synced from computer, view only.” It has no composer for continuing the task.
- Check the content and update time. Confirm that the intended conversation appears and that recent activity is reflected. An offline computer can leave visible history that is no longer current progress.
No composer is expected for a read-only mirror. Changing a member's Workspace role does not turn it into a remotely controllable conversation.
What about images and private information?
The current manual describes image sharing for newly enabled folders. Older shared folders may show “Images aren't shared” and require the computer owner to confirm “Share Images…”. Check thumbnails and transfer messages: synced text does not prove that every image arrived.
Before enabling sharing, inspect the conversation for credentials, private customer details, and material your teammates should not see. Also check what screenshots or other images reveal. Do not assume a conversation mirror is a complete replica of every local log or tool output.
Before sharing sensitive work, confirm how the current App stops future sharing and how previously synced history is handled. Stopping updates and deleting existing records are different actions; do not assume one performs the other.
If a teammate needs to continue the task
Read-only viewing helps someone understand the work. Continuing it also requires an appropriate execution environment, permissions, files, and a useful handoff.
Write down the goal, current code or file version, checks already performed, and unresolved questions. If using conversation import, remember that it transfers history, not the local project directory. Supply the required files and have the Agent check which ones exist before continuing. See importing Codex and Claude Code conversations.
For access decisions, use the Workspace roles guide. Do not share personal credentials to work around a missing permission or confuse permission to read a conversation with permission to use someone else's subscription.
Try it with a non-sensitive conversation first
Choose a small local task with no private data. Check the destination members, enable the documented sharing option, and verify the read-only result and update time. If your App does not show the option, check the current manual and App version rather than assuming a different sharing command does the same job.
Want teammates to follow your local Claude Code work without giving them control of your computer? Use Agent.Space's read-only conversation sharing. Follow the computer and sharing instructions, enable sharing for a non-sensitive folder conversation in the Mac App, then open your Agent.Space Workspace to verify what members can see. Keep execution and personal credentials on the owner's side; this is not remote control or shared subscription access.