What’s new in Patchy Cloud

Patchy Cloud’s new features and improvements, newest first, in the words people see in the app. The most recent shipped on October 29, 2026.

18 releases51 changesUpdated

5 changes

  • New

    Pages published from one HTML file can run script

    A page your agent publishes from a single HTML file can now run its own script, so it can sort a table, switch tabs or draw a chart, and it can be up to 10 MiB. It still has to carry everything it shows: an image, font or stylesheet loaded from another address is refused at publish and named, so put it in the file instead, for example as a data: URL.

  • Improved

    Pages and Tools sort by what a patch runs

    On Home and All patches, a patch that runs only in your browser is now listed under Pages, and a patch with its own server code is listed under Tools.

  • Improved

    Company data goes through a patch’s own rules

    A patch that reads a company connection such as Postgres, PostHog, Pidgeon or Attio, another patch’s shared data, or the member directory now does it from its server code, where the patch’s rules hold and nobody viewing it can go around them. A patch that runs only in the browser reaches its own tables and files. One that already read any of these stops getting that data until it moves to server code, and Patchy tells your agent what to change.

  • Improved

    Patches with server code open faster

    When you land on Home or All patches, Patchy now gets your company’s server and the three patches you open most ready in the background, so opening one is quick. A patch you just used stays ready for ten minutes instead of one, loading a patch onto its server takes about a third of the time it did, and each company’s server has twice the processing power.

  • Improved

    Your agent checks patches several times faster

    New patch repos now use TypeScript 7 and Oxlint, which check a patch several times faster, and the patchy download is about a third smaller. The next time you publish an existing repo, patchy asks you to move it over first and names the one command to run. Your published patches keep working the whole time.

2 changes

  • New

    Patches can read your Attio CRM

    If your company keeps its customers, deals and pipelines in Attio, an admin can connect the workspace from Integrations with a read-only key. Patches can then find, sort and open its records and lists, shaped to your own objects and fields, and nothing in Attio can be changed through Patchy. While your agent builds one, it reads your real CRM.

  • New

    Patches can read and answer a company email address

    If your company’s mail runs through Pidgeon, an admin can connect one of its addresses from Integrations, choosing Read or Read and send. Patches can then read that inbox and, with Read and send, reply and send from it, up to 200 sends a day; mail Pidgeon holds for someone’s approval shows as waiting, never as sent. While your agent builds one, it reads the real mail and sends nothing.

6 changes

  • Improved

    A sidebar that keeps your things and the company’s apart

    Every page now has a sidebar: Home, All patches and Your agents, then your company’s People, Integrations and Agent access. Search sits at the top, and What’s new and your name, which opens Sign out, sit at the bottom. On a phone, Menu opens the same list. Pages are calmer too, with fewer heavy borders, shadows and badges.

  • Improved

    Your agents shows what’s connected first

    Your machines is now Your agents. It starts with the computers that publish as you and the apps that use your company’s tools as you, each with a button to end it. Add a computer and Connect an app open the steps only when you want them, and Disconnect everything says what it ends and asks once before it does.

  • Improved

    People, Integrations and Agent access each have a page

    The Company page is now People, with Invite people in its toolbar. Agent access has a page of its own that says what turning it off does before you do it, and the page for your company’s databases and analytics is now called Integrations.

  • Improved

    Patches go by their real names, and one click opens them

    Lists show a patch’s title, like Spend Requests, instead of its short name, and clicking a patch opens it wherever it’s listed. Its menu has About, Copy link and the rest.

  • New

    Patchy says what just happened

    After you revoke a computer, invite someone, change who can open a patch or anything like it, a line at the top of the page says what was done.

  • Improved

    Making a patch public asks first

    Choosing Anyone on the internet now shows one step that says anyone with the link can open it without signing in, so nothing goes public by accident.

4 changes

  • New

    A Final step to connect your AI agent

    Until your agent is connected, Home opens with a short Final step: give your agent one line, then confirm it’s you. It follows along as your agent works, showing when it opened the line, when it’s waiting for you and when it’s connected, and if something goes wrong it says what happened and gives you a new line. It comes back each time you sign in, for your first week or your first three sign-ins, whichever lasts longer, and Later puts it away until next time.

  • New

    Confirm your computer without leaving Home

    When your agent asks to connect, the Final step shows its code and asks if it’s yours. Check it against the code your agent shows, then confirm right there, with no second tab. If you didn’t start it, Not me turns it away and nothing is connected.

  • Improved

    Setting up ends with your first page

    When you set Patchy up with your AI agent, it now finishes by publishing a welcome page in your company’s look, so you have something live straight away. Then it suggests a first tool to build, based on what it knows about your work.

  • Improved

    The logo takes you Home

    Clicking the Patchy logo at the top of any page now takes you to Home, and Patches opens the full list of your company’s patches.

