What’s new

Your client book goes deeper. The API can now add and read meeting notes on a person, import a list of people at once with the same duplicate handling as the CSV import, show how a client has engaged with what you shared (opens, time on each slide, submissions, comments), and list the projects and decks they are connected to. Research is there too: fill in a client's empty fields from the web with the research brief filed as a note, and find out which firms their organisation has worked with, cached so the second colleague at the same company costs nothing.

Studio is in the API. Read and update the firm profile, and have the interview answers or a spoken transcript structured into one. Manage the team's people, past proposals and work items, with the same résumé, proposal and case-study extraction the Studio tabs use. Repair a proposal's extracted text in the background and check on the job. Read and save the brand kit, and pull a brand from a website for review.

Claude knows your firm. With the Studio permission, Claude can read your firm profile, your team and your past proposals, including the full text of a past proposal's sections, so drafts start from what you have actually said and done. With the AI permission it can research a client or their company on your behalf, spending your credits as the app would.

Every AI action is priced as in the app. Each one checks your balance before it calls a provider, charges afterwards, and records that the API or Claude made the request.

Share a deck or project from any tool. The API can now return the public link for a deck or project, or send that link by email to named recipients with a note, using the same email the app sends. Recipients are let straight through the share gate, and a retried request never sends the email twice.

See who opened what. For any share link, read the open count, the people who identified themselves at the gate (name, email, role, when they last looked), and each open with its city and country, newest first. Set or clear a password and an expiry, or turn a link off, which makes the content private again while keeping its history.

Comments on decks are in the API. List a deck's comments and feedback newest first, filter by slide or by resolved state, add a comment pinned to a point on a slide or reply to an existing one, edit your own, resolve threads, and delete. Comments made through the API appear in the editor like any other, and the deck's owner and anyone you mention are notified as usual.

Claude can share and comment too. With the new sharing and comments permissions, Claude can hand you a deck's share link, email it to a client, tell you who has opened it, read the feedback on a deck, and leave a comment on a slide, all as you.

Combine copies that share a name. When your Library holds several files with exactly the same name (import the same PDF twice and every picture in it arrives twice), the All Assets tab offers to combine them. Each name keeps one card showing its newest copy, and the older copies become its earlier versions, numbered by date. You review the list first, with a preview of every copy, and can leave any name out. Copies that came from different projects start unchecked, since they're often different files that happen to share a name. AI generations, stock photos and drawings are never combined. No file is deleted, and slides that use an older copy keep showing it.

Version history in the Library. A file with earlier versions carries a small version badge in the top-left corner of its thumbnail, in your Library, in a deck's Library and when you open the file. Library cards also have a light outline now, so each file reads as its own tile. Choose Version history from its menu, or History beside its version when you open it, to see every earlier version and restore any of them. Uploading a file from the Library with the same name as one you already have now adds it as a new version too, instead of a second copy. That includes a file you downloaded from Foveate and are bringing back, even though its download gained a "foveate-" prefix or a file extension, and a video that came down as an MP4.

Drop files onto your Library, and keep working while they upload. Drag files anywhere onto All Assets to upload them. The Upload window can now be closed while files are still going; they carry on in the background, with their progress at the bottom of the page. A video's percentage now climbs steadily from the start of the upload through processing, instead of sitting at 0% and then jumping around. Each file in the Upload window shows a preview of itself.

No more blank "FILE" cards for pictures. Files whose names start with "._" are hidden metadata a Mac saves beside every file in a zip, not pictures, so they could never show a preview. Your Library now hides them, offers to delete them in one click, and skips them when you upload. Real images that arrived without a file type, which happens when you drag them from a zip or a network drive on Windows, now show their preview too.

Download saves the file. Download on a Library card, or in the file viewer, now saves the file itself under its own name instead of opening it in a new tab. Videos come down as MP4 files rather than an unplayable streaming link, and the first download of a video takes a few seconds while its file is prepared. Download buttons in chats, which did nothing, now save the file too. The card's menu also shows an icon beside each action.

Downloading and extending videos works again. Since September 21, saving a generated video failed for any clip that didn't already have a downloadable copy, with a message that the file wasn't ready. Extending such a clip into a longer one failed the same way. Both work again. If a video truly can't be made into a file, you're now told that directly instead of being asked to try again.

Sort your Library. All Assets can now be sorted by recently updated, recently added, oldest first, name (A–Z or Z–A) or size, and your choice is remembered. Names sort the way people read numbers, so "image 2" comes before "image 10", here and in a deck's Library. Long names also keep their ending in view on each card, so files that differ only at the end are easy to tell apart. The Type filter shows an icon beside each type, the same icon each card carries, and drawings now show a drawing icon instead of an image one.

Projects are in the API. Integrations can now list your projects, read one in full, create new ones, edit them and delete them, with the same permissions the app enforces: people on a project see it, editors change it, only its creator deletes it. Every field the project page edits is there, including the pursuit stage, the fee and its currency, the decision date, the outcome, the timeline, the deliverables and the team. Moving a pursuit to won or lost stamps the decision date and freezes its exchange rate, exactly as it does in the app.

The pipeline, activity and people too. A single call returns your pipeline as pursuits with their stage, fee, dates and engagement score. Each project's activity stream (views, downloads, opened files) pages newest first, so a CRM or a Slack bot can follow what stakeholders are doing. A project's linked clients come back as client-book records.

