Changelog

PatchyHub now has three public plans: Free, Pro, and Agency. Free keeps the core documentation workspace and unlimited team members. Pro adds AI management for up to 3,000 assets per month. Agency raises that to 15,000 and includes client-delivery rights. Existing paid and complimentary workspaces keep their previous unlimited coverage while the new model rolls out.

The limit is a monthly high-water mark of unique assets placed in AI-managed modules. Reaching it pauses new model-based asset analysis, not the rest of PatchyHub: imports, deterministic features, documentation, chat, and existing results keep working.

Imports and module rebuilds no longer leave an account looking mysteriously empty while PatchyHub works. A floating status tray stays out of the way while major account organization is running, individual assets show a light processing state, and the System page makes it clear when the module structure is still being built.

The small GHL badge beside an imported item now opens that exact item in GoHighLevel when a direct link is available. You can still hover over the badge to see or copy its ID, but the main click finally does the useful thing.

Imported workflows now have a full-screen visual inspector. Open a workflow and choose “View workflow” to follow its triggers, actions, waits, branches, and jumps on a map while reading the details of each step beside it. The view is built from the workflow data PatchyHub actually imported, so missing information is shown as missing instead of being guessed.

After creating an account, PatchyHub now shows what happened to the confirmation email. The page updates automatically when the email provider accepts, delays, or rejects it, then gives you the right next step instead of sending you back to the sign-in form to guess.

A new public Use Cases library shows how PatchyHub fits into real GoHighLevel work before you have to translate a feature list into a plan. It includes 15 focused examples for agencies, freelancers and VAs, support teams, and in-house teams.

Cleanup now ends with one exact list of everything marked for deletion. You can remove items, return to unanswered decisions, see anything still referenced elsewhere, and review plain-language risk warnings before approving the batch. Live deletion now covers 13 supported GoHighLevel item types.

PatchyHub now has a guided cleanup flow for finding and removing GHL assets that look unused, empty, deprecated, or left behind. It reads the whole selected system, groups related clutter together, explains the evidence in plain English, and asks you to make one decision at a time. Patchy's AI review also reads the system charter, so it can judge an asset against what the account is actually supposed to do instead of treating every lonely workflow as junk.

Deletion is deliberately harder than clicking the wrong checkbox. PatchyHub shows the exact list, blocks groups that still have outside references, requires a fresh Browser Connect handoff, and keeps progress and history after the run. Confirmed deletions are reflected in PatchyHub too, so the documentation does not keep pretending a deleted GHL asset exists. The first live cleanup types are workflows, forms, surveys, email templates, and snippets.

Paid workspaces can now connect PatchyHub to Claude web through MCP. Claude can read the documented systems, modules, assets, dependencies, freshness warnings, and system operating context in the workspace you approve. It can also inspect likely change impact, generate build briefs, and keep a work journal against planned updates. That gives Claude the map before it starts giving account advice, which is a fairly useful ordering of events.

The connection is workspace-scoped, revocable, and explicit about its limits: it reads PatchyHub's imported documentation, but it does not inspect live contacts or make changes directly in GHL. Important results should still be confirmed against the current account before anyone acts on them. CSV exports also got an AI-readability pass for anyone working outside the connector.

PatchyHub now asks for a system account charter before opening the rest of a newly imported system. The charter records who the system serves, what success looks like, and what must stay separate. Every workspace member can edit it, and Patchy uses it as the human source of truth when analyzing the account or handing context to an external builder. Structure without intent is just a very elaborate pile.

Browser Connect also captures more of the evidence hidden inside GHL. Email copy, form fields, and survey fields can now contribute to dependency mapping, workflow pagination has been repaired for larger accounts, and object-schema links are connected more reliably. Patchy's module builder also stops collapsing large accounts into a single giant module.