# Save and share results

Keep a useful output or publish a fixed copy of selected context and files.

Choose the output you need. Saving a file on your computer, updating a provider document, creating a share link, and sending that link to another person are separate actions.

## Save a result for yourself

Use your terminal, editor, or agent host's file-writing capability to save a summary or generated file. Keep its location and source references. Reopen the file to check its contents. For a document in an app, use that app's current write method and read the saved object afterward.

Vision does not provide a universal file-export command for every tool result. Use [Run an action](/docs/vision/tools/actions) for an app document or [Work with local files](/docs/vision/tools/local-files) to locate an existing file.

## Understand a Vision share link


### Public, fixed copy

A Vision share is a **static copy** of selected text or files. Anyone holding the link can read the published copy. The current mode has no recipient access control, expiry, or revocation, and changes to the originals do not update it.

Choose a different supported sharing route if you need restricted recipients, expiration, or a live collaborative document. The recipient does not gain access to your original Vault or account.

## Prepare, publish, and inspect a share

1. **Choose the audience and contents**

   Specify the audience and purpose, such as a contractor receiving the agreed project brief. Select only the necessary material and preserve any exclusions. Find and inspect files through the allowed file connector, or open the saved records behind a summary.

   The share input records the selection and review basis. `reviewBasis:"content"` means the contents were inspected; `"metadata-only"` means only file information was checked. Do not label a file content-reviewed from its name alone.

   A file decision of `redact` does not edit its bytes. If a file needs redaction, create a redacted copy, inspect that copy, and select its actual path; otherwise exclude the file. Text facts use the explicit outbound `shareText`.

2. **Build a preview**

   Use one connected MCP session for the preview and publication. In an agent host, keep the same Indra connection open. Without an agent, [open MCP Inspector](/docs/vision/reference/mcp-setup#section-use-mcp-manually), connect to your Vault, and select `indra.action` in its Tools panel. Submit the JSON inputs below through that tool.

   **Current terminal limitation:** separate `zortex action` commands do not retain a share preview. A preview is held by the process that created it, so a later command cannot publish it. Keep the MCP server and its connection running through step 3. If that session ends, create and review a new preview. Terminal continuity is an implementation gap; the intended workflow is still to publish the exact reviewed selection.

   For actual local files, the following is an **input template**. Replace every placeholder with the values you selected and inspected. It describes one non-sensitive project brief with no identified risk; change the assessment to match the real file.

   ```json
   {
     "name": "share.preview",
     "params": {
       "intent": "Share the agreed project brief",
       "audience": "Project contractor",
       "purpose": "Prepare the project estimate",
       "candidateRefs": [],
       "fileSelection": {
         "source": "computer-files",
         "folderPath": "<allowed-absolute-folder>",
         "folderLabel": "Project brief",
         "files": [{
           "path": "<actual-absolute-file-path>",
           "reviewBasis": "content",
           "necessity": "required",
           "risks": [],
           "decision": "include",
           "confidence": "high",
           "reason": "The requested brief needed for the estimate"
         }]
       }
     }
   }
   ```

   Inspect the returned preview. Check the files, outbound text, audience, purpose, and content-review status. A preview assembles data; it does not publish the link. Under an already authorized sharing request, the agent should proceed with the valid selection instead of adding an unrelated approval loop.

   For a summary of saved information, use `candidateRefs` and `facts` bound to the exact source records. Each fact includes `ref`, `title`, exact `sourceQuote`, outbound `shareText` when included, `necessity`, `risks`, `decision`, `confidence`, and `reason`. For live source facts or provider files, use the contracts in [Action reference](/docs/vision/reference/actions). A title-only selection is insufficient evidence for a factual summary.

3. **Publish the fixed preview**

   Copy the returned preview ID and call `indra.action` again in the same session:

   ```json
   {
     "name": "share.create-link",
     "params": {"previewId": "<returned-preview-id>"}
   }
   ```

   Publication rereads the selected bytes and checks that the source and metadata still match. If something changed, reread the affected material, build a fresh preview, and continue with its new ID. Do not bypass the mismatch by recycling the old preview.

4. **Inspect the published copy**

   Use the exact returned URL:

   ```json
   {
     "name": "share.inspect-link",
     "params": {"url": "<returned-share-url>"}
   }
   ```

   Check that the published selection matches the requested handoff. If the manifest includes a file, use its returned identity:

   ```json
   {
     "name": "share.read-file",
     "params": {
       "url": "<returned-share-url>",
       "fileId": "<returned-file-id>"
     }
   }
   ```

   The bounded reader returns supported UTF-8 text or download metadata for binary content. Google Drive's native documents use export formats: Docs as PDF, Sheets as XLSX, and Slides as PPTX. Use the returned file names and formats rather than assuming the original cloud file remains live.

## Finish the handoff

Return the link, what it contains, and any material review limit. Creating a link does not send it to the intended person. Use an authorized communication channel only when sending was part of the task.

If publication fails or times out, inspect any returned link and operation result before creating another copy. If a file exceeds a size bound or changes version, fix the selection and rebuild the preview. Never silently omit a requested file and call the handoff complete.

The [Action reference](/docs/vision/reference/actions) contains the complete input fields. Once a link has been published, inspecting its URL does not depend on retaining the preview session.
