Make and save images

Prints turns a prompt into media saved on your Team’s Computer. Its gallery shows the files in the selected folder. You can also upload images you already have.

Choose where the images go

1. Open Prints from your Team’s App launcher.
2. Select the Computer you want to use. Prints needs permission to read and write its files. Generation also needs the Team’s media approval and credit.
3. Open the folder chip beside the composer controls (Choose folder before a folder is selected). Enter an absolute folder path, such as /media. Choose Use if it exists, or Create to make it.

Prints remembers one folder choice per Computer in its App backend. Switching Computers changes which folder and gallery you see. A normal image write does not create a missing folder for you.

See Use Computers for Computer selection and Use Apps for permission settings.

Generate an image

1. Write a prompt in the composer. Describe the subject and the result you want. For example: “A small green mushroom house beside a stream, watercolor.” This is an illustrative prompt. Submitting it starts billed generation.
2. Choose a Generation model and its available size and settings.
3. Check the displayed save folder, then choose Generate image.
4. Wait for the reserved gallery tile to become a readable image. Selecting a saved Computer image asks the host to open that file in Inkcap.

The model list and settings come from the Team’s granted media service. If a model supports image references, use Add reference on a gallery image. The composer shows the model’s reference limit. Changing models can clear references or reduce that selection.

An empty model list or disabled generation action needs attention to media access and funding. An Agent’s own provider key does not supply Prints’ hosted media access. Usage is charged to the Team. See Billing.

Browse the gallery

The gallery reads media files from the selected Computer folder. It loads pages of up to 24 matching files; choose Load more images when more are available. Loaded images are ordered by the Computer’s file modification time, newest first, with filenames breaking ties. An image’s loading speed does not determine its order.

Generation and uploads reserve tiles while work is running. A saved result replaces its placeholder after Prints can read and decode it. If preview loading fails, use the tile’s retry action. An unavailable preview is different from a failed write.

Recover an unfinished save

Generating, saving and confirming completion are separate stages. Before sending a generation, Prints records its Computer, request, input and destination. After the image is saved, its backend records the completed print and file location together and removes the unfinished record. A lost completion reply can still be recovered using the same attempt.

Use the failed tile’s retry button or Retry in Activity. These actions reuse that attempt’s request and destination. When generated bytes are retained, recovery saves those bytes without asking for another generation. Editing the composer does not change the captured attempt.

After reopening Prints, retained attempts appear as Unfinished image in Activity. Choose Resume for that attempt, with its original Computer selected. Switching Computers does not move the attempt to the new destination. Load more activity retrieves further retained attempts when offered.

Discard removes an unfinished recovery record. It does not delete a file already saved or undo a charge. Dismissing a notice, or choosing Clear, only hides nonblocking notices; it does not discard an attempt or cancel work. Setup notices stay until their cause is resolved.

A new submission creates a new attempt and can incur another charge. Use the existing retry action to recover work rather than submitting the prompt again. A missing preview alone does not prove that no file was saved or no charge occurred. Check the destination in Inkcap if Prints cannot display it.

Upload your own images

Drop image files into Prints, paste images, or choose Upload images. Uploads write to the selected media folder and show progress. When the saved image can be read and decoded, it replaces its reserved tile.

An upload retry keeps the original Computer and destination. Return to that Computer before retrying. Dismissing a progress notification only hides it. It does not cancel the write. Use the transfer’s cancel action when available.

If something fails

Open Activity beside Send for setup, image and upload details. When the Team is out of credit, Prints shows Media generation needs Team credits. Add credits in Billing, then retry. Choose Open Billing to open the Team’s Billing page. Funding and App permission are separate requirements.

When Prints loses its host connection, Activity shows Connection lost with “Reopen the App to connect again.” Reopen Prints from your Team’s App menu, then check the selected Computer and permissions before retrying. This setup notice stays until the connection returns; Clear does not dismiss it. An empty gallery does not establish that the connection is working.

What you see	What to check
No usable media folder	Check the path and file permissions, then choose or create a folder
No generation models or a permission denial	Check the App’s media approval and selected Computer
A funding refusal	Choose Open Billing and fund the Team before retrying
An unfinished generation	Use its retry action on the original Computer
A saved file with an unavailable preview	Check the file and retry loading it before generating again
A failed upload	Read its error and retry on its original Computer

Prints reports generation, save and preview failures separately. Keep the existing attempt when its outcome is uncertain. A successful request being accepted is different from an image being saved and visible in the gallery.