Artifacts
Artifacts are the documents an agent run leaves behind: its plan, a walkthrough of what it did, screenshots, and sometimes an interactive HTML page. Review them in the Artifacts view and comment on any line; your comments go straight back to the agent.
What a run saves
Each agent turn that writes something gets its own folder, .ingot/artifacts/<run-id>/:
| File | Contents |
|---|---|
plan.md | the agent's plan as a checklist, updated when the plan changes |
walkthrough.md | written when the run ends: steps, changed files, screenshots and the result |
<name>.md | any other note the agent saves |
<name>.html | an interactive HTML page: a chart, a diagram or a small demo |
screenshots/shot-1.png | screenshots from the built-in browser |
comments.json | your comments |
Markdown is the default: a name without an extension is saved as .md. A file name may use letters, digits, ., _ and -, up to 64 characters, and a file holds up to 200,000 characters.
Plain questions that change nothing leave no folder behind. .ingot/artifacts/ holds a .gitignore that ignores the whole folder, so run records stay on your machine and never show up in git status or a commit.
# Walkthrough: Add CSV import
> Add a CSV import to the products page
## Steps
- [x] Parse the CSV file
- [x] Add the Import button
## Changes
- `src/products/import-csv.ts`
- `src/products/ProductsPage.tsx`
## Screenshots

## Result
The products page has an Import button that reads a CSV and shows a preview before saving.
The Artifacts view
Open it with Agents: Artifacts (⌘⌥⇧F, Ctrl+Alt+Shift+F on Windows and Linux), or from a chat's row in the Agent Manager.
- Pick a run from the dropdown (newest first).
- Each file has its own tab:
plan.md,walkthrough.md, then other notes and HTML pages. - Screenshots show inline and in a gallery below the document.
Interactive HTML artifacts
Besides Markdown, the agent can leave a small HTML page, <name>.html, when a picture says more than text: a chart of benchmark results, a diagram of a flow, or a demo of a component. Ask for one ("show the bundle sizes as a chart") or let the agent decide.
An HTML artifact opens as a tab next to the Markdown ones and runs live in a frame.
The page is sandboxed:
- Its own scripts run, but it can't reach Ingot or your project, submit forms, open popups or navigate the window.
- It has no network access. External scripts, styles, fonts, images and fetch requests are all blocked.
- So everything must be inside the file: CSS, JavaScript, and images as
data:URLs.
There is no deploy or share button. The file stays in the run's folder with the other artifacts.
Comment on a line or a screenshot
Hover a line and click +, or click Comment under a screenshot. Type your note and choose Send to agent. The agent receives it with the exact place you pointed at:
Comment on artifact plan.md line 3 ("- [ ] Parse the CSV file"): handle semicolon-separated files too
| The chat is… | Your comment |
|---|---|
| running | is read by the agent on its next step, so you can steer it mid-run |
| idle | starts a new turn in that chat |
| closed | is saved with the artifacts |
Line comments work on Markdown artifacts only. An HTML artifact shows a note saying so.
Settings
| Setting | Default | What it does |
|---|---|---|
ingot.artifacts.html | On | Interactive HTML artifacts. Off, the agent is told HTML artifacts are turned off and writes Markdown instead |
The switch is also in Settings › Features and in the first-run setup, under Agent.
.ingot/artifacts/ ignores itself in git, so HTML pages and screenshots never end up in a commit. Delete a run's folder to clear it.