Swipe file
/library/swipe is your workspace's swipe file: the ads somebody here thought were worth keeping, in collections, with notes.
It is the workspace's, not one person's. Every member sees the same collections and the same items, the way every member sees the same media library — a swipe file whose point is "here is what we are up against" is worth less when only one person can open it. Each item records who saved it, so attribution survives.
Saving
Save to swipe on an ad card or an ad page puts it in the file.
- Your first save creates the workspace's Unfiled collection. Nothing is seeded ahead of time, so a workspace that never saves an ad never carries an empty collection.
- Naming a collection that does not exist creates it.
- Naming a collection for an ad that is already saved moves it there rather than saving it twice. One ad is one item per workspace, moved rather than duplicated between collections.
- A save of an ad that is already in that collection is idempotent: it costs nothing and creates nothing.
The button toggles. On an ad you have saved it reads Saved, and pressing it removes the item. The ad itself is untouched — the corpus is shared, so removing your row removes your row and nothing else. Removing an ad your workspace has not saved is refused rather than quietly succeeding, including one another workspace has saved, which yours cannot see at all.
Notes
Each item carries one note, and it belongs to the workspace that wrote it. Your note never travels with the ad into anyone else's file, and nobody else's note reaches yours.
A note is also searchable ground of its own kind: it comes back on the item
over MCP as savedNote, and a search result for an ad your
workspace has saved carries the note beside the saved flag — so your own AI
can read "we tried this angle in March" off the row rather than being told
about it.
What an item stores
A pointer, a note and who saved it. No copy of the ad.
That is deliberate, and it is what makes the next paragraph work. The item names the corpus row; the corpus row is shared and permanent; so every time you open your swipe file you get the ad as it is now — the same creatives, the same derived reading, the same published spend range and the same longevity score that search would give you today, not a snapshot of what it looked like when somebody pressed Save.
An ad that stops running stays
An ad you saved will eventually stop. When a run no longer returns it, it is marked Stopped and it stays — in the corpus and in your swipe file, with its status shown on the card.
This is the case the swipe file exists for. An ad that ran for eight months and then stopped is the most useful row in the library: it is evidence of something an advertiser committed to, and the moment it stops, the platform's own archive is where it is most likely to disappear from. Dropping it from your file the day the advertiser paused it would throw away the thing you saved it for.
The same rule applies to the whole corpus: nothing is ever deleted, and the last-seen date simply stops moving. See nothing is deleted.
Collections
A collection is a name, an optional description and the items in it. Its item count is computed when the page renders, never stored, so it is right rather than eventually right.
There is no delete for a collection. A collection exists while ads are saved
into it: remove the items and it has nothing left to hold. Over MCP the
swipe_collection entity says exactly that in its refusal, naming the call to
use instead.
What it costs
Saved ads are counted against your plan, because they are storage. The page states your count and the plan's ceiling, or says plainly that the plan sets none. At the ceiling a new save is refused with the limit named; editing a note or moving an item you already have is never refused, because neither adds a row. Allowances are on the billing page.
From an agent
Over MCP, list_swipe returns the collections and the items in
one call — a page that needs two calls to render is a page that renders twice —
and update_swipe saves, notes, moves and removes. Both are reachable through
tempio_manage as the swipe and swipe_collection entities.
Saving an ad changes nothing in your own ad accounts, so it creates no change request and there is nothing to approve.
Tracking and alerts
Watching an advertiser, the four kinds of activity alert and what each one fires on, the Monday digest, and how to turn the mail off without leaving Tempio.
The agent
The chat agent inside Tempio — what it reads, what it can draft, why it can never approve, and how its messages are metered.