Artifacts

Artifacts are the files a step leaves behind for a person to look at: design options as Markdown, SVG wireframes, screenshots, an HTML prototype, a PDF report. Jimothy keeps them with the run and shows them on the step, so you don’t have to dig through the workspace to review what an agent made.

What gets kept

Agent and shell steps are watched. Before each attempt, Jimothy notes every candidate file in the workspace (its size and modification time). When the attempt ends, the files that are new or changed are copied into the run’s folder. This works whether or not the step commits, and in workspaces that aren’t git repositories.

By default a step’s artifacts are the documents and images it adds or changes:

Kind	Extensions	Shown as
Markdown	.md, .markdown, .mdx	Rendered Markdown
Image	.png, .jpg, .jpeg, .gif, .webp, .svg	The image
PDF	.pdf	The PDF
HTML	.html, .htm	The page, with scripts turned off

Hidden folders (.git, .claude, …), node_modules, and build folders (dist, build, out, target, coverage, vendor, …) are skipped.

Choosing the files

To pick the files yourself, set Artifacts on the step (under Flow) to one or more comma-separated globs, relative to the workspace:

docs/designs/**, screenshots/*.png

With globs set, any changed file that matches counts, whatever its type: .txt, .json, .csv, .yaml and .log files are shown as text, and anything else can be downloaded. A plain folder path such as docs/designs matches everything inside it. In JSON this is the step’s artifacts field:

{ "id": "draft", "type": "agent", "artifacts": ["docs/designs/**"] }

Limits

Each attempt keeps up to 50 files, 10 MB per file and 25 MB in all. Files over the limits aren’t kept; the step’s log says how many.

Caution

Steps that run at the same time in the same workspace can each pick up files the other one changed. Give parallel steps their own artifact globs if that matters.

Where they show up

• The Artifacts tab on the step (with a count, like Artifacts · 3): the files on the left, a preview on the right, and Download for each one. It follows the attempt picker, so after a rejected round you can still look at the earlier attempt’s files.
• Logs: thumbnails and file tiles right under the Kept N artifacts line. Click one to open it in the Artifacts tab.
• Details: the same tiles above the attempts table, which has an Artifacts column linking each attempt’s files.
• Approval banners: when an approval waits on steps that made artifacts, they’re listed as chips (From Draft design options: option-a.md, option-a.svg, …), so you can open each one before you decide. See Approvals.

Using them in later steps

{{steps.<id>.artifacts}} lists the paths of the step’s latest artifacts, one per line, relative to the workspace. A later agent working in the same workspace can open them:

The reviewer picked:
{{steps.pick.selected}}

The design files from the previous step:
{{steps.draft.artifacts}}

Read the picked option's files, then write docs/designs/spec.md.

Where they’re stored

Each attempt’s artifacts are copied to runs/<run-id>/steps/<step-id>/<attempt>/artifacts/, keeping their paths. They stay with the run after its workspace is cleaned up, and are removed when you delete the run. See Data & security.