What’s new

Library search looks past file names. Searching in the Library, in the deck editor's Library panel, or in the picker you attach files from on Home now also checks:

• the prompt an image or video was generated from;
• the project a file came from;
• a stock photo's credit;
• the kind of file.

So "atrium" finds an atrium render even when its file name is a string of letters and numbers, and "clip" finds your videos. Once you've typed three letters, a word also matches the start of longer words. Common building terms find each other, so "housing" also finds "residential".

Search your notifications. The Feed page and the expanded notifications window from the bell have a search box. It matches what each notification says on screen, including a deck's current name after it has been renamed. Searching the old name still finds the notifications from before the rename.

Studio belongs to the whole firm. Owners and members of a workspace can edit its Studio. Guests can see it but can't change it, and Studio tells them so at the top of the page.

Insights opens faster. Insights now loads only what it shows, so it opens faster, most of all in workspaces with a lot of content.

Claude can find and open your walkthroughs. With the new 3D walkthrough permissions, Claude can list your splat scans, 3D models and 360° tours, filter them by project or kind, and look inside one: its files, its saved views and a link to open it in Foveate.

Build a walkthrough from your library. Ask Claude to turn a model, a scan or a set of panoramas already in your library into a walkthrough. One GLB or GLTF file makes a 3D model walkthrough, one splat file makes a scan walkthrough, and several images make a 360° tour in the order you give them. Claude can also rename a walkthrough, file it in a project, or make it public.

Share walkthroughs and read their feedback. Claude can get a walkthrough's share link or email it to people, just like a deck. Sharing a walkthrough makes it viewable to anyone with the link. Claude can also read the comments left on a walkthrough, including which saved view each one is about and whether it has been resolved.

For developers. The same features are in the Foveate API, which can also delete a walkthrough and post comments on one. An existing Claude connection needs to be reconnected to approve the new permissions.

Ask Claude what's new. With the new notifications permission, Claude can read the same notifications as the bell in Foveate: who opened your share links, new comments and mentions, access requests, and projects you were added to. Ask "what did I miss today?" or "has anyone opened the Harbor deck?" and Claude answers from your feed, with a link to what each one is about. Access requests have no link; you still approve them in Foveate. Claude can show only what's unread, one kind of notification, or everything since a given time. Reading notifications in Claude doesn't mark them as read in Foveate.

Approve it when you reconnect. Notifications are a new permission, so a connection you made earlier can't read them yet. Settings lists it as not granted; reconnect Claude and approve it to turn it on.

Claude can see and update your clients. With the clients permission, Claude can search your client book, open one person's record, add someone new, or update their details from a chat. Adding a person who is already in the book returns that record instead of a duplicate, and an edit Claude makes is kept as your edit, so a later CRM sync leaves it alone. Together with decks, projects, files, sharing, comments and Studio, that makes twenty-seven tools Claude can use on your behalf.

A clearer permission screen. When you connect an app, the permissions it asks for are grouped by area, such as Decks, Projects, Clients and Studio, so a long request reads as a short list of what the app can reach. An app that asks for less shows only what it asked for.

Connected apps show what they cannot do yet. As Foveate adds new permissions, an app you connected earlier keeps working with the ones you already approved. Settings now lists the permissions that app was never granted, with a note that reconnecting it is how to add them.

Claude understands Foveate better. The instructions Claude reads when it connects now describe every area of the product and which actions spend credits, so it looks before it writes and asks before it spends.

The API is documented. The full contract, every endpoint, its inputs and its permissions, is published as an OpenAPI document that stays in step with the code, and a guide to authentication, conventions, permissions and background jobs sits alongside it.

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.