Upload to your library from anywhere. Ask the API for an upload link, send the file straight to storage, then register it as a library asset, attached to a project if you like. Images, PDFs, 3D models and documents go to Foveate's storage; video goes to the streaming service the app uses. List, rename, attach, detach and delete files the same way.

Duplicate a deck. One call makes a fresh, unshared copy of any deck you can see, owned by you, optionally under a new name.

Claude can work with projects and files. Connect Claude and grant the new project and library permissions, and it can list and open your projects, create one, move a pursuit's stage or update its fee, and browse your library files, all from a chat.

Upload a file with the same name and it becomes a new version. In a deck's Library, or when you attach images or videos to the deck assistant, a file with exactly the same name as one you already have (say, a corrected "logo.png") now replaces it as a new version instead of adding a second copy. Every place in the deck that showed the old file switches to the new one straight away, and the editor's normal undo puts the old one back on your slides. Other decks keep the version they're using. Generic names like "image.png" (what a pasted screenshot is called) are never treated as versions of each other.

Version history, with restore. A file that has been updated shows its version number in the deck's Library, and its menu there has Version history. From there you can bring back any earlier version: it becomes the current version again, and the deck switches to it. Nothing is deleted along the way.

New accounts start from what they already have. The first time you sign in, Foveate offers to bring in something you've already made: a PowerPoint, a PDF or a Word document, or your brand from your website. You can skip it. Either way it's only asked once, and Import is always there when you create a deck. If you joined through a team invite, you won't see it, since your team's work is already waiting for you.

Resuming a saved deck draft works again. Choosing to pick up an unfinished deck draft where you left off no longer fails, and changing a draft's format once again updates its slide layouts to match.

The whole Foveate API is now described in one machine-readable document. Fetch app.foveate.com/api/v1/openapi.json to get every endpoint, its permission, its rate limit and the exact shape of every request, generated from the same rules the API enforces. Point an API client, a code generator or an AI assistant at it and it cannot send a request the API would reject.

Every API response now tells you how much of your rate limit is left. Look for the X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers on any call, so an integration can pace itself instead of discovering the limit by hitting it. Browser-based tools can call the API directly too.

Filter your decks by project. Listing decks with a project id returns only the decks filed in that project, with paging that stays inside the filter.

Long-running work can now run in the background. When an API operation takes longer than a request should, the API answers immediately with a job you can check on, and Claude gets a matching tool to check the same job from a chat. No operation uses it yet; it is the groundwork for the ones that will.

One set of permissions everywhere. The permissions you pick when creating an API key and the ones an app like Claude asks for on the approval page are now the same list with the same wording, so connecting Claude can also grant it access to your client book.

Published Claude artifacts play live on your slides. Paste the link to a published Claude artifact onto a slide (the page link, or the code from Get embed code) and it goes on the slide as the working app, not a picture of it. Your audience can click and type in it while you present, and on your share link. Claude only allows an artifact to be embedded on sites its author has approved, so in Claude open Get embed code and add the address you use Foveate at to Allowed domains.

Paste an artifact's code and it runs on the slide. Copy an artifact's code in Claude and paste it onto a slide: a whole web page or a React component becomes a live code widget that runs right there, libraries included. This works for any artifact, including shared links that Claude won't let other sites embed. Before, the code landed on the slide as a wall of text.

When an artifact can't play here, you get a link and a reason. A shared artifact link, or a published one that hasn't approved this site, goes on the slide as a link card that opens the artifact in Claude, instead of an empty box. In the editor, the card and a short notice tell you what to change in Claude to make it play live.

Bigger changes start with a plan. When you ask the deck assistant for something that reaches past the slide you're on (rewriting the whole deck, personalising it for a client, reworking several slides), it shows you a plan before touching anything: each slide it would change, what it would change, and why. Every step starts ticked. Untick the ones you don't want and press Apply, and it makes only those changes. Cancel changes nothing. To adjust the plan instead, type what you'd like different and it comes back with a revised plan. Small, specific requests, like a change to the slide you're on or "make every heading 48px", still happen straight away.

Keep or revert each slide on its own. After the assistant edits your deck, its reply lists every slide it changed. Open a slide to see the old and new text side by side, then keep it or revert just that slide, leaving the others as they are. Keep all and Revert all are there when you want to decide in one go, and each revert can itself be undone with the editor's normal undo.

Plan first, every time, if you prefer. A new switch beside the assistant's message box makes it propose a plan before any change at all, even a one-word edit on a single slide. It stays on until you turn it off.

Mentioning a client tells the assistant who you're writing for. In the deck editor's assistant, typing @ and a client's name used to be read as text to find on your slides — ask it to "alter the text for @Jim" and it would search the deck for Jim, find nothing, and ask what you meant. It now knows that person is your audience. It rewrites the copy on the slide you're on so it speaks to them, drawing on what their client profile says they care about, while keeping every fact the same and leaving the design exactly as it is.

Ask for the whole deck and it suggests before it changes. If you ask it to personalise an entire deck for someone, it doesn't rewrite everything at once. It shows you a plan — which slides would change most for that person, what it would change on each and why — and waits for you to choose which of those changes to make.

It tells you when it doesn't know enough. If the person you mention has no client profile yet, or only a thin one, the assistant says so and personalises only from what's actually known about them — their role and company — rather than guessing at what they want.