6 changes

  • New

    Your AI agent can use your company’s tools

    Connect Claude Code or Codex to Patchy once, with the steps on Your machines, and it can find your company’s tools and read or change them for you. It reaches only a tool’s agent tools, the parts made for agents, and it can’t do anything you can’t. Before it connects, Patchy asks you in your browser, showing what it will and won’t be able to do.

  • New

    Admins choose whether agents can use the company’s tools

    Agent access, at the foot of the Company page, starts off. An admin turns it on to let everyone connect their own agent, or off to refuse every agent until it’s back on, without ending anyone’s connection. Everyone can see whether it’s on and who changed it last.

  • Improved

    Your machines shows your agents too

    Your machines now shows how to connect your agent, and lists the agents you’ve connected beside your computers, with when each was last used and a button to disconnect it. Revoke all machines is now Disconnect everything, at the foot of the page. It’s always there, and it disconnects your agents as well as your computers.

  • New

    See what agents can do with a tool

    A tool’s page now lists its agent tools beside the Overview, under What agents can do: what each one does and whether it reads or changes anything, with a link to connect your agent.

  • New

    The log says when an agent made a change

    A tool’s log now names agent work as the person via their agent, such as “Jordan Lee via Claude”, so you can tell someone’s own changes from their agent’s. It shows in the Log tab, the tool’s recent activity and the log your agent reads.

  • New

    Your agent can make a tool ready for agents

    When your AI agent builds a tool with server code, it can now add agent tools: what people’s agents may read and change in it, under the tool’s own rules. It can try them on your computer before publishing, and publishing lists them and says if agent access is still off.

6 changes

  • New

    Your agent can read a tool’s log

    When a tool your agent published goes wrong, the agent can now read the tool’s log itself, errors included, instead of you copying them out of the Log tab. Ask it to look at what happened, fix the tool and publish again. It sees the same log you do as the tool’s owner or a company admin.

  • Improved

    Tools with server code answer faster

    A tool your agent built with server code now keeps its server ready while you have it open, so switching screens or saving after a pause no longer waits for it to start again. Each call also does less work before it reaches your data, and a screen runs two of its lookups at once instead of one after another.

  • Improved

    Your company’s tools and pages open sooner

    Opening a tool or page no longer waits for Patchy to check who you are before it starts loading its data. Its files come from memory and arrive compressed, and the parts every tool shares stay in your browser between visits.

  • Improved

    Publishing is quicker

    When your agent publishes a tool that uses your company’s look, Patchy checks the look is current without downloading all of it first.

  • Improved

    New tools start with a tidy layout

    A tool your agent starts now opens as a centred column with room around it, instead of text pressed into the top-left corner.

  • Improved

    Your usual is easier to scan

    The patches in Your usual on Home now show just their name and why they’re there. On a mid-sized window, Home’s rows fit their column instead of breaking names across lines.

7 changes

  • New

    Home puts the patches you use first

    Signing in now opens Home. Your usual shows the four patches you open most, so you’re one click from them, then come your company’s tools and its pages, with new pages marked until you read them. Search covers every patch by name, what it does or who made it, and when nothing matches, Home gives you a line to ask your AI agent to build it.

  • New

    Every patch in one list

    All patches lists everything your company has published, with tabs for tools, pages, your own, and retired and deleted ones, plus a search. Each row’s menu holds its actions. Owners and admins also get a Needs attention tab for patches whose owner has left or that are about to be deleted for good.

  • Improved

    Each patch’s page leads with Open

    A patch’s page now starts with Open and its address, then tabs: Overview and Versions for everyone, and Log and Settings for its owner and admins. Settings holds the description, who can open it, and retiring or deleting it.

  • New

    See when your tools are failing

    If a tool you own with server code had calls fail in the last day, Home tells you which, with a link to the failures in its log. Owners and admins also see each tool’s health in All patches.

  • Improved

    Your company’s look is easier to get right

    When your agent previews a first company look, it can now compare it with the look your tools use today, both shown whole in one screenshot. A logo that browsers can’t show is refused when the look is published instead of appearing broken in every tool. Restoring an earlier look now records who restored it and why.

  • Improved

    Forms follow your look’s error states

    Tools your agent builds now show a field with a problem, and a disabled one, the way your company’s look styles them. The example looks your agent learns from got the same fix.

  • Improved

    Clearer answers when a publish goes wrong

    When a page can’t be built because something it uses is missing, your agent is told exactly what. A page whose font or stylesheet won’t load is published with a note naming it, and a file too big to save says so.

