Saving generations to a project is a folder; it does not remake the file

Keep the keepers together, in one collection. That is the job. Save generations to a project is one named agent capability. save_to_project takes hosted image/video urls and either an existing project_id (from list_user_projects) or a project_name to create one. Duplicate URLs are skipped. Saving does not use generation credits. Regenerating a take "so I have it" because chat scrolled is a generate you ran as a filing cabinet. That wastes credits on a cousin of a file you already paid for.

The folder is the artifact. The pixels already exist.

What save_to_project actually files

Give the agent the URLs and a project name — existing or new. It saves them into that collection. Required field: urls (absolute http(s), already hosted — not data URIs, not local paths). Prefer project_id when the project exists; pass project_name when it does not. Re-saving a batch to catch stragglers is safe because duplicates are skipped.

Output: those URLs sitting in a named project you can open later. Not a new render. Not a zip. Not a share link — share a generation with a link is a different named job.

The habit is to treat "save this" as part of liking a result, not a chore for later. "Save this to my Q3 Launch project" is enough. From then on, "find it" is "open the folder," which is more reliable than hoping a later prompt-search lands on the same words the original generate used.

What this job is not

A search. Find something I made before is how you recover a file you never filed. Search is for the mess. Save is how the mess stops. Do not search-as-save: describing the golden retriever again so the agent can regenerate it is a new still. File the old URL.

A generate. Nothing in this capability calls a model. "Save a version with warmer light" is an edit or a remake, then a save of the result. Asking save to "keep the good one and also make two backups" is how people spawn extras they did not need.

A brand kit. Set my brand kit stores defaults that apply going forward. A project stores specific files from a campaign. Putting hex codes in a project name does not set a kit. Putting keepers in the kit does not file a campaign.

A share review loop. A project is for you (and teammates who can see the account). A review link is create_share_link. Clients should not have to join a project to see one take, and you should not regenerate a preview because you skipped the share job.

File the keeper. Do not reroll it to keep it.

The waste is almost always retrieval panic. The take existed. Chat scrolled. Downloads filled up. Someone regenerated "the coffee shop one" for a deck due in an hour. Credits gone, identity drifted, the original still sitting in history unfiled.

Order:

1. When you would download it, save it to a named project instead — or as well.
2. Name the project after the job ("Product launch — scene 3"), not "New Project."
3. If you cannot see it, search your library before you generate.
4. Only generate when the file is actually wrong, not when it is merely unfiled.

Saving is free of generation credits. That is not a reason to dump every miss into a folder until the folder is as noisy as history. Save keepers and the near-misses you might still need. Do not save the sampler.

Using generate, search, share, or a brand kit as a substitute is how a filing problem becomes a credit problem.

FAQ

Does saving to a project cost generation credits?

No. save_to_project files URLs you already have. Duplicate URLs are skipped. Regenerating in order to "have a copy in a project" is the billed job you should not run.

Can I save a file that is only on my laptop?

Not directly. The URLs must be absolute http(s) already hosted on Versely — a generation, an upload, a library item. Upload first, then save. A local path is not a urls entry.

Is a project the same as finding something I made before?

No. Search recovers by description. A project is a named collection you chose. File on the way in so you are not searching on the way out. Search is the backup for the week you forgot.

Should I save every variation in a pack?

Save the ones you might still ship or learn from. Saving the entire sampler recreates generation history inside a folder, which is how "open the project" becomes another scroll. Keepers plus one or two near-misses is a collection. Twenty cousins is a mess you paid to make and then paid nothing to file.