mirror of
https://github.com/paperclipai/paperclip-docs.git
synced 2026-11-07 06:16:07 -10:00
Aron PrinsandClaude Opus 5.5
d811a89622
## Summary Every docs screenshot is retaken from Paperclip **v2026.1012.0**, in light and dark. Verifying them showed that about 50 guides described UI the release had moved or renamed, so those guides are updated too. **Screenshots** - 138 automated captures (276 PNGs), all stamped `v2026.1012.0` (`bba6a45`). The final run had no failed steps or skipped captures, and the luminance and theme check passes on all 278 files. - Four independent reviewers checked every light shot against its caption, then a fix round cleared the findings. - 37 captures (74 PNGs) are retired: none is embedded on any page, or the screen no longer exists in the release. - The capture pipeline (`scripts/screenshots/*`) is fixed for the release UI: - turns off the remote "Introducing Connectors" announcement that covered most shots; - masks local temp paths as `~/acme/…`; - keeps the demo company quiet during capture (no recovery loops, no capture-created activity rows); - seeds the states the guides describe: status cards, 50/80/100% budgets, a blocked inbox, schedule triggers, a checkbox confirmation, skills-capable agents and more; - uses updated routes and steps for the moved UI, and gains `scrollToTop`, `readyText`, per-target `experimental` flags, and comma lists for `--only`. - **The budget shots show a fixed incident card.** In v2026.1012.0 a warning-threshold incident is labelled "hard stop · This scope is paused", which is wrong. The fix is [paperclipai/paperclip#16201](https://github.com/paperclipai/paperclip/pull/16201). The costs and budget shots were captured from v2026.1012.0 with that patch applied, and the budget guides say so and explain what v2026.1012.0 itself shows. **Docs aligned with the release UI** - **Audit:** costs, budgets, runs and the timeline moved under Audit. That covers Costs and Budgets, Activity Log, Work Timeline, Set a monthly budget, and Dashboard. - **Agents:** the agent page's side menu (**Overview**, **Harness / Runtime**), the two-step **New agent** dialog, **Run now**, and the org chart as a view toggle. That covers Agents, Your first agent, Watching agents work, Key concepts, Org structure, Agent adapters and Adapters. - **Projects, routines, tasks, approvals:** current tabs, buttons and flows. - **Skills, plugins, company, settings:** current labels, including instant-join invites, the Experimental settings list, and **Settings → Experimental** paths on 21 pages. - **Removed features:** Auto-Create Recovery Tasks and Cloud Sync are marked as removed in this release. - Every rewrite was checked against the v2026.1012.0 UI source, then by two independent verifiers. A changelog entry is added under v2026.1012.0. ## Checks - [x] `npm run docs:build` - [x] `npm run docs:test` (all suites) - [x] `sync:lint-links` and `sync:verify-nav`: only the 4 intentional orphans remain - [x] SEO metadata and crawlable links ## Known, accepted - The activity feeds lead with agent setup events rather than task events. - The dashboard agent strip shows two cards for Ada. - Agent budgets can only be created from the CLI or API in this release, and the guides say so. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <[email protected]>
4.3 KiB
4.3 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.1012.0 | Experimental File Viewer | Read the reports, code changes, and screenshots an agent produced without leaving the task — the files, not just the comment thread that describes them. |
Experimental File Viewer
When an agent works on a task, the interesting output often isn't the comment thread — it's the files: the report it wrote, the code it changed, the screenshot it saved. Without the file viewer, seeing those means finding the workspace on disk or asking the agent to paste contents into a comment.
The Experimental File Viewer fixes that. It adds controls to every task detail page for browsing and previewing the task's workspace files right in the browser — search the tree, open a file, read rendered Markdown, view images and video, copy contents, download, and share deep links to an exact file and line.
Turn it on
- Go to Settings → Experimental.
- Turn on Experimental File Viewer — "Show task detail controls for browsing and previewing workspace files relative to a task."
The setting is instance-wide and takes effect immediately.
Where it appears
Once enabled, a task detail page grows several entry points to the same viewer:
- A file icon button in the task header (desktop only) — tooltip "Open file… (g f)".
- The
g fkeyboard shortcut anywhere on a task page. - A command palette entry — "Open file in this issue…".
- Two links on the task's Workspace card: Browse files… and Open file by path….
- Inline file links — when agent comments, documents, or artifacts reference workspace files, those references become clickable chips that open the viewer at that file. Work products that point at workspace files show up as clickable Artifacts chips too.
Using the viewer
The viewer opens as a large sheet over the task with two modes:
- Browse mode — a search box ("Search files by name or path…") plus a file tree. By default it lists recently changed files, so the agent's latest work floats to the top. Type to filter, use the arrow keys and Enter to open a result, or type a full path and press Enter to jump straight to it. Breadcrumbs track the folder you're in.
- File mode — a resizable file-tree sidebar on the left and a preview on the right:
- Text and code render with line numbers. If you arrived via a deep link with a line number, that line is highlighted and scrolled into view.
- Markdown gets a toggle between Rendered and Raw.
- Images and video preview inline.
Header controls in file mode: Download, Copy file contents, Copy link to this file view, and Close. The copied link encodes the file, line, and workspace, so a teammate who opens it lands on exactly what you're looking at. If you opened a file from browse mode, Back to files (or Esc) returns to the list.
When it's off
The flag is purely a UI gate. Turning it off hides the header button, shortcut, palette entry, and Workspace-card links, and inline file references render as plain, non-clickable chips. Nothing is deleted, and flipping it back on restores everything.
Limits and safeguards
- The task needs a local workspace. Remote workspaces show "Remote workspace preview coming soon"; if an isolated worktree has been cleaned up, the viewer says so instead of previewing.
- Size caps: text files up to 512 KB, images/video up to 10 MB. Larger files report "File is too large to preview" (you can still download).
- Sensitive paths are blocked. The viewer refuses secret-shaped files (
.env, SSH keys,.npmrc,.netrc, kubeconfig, anything under.aws/.ssh/.docker/.kube) and skips.gitandnode_modules. Path traversal outside the workspace is rejected. - The viewer is read-only — browse, preview, copy, download. No editing.
- Big folders page 100 items at a time with a "Load more from this folder" control.
Where to go next
- Workspaces — what execution workspaces are and how tasks get one.
- Artifacts — how agents attach deliverables to tasks.
- Experimental features overview