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]>
1.9 KiB
paperclip_version, seo_title, seo_description
| paperclip_version | seo_title | seo_description |
|---|---|---|
| v2026.1012.0 | Cloud Sync (Retired) | Cloud Sync, which pushed a local company into a Paperclip Cloud stack, is gone in this release. Here is what replaced it and where old links now go. |
Cloud Sync (retired)
Removed in this release. Cloud Sync no longer exists in Paperclip v2026.1012.0. There's no Cloud upstream screen, no Cloud Sync toggle on Settings → Experimental, no
paperclipai cloud pushcommand, and no cloud-upstream API. To move a company to another instance, including a hosted one, use company Export and Import instead. See Back up and restore a company.
What it was
On older builds, Cloud Sync connected a locally run Paperclip instance to a Paperclip Cloud upstream. You could preview a push, resolve conflicts, push a local company (agents, projects, issues, skills, portability files) into a cloud stack, and then choose which agents, routines, and monitors woke up on the cloud side.
What you'll see now
If you follow an old link or bookmark to the Cloud upstream page (/company/settings/cloud-upstream), Paperclip sends you to the Export page instead:
From there you can export the company to a portable package and import it on the other instance. Import/Export moves the same things Cloud Sync did, and it works local-to-local, over a URL, or from GitHub, with no live upstream connection and no experimental flag.
Where to go next
- Back up and restore a company: the replacement workflow.
- Company export & import: the Export and Import pages in detail.
- Experimental features overview