Skip to content

Deliverables

A QuickAgent's run writes a folder of files: what it was asked for, its working notes, and the receipts that prove how it ran. The deliverables are the part you came for. A run names them, so that Agentry can show them first, copy them to a folder you keep your work in, and open them with one click.

This page is about the idea and what every client shares. The desktop app's screens are on its own page, and the commands and the record's exact shape are in Running them.

What counts as a deliverable

The QuickAgent says which file is the one you asked for. When it writes a report or exports a PDF, it can mark the file as a deliverable and give it a title, such as "Weekly digest". It leaves its notes and drafts unmarked.

The runner, not the QuickAgent, makes the final list, once the run is over and its containers have stopped. It lists a file only if it is a regular file under the run's reports folder, and it records the file's SHA-256 and size itself, as the file is then.

When a QuickAgent marked nothing, the runner picks, so a run still shows its work:

  1. the PDFs the run exported;
  2. otherwise the files in reports;
  3. otherwise the final message, saved as deliverable.md with the title "Result", when it is plain text. A run that returns structured data, a chat, and a run that failed have no such file.

The list is part of the run's record, the envelope in result.json. It needs agentry-cli v0.6.138 or later. A run that ended on an older runner has no list.

Copying them to a folder

Nothing is copied unless you give a folder, and neither a QuickAgent nor its publisher can name one. Where you give it:

  • The desktop app has a Deliverables folder in Settings → Run defaults, on unless you turn it off, an Agentry folder in your Documents folder until you choose another (Deliverables folder). Needs Agentry Desktop 0.6.136 or later.
  • The command line copies to the folder named by agentry run --deliver-to DIR, or by deliver.folder in the CLI's config for every run. agentry deliver RUN-FOLDER --to DIR copies from a run you already made. Needs agentry-cli v0.6.138 or later (Copying them out).

Each copy lands in <folder>/<QuickAgent>/<date time> <title>/. The file is copied only after its contents are shown to match the record, so a file that changed after the run is refused and nothing of it is left. A copy never replaces a file that is there, names are made plain for every system, and the run's own folder is left as it was apart from a note of what was copied. On Windows and macOS each copy is marked as a download, so the system treats it as a file from outside the computer.

Copying never changes how a run ended. A copy that could not be made is recorded, and the run is still the run it was.

What opens with one click

A file a QuickAgent wrote can be anything, and some types are acted on by your computer the moment you open them. So the desktop app opens only a short list with one click: PDF, Markdown, text, CSV, JSON, PNG, JPEG, Word, Excel and PowerPoint documents. It checks each file's first bytes as well as its name, and it refuses an Office file that carries a macro project, a control or an embedded object. Every other type, such as a web page, a shortcut, a script or a document with macros, is shown in its folder and left for you to open yourself (Open, View and Show in folder).

The app also lists a deliverable only while it is still the file the run recorded.

On the website

A run you ran In Agentry lists its deliverables first on its page, above its result and the other files it wrote. Each has a Download, and a PDF an Open, which shows it in your browser's own PDF viewer in a tab of its own. Open checks the file against the run's record again before it shows anything, and every other type is a download; the page never draws what a file holds.

Settings → Dashboard has the Dashboard's optional cards, each off until you switch it on. The Deliverables card lists the files of your latest runs that finished well, newest first, up to eight, each with the QuickAgent it came from and its Download or Open. It says so when your runs, or one run's files, could not be read. The switch is kept in the browser you set it in, for your account, so another browser starts with the card off.

Only you can read a run's deliverables. Another account, platform staff and the other members of an organization that paid for your run are told the file is not found, and each file is served only if it is still the one the run recorded, by its fingerprint. A run on a sandbox host whose runner predates agentry-cli v0.6.138 has no list, and nothing is drawn for it.

Where they appear

Where What you see
Agentry Desktop 0.6.136 or later The files first on a run's result, a Deliverables card on Home, and the Deliverables folder.
The agentry command The envelope's list, the copies --deliver-to makes, and agentry deliver.
A run In Agentry The website's run page lists the run's deliverables first, and the Dashboard can show a Deliverables card (on the website). The desktop copies a run's deliverables when its output comes down, if the runner that ran it recorded them (Running on Agentry).