HubSpot just dropped a look at their vision for the "agent era," and if you are an operations nerd or a developer who lives inside tools like Claude Code, Claude Cowork, or OpenAI Codex, this one is going to make you sit up.

But first, the bad news: It is currently a private beta, and many users, including me, as I write this, are still stuck on the waiting list staring at a closed door.

However, what they are building is absolutely worth putting on your radar while we all wait for access.

It is called the HubSpot Agent CLI, and the simplest way to think about it is this: it brings your CRM data directly into your AI agent workspaces so you can automate repetitive, bulk, and scheduled work before you even get to your desk in the morning.

Instead of jumping into HubSpot to build a massive, complex workflow or manually filtering through lists, you can just tell your AI agent to do the heavy lifting using standard prompts.

Imagine being able to tell your workspace:

The big idea here is optionality. HubSpot is trying to build an open ecosystem where your AI agents aren't locked into just one infrastructure, they can use whatever tool is best for the specific task at hand.

When you do finally get the golden ticket into the beta, setup looks pretty straightforward. You copy a quick installation script (using a curl command for Mac/Linux or an irm command for PowerShell) directly into Cowork or Codex, run hubspot auth login to link your portal, and start prompting.

If you want to get on the list to try it out, a Super Admin in your account needs to go request beta access.

Hopefully, the gatekeepers let us all in soon so we can actually see if it lives up to the hype.

Use Workflow Comments Before Your Automation Becomes an Unsolved Mystery

If your HubSpot portal has more than one person building or managing automation, your workflow tool probably contains a few hidden logic traps that everyone is terrified to touch.

You know the vibe:

"Why is there a random 4-day delay right before this internal notification?"

"Who added this specific enrollment branch for contacts with a lifecycle stage of Opportunity?"

"Is this webhook actually doing something critical, or will deleting it break the entire tech stack?"

"Do not touch this action, John built it two years ago and he doesn't work here anymore."

This is where the workflow commenting tool is quietly very useful.

Instead of relying on a completely separate Slack thread, an outdated Google Doc, or the emotional memory of your marketing team, you can drop context-rich notes directly onto specific workflow actions.

Think of workflow comments like a built-in paper trail that explains the why behind your logic:

Why did we change this property update? What edge case does this specific branch protect against? Who approved this routing logic? Is this action temporary for a seasonal campaign, or is it a permanent fixture holding up the CRM with duct tape and vibes?

This is especially helpful for keeping everyone in the account on the same page without leaving the builder. Instead of messaging a teammate to say, "Hey, can you look at the new deal routing workflow?" and having them hunt through the portal, you can @mention them directly on the exact action that needs their eyes. They get a notification, jump straight to the correct step, and reply in a clean, threaded conversation right inside the canvas.

My favorite ways to implement this:

That tiny bit of structure turns a workflow from a terrifying black box into a transparent, shared map that the whole team can confidently collaborate on.