Projects, restore points and API tokens

#Edit Project

Edit Project opens the project as text so you can change many scenes in one pass. Open it with the small </> button (Edit project JSON) next to the project's name in the Project section of the right-hand panel. The editor covers the preview; press Close or the button again to leave.

The file has the project's name and a scenes list. Each scene shows only the fields it has set, from this list: name, h1, h2, h3 (the headline lines), ctaText, disclaimerOverride, duration, the background and text colours, the logo and content positions, alignment, and notes. Everything else about a scene (its layers, its framing in each format, its generated images) stays as it is.

How Apply works

1. Edit the text and press Apply. The status reads Applied and the project saves itself.
2. Each entry in scenes updates the scene in the same position: the first entry changes scene 1, the second changes scene 2, and so on.
3. Extra entries at the end become new scenes. Removing entries from the end removes scenes.

Because scenes are matched by position, moving an entry up the list rewrites the text of both scenes rather than moving the scenes. Reorder scenes in the Scene overview instead. Deleting an entry from the middle shifts every later entry up one and drops the last scene.

Only the JSON itself is checked. A missing comma gets an Invalid JSON message and nothing changes; a wrong value, such as a word where a number belongs, is applied as typed. Fonts, colours and the logo belong to the design system and are edited in its own code editor (see Design systems).

Worked example

A six-scene sale campaign needs "20% off" changed to "30% off" everywhere, and a new CTA.

1. Open Edit project JSON.
2. Change the offer in each h1 and set every ctaText to "Shop the sale".
3. Press Apply. All six scenes update at once and the preview shows scene 1.

#Restore points

Restore points are the undo history. The account panel no longer lists them. Step back with Undo and forward with Redo in the header. Each step is a change, such as a scene generation, or a plain edit or checkpoint.

Undo walks back one step at a time. The steps you went back over sit on the redo stack, and Redo walks forward again. Make a new edit after undoing and that redo path is gone, as with any undo.

A few limits to know:

• The history holds the last 60 steps.
• It is kept in this browser, per project, and the most recent points survive a page reload.
• It does not follow you to another computer and is not shared with teammates.
• Very large items, such as a background video, are not part of the snapshots.

Worked example

You spent twenty minutes trying a darker palette and the client preferred the first version.

1. Press Undo until you are back at the edit just before the palette changes.
2. If you went one step too far, press Redo.

#Scene overview

The Scene overview lays every scene out as cards so you can plan the whole campaign at once. Open it with the grid icon (Scene overview) in the header of the Scenes strip; click it again, or the Canvas mode tab, to leave. Cards show the active format.

There are two areas:

• Selects, the scenes in play: the sequence that renders and that Sync sends to a review link.
• The scenes you keep outside Selects: alternates, older takes and ideas you are not ready to drop.

On the cards you can:

• click or double-click a card to open that scene;
• drag cards to reorder them, or to move them in or out of Selects;
• double-click a scene's name to rename it;
• Duplicate a card in Selects, or Delete it with the X. Delete removes the whole ad, its linked scenes included, after a confirm that says how many scenes go; rendered clips and finished sequences are kept, and Cmd/Ctrl+Z brings the ad back. To remove one linked scene only, delete it from the Scenes strip.

Linked scenes show as one card for the family unless Show linked scenes is on. The toolbar also holds Render timeline, the review link controls (Copy share link, Share by email, Sync), and switches for ad copy and demo metrics. Finished timeline renders are listed under Rendered sequences with a Download MP4 link.

#Saving and conflicts

A project saves itself as you work. Your own saves, from this window, never count as a change made somewhere else, even when a save's reply was lost or you reloaded mid-save.

Working alongside your agent

You can keep a project open while your own AI assistant edits it over MCP, for example "change all scenes to 0.2s". The assistant's change shows up in the open editor within a few seconds, with a note such as Updated by your agent: 12 scenes changed and an Undo that puts the project back as it was just before. If you have unsaved edits of your own, they are kept and merged with the assistant's change, as long as you did not both change the same thing.

Only someone else's open editor holds a project back from your assistant. It then says who has it open; this is an editing lock, not a permissions problem, and it clears about 90 seconds after they close the project.

If the project really did change somewhere else and the change collides with yours (you both changed the same thing), an in-app choice opens, This project changed somewhere else:

• Keep my edits (the default) downloads a copy of the other version, then saves your edits over it.
• Load the other version downloads a copy of your edits first, then opens the other version.
• Decide later closes the choice and changes nothing.

Either way, the version you set aside is downloaded first, so no work is lost. If a step fails, the choice says so and nothing changes.

#Send error to dev

When something goes wrong, send it straight to the Wildfield team from the editor. Open History with the clock icon at the top left of the preview. Every log, warning and error row has a small Send to dev button (the paper plane) at its right end, and Send error to dev at the foot of the panel sends the newest error, or the newest log entry when there is no error.

A short dialog shows what goes to support@wildfield.io before anything is sent:

• the entry you picked, with its time
• your account email and name (replies come to your email), the app build, browser, window and screen size
• the project: its id and name, design system, open scene, aspect ratio, scene and layer counts, version
• the last 30 History entries and the details of up to 20 errors from this session
• a copy of the project file, attached when it is under 2 MB, otherwise the project id so the team can open it

Access tokens, keys and signed links are removed before it leaves the browser, and again on the server. Add a line under What were you doing? if you can, then press Send. The toast gives a reference, such as Sent to support. Reference 7K3QM2PA, and the row shows it, so you can quote it in a reply. If Wildfield cannot send the email itself, your own mail app opens instead with the report already written and addressed to support@wildfield.io: check it and press send there. That copy leaves out the project file and is trimmed to fit, but carries the same reference.

Error details are kept in memory for the current session only. After a reload, an earlier error row still sends its History line, but not its full message.

#Costs and usage

The account panel (the profile icon) shows what your account used and what it was charged, for the last 7, 30 or 90 days or all recorded history. It has two parts.

Usage counts every operation your account ran in the period: each image generation, edit, retouch, outpaint, video, render, sound and Agent run, including the ones your API tokens ran. It adds them up at Wildfield prices in Australian dollars, with one line per kind of operation. These are the same numbers an admin sees for you in Usage & Costs. Admins also see the provider cost in US dollars.

Wallet is your credit balance and the money that moved through it: usage charges, refunds, top-ups, credit grants and adjustments, with the records underneath. Each operation is charged to the wallet as it runs, and a cancelled render gives its charge back as a refund. A billing exempt account has usage but no wallet charges, and so does every account while wallet charging is off; the note under Usage says which applies.

The time list in the same panel shows only the design systems you have tracked time on. Reset clears one, and its row goes until it tracks time again.

#API tokens

An API token lets an AI assistant or a script work in Wildfield as you. Through the MCP connection an assistant can list and create design systems and projects, edit scenes, generate and retouch images, render video and stills, and prepare review links, all in your account.

Create a token

1. Open the account panel and expand API tokens & assistant connection.
2. Type a name that says where it will live, such as "Claude MCP" or "Laptop CLI", and press Create token.
3. Copy the token straight away with Copy. It is shown once and never again: Wildfield keeps only a fingerprint of it, and the token is cleared from the page when you close the panel.
4. Paste it into your assistant's settings. The setup steps are in the MCP setup guide.

Each token acts as you, with your full access and your credits, and it does not expire. The list shows when each was created and last used. Revoke takes two clicks (the first asks you to confirm); the token stops working at once.

Make one token per assistant or machine. If one leaks, you revoke it and the others keep working, and "last used" tells you which one an unexpected change came from.