> For the complete documentation index, see [llms.txt](https://cullshot.gitbook.io/cullix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cullshot.gitbook.io/cullix/guide/handoff.md).

# Handing off

{% hint style="success" %}
Handing off **only copies** and **never overwrites** anything at the destination. Your originals stay unchanged.
{% endhint %}

## Share selection

**"Share selection …"** (**⇧⌘E**) hands your selection to:

* **Lightroom** (cloud)
* **Lightroom Classic**
* **Capture One**
* **Apple Photos**
* **a folder** (copy with XMP)

This creates **copies with embedded stars and color labels**.

![The Share selection dialog with hand-off to Lightroom](https://3241425949-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7nze4m2x861AVIl1RxE0%2Fuploads%2Fgit-blob-12b733e98d12ff93a596e2512d66f1ace7a04484%2Fshare-en.jpg?alt=media)

### Why copies?

For DNG, JPEG and HEIC, Lightroom **does not read** XMP sidecar files. To make stars and labels arrive, Cullshot embeds the XMP in the copy. Lightroom, Apple Photos and Lightroom Classic (via the copies) pick up stars and labels.

### Lightroom Classic

Classic links files instead of copying them. So Cullshot puts the copies in a remembered **handoff folder** – each handoff in its own subfolder ("date time folder name").

## Move Rejects to Trash

**"Move Rejects to Trash …"** moves rejected images together with their sidecar to the Trash – **only after confirmation**. You can restore them in the Finder.

This is the only place where Cullshot touches originals, and only at your explicit request.

## iPad

On iPad you share via the **share sheet** (images only) or copy with XMP. The trash corresponds to "Recently Deleted". See [Using Cullshot on iPad](/cullix/guide/ipad.md).


---

# 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://cullshot.gitbook.io/cullix/guide/handoff.md?ask=<question>&goal=<user_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.