> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genesiscomputing.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Artifact Manager Tools

> Manage generated artifacts from agentic workflows. Describe, link, and delete stored outputs like reports, images, and data files.

## **Overview**

### **Tool Name**

```json theme={null}
artifact_manager_tools
```

### **Purpose**

The **artifact\_manager\_tools** provide controlled access to files created by bot operations. Use them to look up artifact metadata, retrieve access links, and remove unneeded outputs while preserving security and traceability across projects.

#### **Functions Available**

1. **`manage_artifact`**: *Describe or delete an artifact by ID, returning metadata and an access link for sharing when available.*

### Key Features

<Steps>
  <Step title="Unified Artifact Access" icon="boxes-stacked">
    Centrally manage outputs created by bots, including documents, images, and data files.
  </Step>

  <Step title="Rich Metadata" icon="circle-info">
    Retrieve type, size, timestamps, owning context, and a shareable path when supported.
  </Step>

  <Step title="Safe Sharing" icon="link">
    Generate or surface a clickable link for stakeholders to review results without moving files.
  </Step>

  <Step title="Lifecycle Controls" icon="trash-can">
    Remove obsolete artifacts to reduce clutter and storage cost. Deletion actions confirm success or return errors.
  </Step>
</Steps>

## **Input Parameters for Each Function**

### **`manage_artifact`**

**Parameters**

| **Name** | **Definition** | **Format** |
| - | - | :-: |
| **action** | Operation to perform. One of `"DESCRIBE"` or `"DELETE"`. | String (required) |
| **artifact\_id** | Unique artifact identifier in UUID-4 format. Obtained from prior data agent outputs or logs. | String (required) |

<Tip>
  Run`DESCRIBE`first to confirm the artifact content and context before calling.
</Tip>

## **Use Cases**

1. **Retrieve prior analysis results** Describe a stored CSV or PDF created by a data processing agent and surface a link for review.
2. **Access generated media**
   Get details for images produced by `image_tools` and share the artifact link with stakeholders.
3. **Manage storage hygiene**
   Delete outdated simulation outputs after publishing a final report.
4. **Reference past work**
   Pull metadata for artifacts attached to a project milestone to include in documentation.

<Warning>
  **Permanent deletion**

  Removing an artifact cannot be undone. Verify the ID and relevance first.
</Warning>

## **Workflow/How It Works**

<Steps>
  <Step title="Locate the Artifact ID" icon="magnifying-glass">
    Copy the UUID from the data agent response, task log, or project record that created the file.
  </Step>

  <Step title="Describe the Artifact" icon="file-lines">
    Call`manage_artifact`to retrieve metadata and link details.
  </Step>

  <Step title="Share as Needed" icon="share-from-square">
    Use the returned link path for stakeholder access according to your permissions model.
  </Step>

  <Step title="Clean Up" icon="trash">
    If the artifact is no longer needed, call action=`"DELETE"`. \
    Capture the confirmation message for your records.
  </Step>
</Steps>

## **Integration Relevance**

* **`image_tools`**: Manage images generated or processed during workflows.
* **`snowflake_tools`**: Track exported query results and reports as artifacts.
* **`file_manager_tools`**: Register artifacts as managed files when they must be attached to missions or tasks.
* `git_action`: Cross-reference saved files committed to repositories with their produced artifacts.
* **`project_manager_tools`**: Link artifacts to project deliverables for audits and reviews.

## **Configuration Details**

* Artifact IDs are generated automatically as UUID-4 values.
* No setup is required to create artifacts. They are produced by tools that generate files.
* Access permissions typically inherit from the creating data agent or user context.
* Retention and expiration policies may apply depending on system configuration.

<Note>
  Artifact access can be restricted by ownership and permissions. Users without access will receive detailed error messages on describe or download attempts.
</Note>

## **Limitations or Notes**

1. **ID format**
   The `artifact_id` must be a valid UUID-4 string.
2. **Irreversible deletion**
   Deleted artifacts cannot be recovered.
3. **Access scope** Viewing or downloading may be blocked by permissions or data agent ownership rules.
4. **Large files**
   Very large artifacts may have longer access times or require special handling.
5. **Temporary storage**
   Artifact storage is optimized for working outputs, not long term archival.
6. **Expiry**
   Some artifacts may expire after a defined period and become inaccessible.

### **Output**

* **Describe**
  Returns artifact metadata including ID, type, size, created timestamp, content summary, associated entity references, and a clickable link path when available.
* **Delete**
  Returns a success confirmation for removal or a descriptive error if the artifact is inaccessible or the ID is invalid.
* **Errors**
  Clear diagnostics for invalid UUIDs, permission failures, or missing artifacts.