2 changes

  • Improved

    Set up Patchy however you ask

    Your AI agent now sets Patchy up on your computer whatever words you use, not only the line from the guide, and still sets up your company’s look. If you give your agent nothing but Patchy’s address, the sign-in page now shows it the line to start from, so it no longer has to guess.

  • Improved

    Claude Code can know Patchy is your company’s own

    If you use Claude Code, setting up Patchy now offers to tell its auto mode that Patchy is your company’s own service, so it doesn’t treat publishing a page as sending it outside the company. It asks you first, applies to all your projects and can be undone. If auto mode still stops a publish, your agent explains why and asks you what to do.

6 changes

  • New

    Tools can show your PostHog data

    An admin can now connect your company’s PostHog project on the Connections page. Your AI agent can then build dashboards and tools that read its events and numbers. They only read: nothing a tool does changes your PostHog data. While your agent builds, it works from the real data, so what you try is what your team will see.

  • Improved

    The Connections page stays clear with one connection or thirty

    Each of your company’s data connections is now one row in a table that shows what it reaches, whether it’s working and which tools use it. New ones start from Connect a source, and each connection’s own page keeps its actions together. If you need a source Patchy doesn’t connect yet, the page tells you how to ask.

  • Improved

    Find anyone on the Company page

    The Company page is now one table of people and invites, with a search box and tabs for admins, invites and deactivated people. Invites that need you, because the email didn’t go out or the invite expired, come first with a Resend button beside them. Each row keeps its actions in one menu.

  • New

    Invite many people at once

    Paste up to 50 email addresses into the invite box, separated by commas or new lines, and each person gets their own invitation. If any address is wrong, nothing is sent and your list stays in the box so you can fix it.

  • Improved

    See a sample tool in your look before you approve it

    When your agent captures your company’s look, it now also builds a small sample tool in it, with your logo, a filter, a table and buttons, and shows it beside the sample page. You see how your tools will really look before you agree, and the agent fills any gaps the sample finds in the look’s brief.

  • Improved

    Publishing the company look says who it’s for

    When an admin’s agent publishes the company look, it now says the look is for everyone at the company and that colleagues’ agents use it for new pages and tools with nothing to set up. It no longer offers to keep a copy of the look’s files, since Patchy already holds them.

6 changes

  • New

    Your tools can look like your company

    An admin’s agent can now publish a company look: your colours, type, spacing and a short brief on how your brand reads. Every new patch starts in it, so the first page your agent builds already looks like you, and your agent sees the brief before it styles anything. Patchy never enforces it: a Halloween page or a page for a client can look however you ask. Admins can publish a new revision or go back to an earlier one, and anyone can ask their agent what the company look is.

  • New

    Preview a look before you publish it

    Your agent can render any candidate look on a fixed sample page, headings, buttons, a table, a form, badges and colour swatches, and show it beside the current look, so you judge a picture rather than a stylesheet. The same checks that publishing runs are listed with the preview, so problems get fixed before anything changes for your colleagues.

  • New

    Setting up Patchy sets up your look

    When you create a company, your agent guesses your website from your email address and asks whether your tools should look like it. If you say yes, it captures the look, shows you the sample page, and publishes it, so your welcome page and every tool after it start in your company’s look. People who join later are told their tools will use it, with nothing to set up.

  • Improved

    Patches hear when the look changes

    When an admin publishes or restores a look, each patch picks it up the next time its agent starts or refreshes it, and says what changed and who changed it. Publishing a patch that is behind warns you and ships the look it was built with, so nothing goes live in a look nobody has checked.

  • Improved

    Static pages can use embedded fonts

    A static page can now carry its own font inside the page, so a company look’s typeface shows on every tier. Fonts fetched from other sites stay blocked.

  • New

    A guide to your first patch

    Until you have a patch of your own, Patches opens on a short guide: what Patchy is, the line to give your AI agent, and what to ask it for, each with a Copy button. It moves on as you go and steps aside once your first patch is live.

1 change

  • New

    See what’s new in Patchy

    A bell beside your name shows a dot when something has shipped since you last looked. Open it for the latest changes, or choose See all changes for the full history.

That’s every release with something new or improved. Fixes and behind-the-scenes work are listed only inside Patchy Cloud.

Patchy Cloud is in beta.

It’s free today, for companies in the US, in Chrome on a computer. Join the waitlist and we’ll let you in as soon as we can.

What happens next

  1. You join the waitlist Your work email is all it takes.
  2. We email your invitation Sign in, name your company and invite your team.
  3. You paste one line into your agent Set up Patchy using https://cloud.patchyhq.com/llms.txt

Questions? Email us.