Case file · For AI agents

Your agent runs the errand.
Fullsy keeps the receipts.

off by default · one toggleevery capture on the record ✓

AI assistants that work inside your browser can drive Fullsy: hand it pages to capture while they research, and every page they read becomes a fingerprinted Capture Record. "My agent looked it up" turns into something you can check — source by source.

Agents · 01 · How it stays yours

Consent first. Audit trail always.

your browser · your togglenothing hidden ✓
The rules, in order
You switch it on — the "Agents" toggle in Fullsy's toolbar, plus one permission prompt. Off is the default, and off means the door doesn't exist.
You watch it work — agent captures open in real, visible tabs, no faster than one every fifteen seconds.
Capture, and only capture — it's the same full-page grab you'd trigger by hand, just started by your agent. It can't browse, click, or read your pages; it can only capture the one you point it at.
Everything is filed — each errand becomes a case file, separate from your own capture history, marked agent-initiated.
Everything stays local — records live in your browser. Fullsy has no server to send them to.
Agents · 02 · Case files

Every errand becomes a case

one errand · one case · one zipdownload the whole thing ✓

Agent captures never mix into your own history — they file into a named case, one per errand, on their own shelf. "Download case" hands you the entire errand as a single zip that carries its own proof:

competitor-research-case.zip ├── index.html ← readable case cover, one row per record ├── case.json ← every record, every fingerprint └── 02-competitor-com/ ├── report.html ← readable record: SEO + design + hashes · Pro ├── screenshot.png ← the whole page, stitched ├── document.pdf ← searchable, links click · Pro ├── page.html ← the source as captured ├── page.mht ← sealed one-file archive ├── seo-report.json ← signals + heading tree · Pro ├── design-tokens.json ← their palette, ready to use · Pro └── metadata.json ← the integrity manifest

Fingerprints are SHA-256 hashes recorded at capture time and re-checked every time a record opens. They prove your copy is intact — they are not a legal-authenticity claim.

Agents · 03 · Ready-made skills

Two skills, ready to install

claude code · codex · any js-capable agentplain markdown ✓

A skill is a set of instructions your agent follows. These two teach it the whole workflow — read, capture, file, report — with the consent rules built in. Read them before you install them; they're short on purpose.

/research-with-fullsy

Research a question — or tear down a set of competitor pages — and capture every source along the way. The answer arrives as a memo where each claim carries a record id, and the whole errand files as one case.

Read the skill →

/watch-pages-with-fullsy

Re-capture pages you care about — pricing, terms, claims — and report what changed since last time. Matching fingerprints prove nothing moved; anything that did comes back with before-and-after records.

Read the skill →

Install for Claude Code: save the file to ~/.claude/skills/research-with-fullsy/SKILL.md — then ask for it by name. Other agents: paste the skill into the instructions surface your agent reads.

Agents · 04 · The bridge

The whole API is four calls

window.fullsy · in-page · rate-limitedcontract stable ✓

When the toggle is on, every page carries window.fullsy — a small, boring API on purpose. Agents that can run JavaScript in your browser need nothing else installed.

// start a capture of a URL — opens a visible tab, files into a case await fullsy.captureUrl(url, { caseName: 'competitor research' }) // → { ok, capId, status: 'started' } — then poll: await fullsy.getRecord(capId) // → record + fingerprint manifest await fullsy.list(10) // → recent captures, cases marked await fullsy.capture() // → capture the current page

One capture per fifteen seconds. Only http(s) pages. Captures are visible by design — the audit trail is you, watching.

Agents · 05 · Asked before you ask

Questions

for the recordanswered ✓
Can a website — or an agent — capture things without me?

No. Agent access is off until you switch it on, and switching it on is a visible choice with a permission prompt. When it's on, captures happen in tabs you can see, rate-limited, filed into cases you can open and delete. The toggle turns it all off again, and the API disappears from every page.

Which agents work with this?

Any assistant that can run JavaScript in your own browser — Claude in Chrome and tools like it. Agents without browser access can't reach Fullsy at all: the bridge lives in your Chrome, on your toggle, by design.

Is agent capture part of Pro?

Yes — agent capture is a Fullsy Pro feature, and every install's 30-day trial includes it, so you can run real errands before deciding. After the trial, agent capture and the Records need a Pro license; your captures and the free tools keep working. On Pro, a downloaded case also carries the report pack for every record — a readable report.html (the SEO and design reports styled like the app, with the fingerprint manifest), a browsable case index.html, plus a searchable PDF, the SEO teardown, and the design tokens.

Where does the evidence live?

In your browser's local storage, like every Fullsy capture. Download a case and the zip is self-contained — the manifest carries every fingerprint, so anyone you hand it to can check the files against the hashes.

Closing note

Agents move fast.
Fullsy keeps the receipts.

Free capture forever · Pro report packs — 30-day trial included