> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/ai/reference/share-links.md). # Share links What a share link opens when you share a failing test, a run, a browser session, a file or a trace, who can open it, how long it lasts, and how to turn share links off When you share a failing test, a CI run or a session an agent recorded, Currents creates a share link. Anyone who has the link can open it, without a Currents account, until it expires. A colleague, a reviewer or an agent then opens the results and files themselves. This page lists each kind of link, what it exposes, and how to turn share links off. | Link | What it opens | Where you create it | Lifetime | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | Fix link | The failure context of a failing test or run, ready for an AI agent. See [Fix failing CI tests](/ai/agentic-testing/fix-failing-tests.md#share-a-fix-link). | **Share failure context** in the dashboard, Slack or the GitHub run comment | 1, 3 or 7 days; default 1 | | Shared Run | Every test of a run, with links to its files. See [Share a CI run](/ai/agentic-testing/share-a-run.md). | **Share whole run** in the dashboard, or ask an agent connected to the Currents MCP server | 1, 3 or 7 days; default 7 | | Shared Session | A [session an agent recorded](/ai/agent-evidence.md), with its files | `currents session share` in the Currents CLI, or ask an agent connected to the Currents MCP server | 1, 3 or 7 days; default 7 | | Test link | One test of a Fix link or Shared Run, with its steps, files and traces | Created with the Fix link or Shared Run, one for each test it lists | As long as that link | | File link | One screenshot, video, log or trace zip | Created with the link that lists the file. **Copy link** on a session file. | As long as that link | | Trace API link | One Playwright trace, for an agent to read in steps. See [Explore a trace](/ai/agentic-artifacts/explore-a-trace.md). | Created with the link that lists the trace, or alone by an agent connected to the Currents MCP server. See [Get a trace API link](/ai/agentic-artifacts/explore-a-trace.md#get-a-trace-api-link). | As long as that link; alone, 24 hours or up to 7 days | A test link opens one test only, not the run it came from. A Fix link, a Shared Run and their test links show the results as they were when the link was created. A Shared Session shows the session as it is now, including files added after the link was created. Fix links, Shared Runs, Shared Sessions and test links also have a Markdown version for agents: add `.md` to the link. A trace API link has its own [routes for agents](/ai/reference/trace-api.md). To put these links in a pull request, Slack or Linear, see [Post evidence to GitHub, Slack and Linear](/ai/agentic-artifacts/post-evidence.md). ## What a link exposes Everything the shared results contain: errors, stack traces, console and network logs, stdout and stderr, screenshots, videos and traces. A trace holds request bodies, headers and cookies. Share a link only where you would post a public gist. Record sessions with test accounts, and do not print secrets in tests. ## Turn off share links An organization admin can turn off **Public share links** in the AI section of the organization settings. New links then fail with `403`, and Slack and the GitHub run comment fall back to a prompt without a link. Links that already exist keep working until they expire. The setting does not apply to trace API links. The GitHub integration also has a **Context Links** setting for each repository: whether the run comment includes a Fix link, and how long it lasts. ## Read limits Public reads are rate limited per reader and per link. A link that many people open at once can answer `429` with a `Retry-After` header, even to a reader who opened it only a few times. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.currents.dev/ai/reference/share-links.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.