Turn any 100xprompt session into a shareable link. The prompts, 100xprompt’s reasoning, the commands it ran, and the changes it made all travel with it - a teammate opens the link and sees the full story in their browser, no install required. To move a session between machines or keep a permanent copy, export it to a file and import it anywhere. Good sessions are worth keeping. Sharing turns them into shared knowledge: onboarding walkthroughs, reproducible bug investigations, and reviewable records of exactly how a change was made.

​
Overview

Sharing publishes a read-only view of a session to a link. Anyone with the link can open it in a browser and scroll through the conversation and the work 100xprompt performed - but they cannot type into your session or change anything.
A shared session stays up to date as the session progresses. Viewers always see a read-only copy - sharing never grants anyone the ability to run commands or edit your files.

​
Choose a sharing mode

The share setting in your 100xprompt.json controls how sharing behaves: whether new sessions become links automatically, only when you ask, or never.
ModeValueBehavior
Manual"manual"Sessions stay private until you explicitly share one. This is the safe default for most teams.
Automatic"auto"Every new session is shared as soon as it’s created and updates as it runs. Best for open, fully collaborative environments.
Disabled"disabled"Sharing is turned off entirely. The share command is unavailable and no session can be published. Ideal for locked-down or sensitive projects.
{
  "$schema": "https://100xprompt.com/config.json",
  "share": "manual"
}
When sharing is set to disabled, attempting to share a session is refused - a strong guarantee for regulated or confidential work.

​
Share a session

Suppose a teammate needs to see how you fixed a tricky bug. Sharing takes one action and gives you a link on your clipboard, ready to paste into chat, a ticket, or a pull request.
1

Open the session you want to share

Use any session - the one you’re working in now or an earlier one you’re revisiting.
2

Run the share command

Type /share in the prompt, or trigger Share session from the command menu. The link is created and copied to your clipboard automatically.
3

Send the link

Paste it wherever your team collaborates. Recipients open it in a browser and immediately see the conversation and changes - no account or install needed.
4

Keep working

As you continue the session, the shared view stays current, so teammates always see the latest state.
Tips:
  • Share a session on a pull request to give reviewers the full context behind a change: what you asked, how 100xprompt approached it, and every command it ran.
  • The link updates as you keep working, so paste it once and reviewers always see the latest state.

​
Stop sharing

When a session no longer needs to be public, unshare it. This deactivates the link so it can no longer be opened.
1

Open the shared session

Return to the session whose link you want to retire.
2

Run the unshare command

Type /unshare, or trigger Unshare session from the command menu. The link is removed and the session becomes private again.
Sharing publishes session content to a link. While a session is shared, anyone who has the link can read it - including prompts, agent output, file changes, and command results. A link is not password protected, so treat it as public.Before anything is published, 100xprompt scans the content and redacts high-confidence secrets - API keys, tokens, private keys, and similar credentials - so common secret shapes are stripped automatically. Treat this as a safety net, not a guarantee: it will not catch proprietary data, customer information, or private business logic. Before you share, make sure the session contains nothing you wouldn’t want public. Prefer manual mode so nothing is published by accident, and use disabled mode for confidential projects. Unsharing retires a link, so stop sharing as soon as a session no longer needs to be visible.

​
Export and import a session

Suppose you need to move a session to another machine, or keep it without publishing anything to a link. Export writes a session - its conversation and the work performed - to a portable JSON file. Import reads that file back in. Use them to move work between machines, hand a session to a colleague as a file, or archive a completed piece of work.
1

Export a session to a file

Run the export command and redirect it to a file:
100xprompt export > session.json
Omit the session id to pick from a list of recent sessions, or pass one directly:
100xprompt export <sessionID> > session.json
2

Move or archive the file

Copy session.json to another machine, attach it to a ticket, or store it alongside your project records. It’s a self-contained snapshot.
3

Import it anywhere

Bring the session into 100xprompt on any machine:
100xprompt import session.json
The session appears in your list, ready to read, reference, or continue.
4

Import from a share link (optional)

You can also import directly from a share link - a quick way to pull a shared session into your own environment:
100xprompt import https://<share-link>
Export and import are file-based and work entirely offline, making them the right choice for air-gapped environments, long-term archival, and moving work between machines without publishing anything to a link.

​
Sharing vs. export at a glance

NeedUseResult
Let a teammate view a session in their browserShareA live, read-only link
Retire a link when it’s no longer neededUnshareLink deactivated
Move a session to another machineExport → ImportA portable JSON file
Keep a permanent, offline copyExportAn archived JSON snapshot
Pull a shared session into your own listImport from linkA local copy you can continue
  • Enterprise Overview: how 100xprompt fits into team and organization workflows.
  • Security: data handling, privacy controls, and keeping sensitive work protected.
  • Web Interface: open and read shared sessions in the browser.

Enterprise Overview

How 100xprompt fits into team and organization workflows.

Security

Data handling, privacy controls, and keeping sensitive work protected.

Web Interface

Open and read shared sessions in the browser.