A factual release record for AgentHub.ai. Each note says what became available without turning the changelog into a sales page.
Release notes describe shipped work. Work still being designed belongs on the roadmap.
Release record
17 entries
Newest first. Dates follow the product release record.
01Change control
Approval opens and scope decisions now stay on the change record.
AgentHub records when a secure approval page is first opened and requires a human scope decision before a passed change can close.
The change record shows when the current approval page was first opened successfully. This records a page open, not who opened it.
After a passed verification, the operator records one scope outcome: the result matches the recorded scope, revised approval was captured, or the change closed with an unresolved scope difference.
Revised approvals require a reference. Unresolved differences require a note. The outcome and attribution remain in the audit record and client brief.
AgentHub does not send approval links, identify viewers, infer scope matches, perform implementation, or verify work automatically.
02Plans and access
Free access no longer expires.
AgentHub now starts on a permanent Free plan for one managed client, with capacity plans for consultants and agencies managing more client relationships.
Free includes unlimited changes and the complete request, owner, approval, change, verification, and client-brief lifecycle for one managed client. No credit card is required and there is no deadline.
Consultant is US$49 per month for up to three managed clients. Agency is US$99 per month for up to ten. Larger workspaces contact AgentHub.
When a lower limit takes effect, the owner chooses which clients remain managed. Other client records become historical and read-only; nothing is deleted and published briefs remain available.
Paid checkout never grants access by itself. AgentHub waits for signed payment confirmation before activating a paid plan.
03Client requests
Clients can submit requests without an AgentHub account.
Each client can have one reusable secure request link, and every submission arrives as a draft for consultant review.
A named client contact can submit a request through the standing link without signing in.
The request enters Request inbox as a draft until a person chooses the workflow and confirms or dismisses it.
AgentHub creates but does not send the link, and submission never approves scope or starts implementation.
04Activation
Every client change now starts in one place.
Start with the request, reuse the client and workflow when they exist, and create only the records that are missing.
Create → Client change is now the single path for new and existing client work.
Start with the client request, then select an existing client and workflow or create only the missing context inline.
A blank workspace can still reach a formal Requested change from five required decisions.
Existing workflow owners are preserved. The signed-in operator fills only missing technical or support ownership.
One transaction creates the minimum accountable record or creates nothing.
No connector is required, and nothing is sent, approved, implemented, verified, or published automatically.
05Activation
A real client change can now be started in one step.
New workspaces can create the minimum accountable record from five inputs without connecting an external tool.
Enter the client name, workflow name, runtime platform, client request, and client decision owner.
AgentHub creates the active client and workflow, records the decision owner as business owner, assigns the signed-in operator as technical and support owner, and files the formal request.
The new record opens in Requested state so approval, implementation, verification, and brief publication remain explicit decisions.
No connection is required, nothing is sent to the client, and AgentHub does not run or edit the workflow.
This new-workspace path was superseded August 7 by the unified Client change path for new and existing client work.
06Activation
Task-based Help and guided Ask AgentHub answers are live.
Users can now follow current setup guides or ask AgentHub how to complete a product task without first creating workspace records.
Seven focused guides cover the first client change, client and workflow setup, connected tools, request capture, approval and verification, client briefs, and product boundaries.
Ask AgentHub answers setup questions from the current Help Center and links to the full guide.
Operational questions continue to use stored workspace records and show the evidence behind the answer.
Empty workspaces receive a clear first-change path instead of a missing-record dead end.
Unsupported connections and unrelated questions are declined rather than guessed.
07Code-backed workflows
Code-backed automations now fit the same client change record.
Work built with Claude Code, Codex, Cursor, or Copilot can keep GitHub and deployment references attached to the client workflow and its change record.
Choose the platform where the automation actually runs. Work built with an AI coding tool can still run in n8n, Make, or Zapier.
If the code lives in GitHub, add its repository and deployment links without connecting the GitHub account.
Attach a pull request, commit, test or CI result, deployment, or other reviewed reference while a change is in progress.
Implementation evidence stays private by default. Only references explicitly marked as client-safe enter new client briefs.
Client workflows are now separate from optional Connected tools, and manual setup starts with only the client, workflow name, and runtime platform.
AgentHub does not ingest source code or AI conversations, run tests, merge changes, deploy code, or treat a technical artifact as passed verification.
08Client briefs
Scheduled client briefs now arrive as drafts for review.
AgentHub can prepare a private client brief draft on an agency-controlled schedule, while review, publication, and email remain explicit consultant decisions.
Set one weekly or monthly schedule for a client and name the contact who should receive the finished brief.
Scheduled runs prepare private drafts from the current operating record. Nothing is published or emailed automatically.
The consultant can edit the draft, publish a frozen brief, and then explicitly email its secure link.
AgentHub records when the email provider accepts the message. It does not claim delivery, opens, or clicks.
09Verification
Workflow changes now produce a focused verification plan.
When a change enters verification, AgentHub turns the recorded request and available safe structural difference into a short editable checklist.
Suggested checks focus on changed workflow status, systems, steps, routes, order, and schedule where recorded evidence supports them.
Partial or missing structural evidence produces an explicit source-platform review instead of invented detail.
Consultants can edit and save the plan to the immutable change history before recording a human pass, failure, or insufficient-evidence result.
The plan does not run a workflow, mark checks complete, or verify the change automatically.
10Connections
Connect once, then choose what belongs to each client.
n8n and Make connections now match the way consultants use shared automation accounts across internal and client work.
Connect an n8n account or Make team once at the AgentHub workspace level.
Assign only selected workflows or scenarios to one client at a time. Unassigned resources stay outside AgentHub.
Later refreshes update assigned resources and surface new choices without importing them automatically.
The n8n setup flow now explains that Cloud trial accounts do not provide API keys and points paid Cloud and self-hosted users to the supported paths.
11Version history
Workflow changes now show what changed.
After a baseline sync, AgentHub can compare supported workflow versions and show safe structural differences on the change record.
The first supported n8n, Make, or Zapier sync for a workflow captures a forward-only structural baseline.
Later supported changes can show differences in steps, systems, status, schedule, order, and routing where provider data allows.
AgentHub does not reconstruct workflow history from before the baseline was captured.
Credentials, parameters, field values, and execution payloads are excluded. Node and step names remain private workspace data.
12Access
30-day access opened.
AgentHub introduced 30 days of full access with no credit card. This offer was replaced August 13 by the permanent Free plan.
New workspaces could start with one live client workflow without requiring an onboarding call.
There was no automatic charge at the end of the access period.
After 30 days, workspaces could continue for US$99 per month or remain read-only.
The permanent Free, Consultant, and Agency plans superseded this offer on August 13.
Authentication and billing screens now use the current AgentHub brand.
13Intake and AI
Slack requests and Ask AgentHub are live.
Selected Slack channels can feed likely client requests into a review inbox, and operators can ask questions against records stored in their workspace.
Only explicitly selected Slack channels are monitored.
Likely requests arrive as drafts and require human review before filing.
Ask AgentHub cites stored records and leaves missing information visible.
AgentHub does not approve, run, or edit a live workflow.
14Operations
A clearer Operations Desk
The main workspace now opens on the work that needs attention instead of a generic dashboard.
A redesigned Operations Desk for active requests, approvals, incidents, and client commitments.
Light mode is now the default application appearance.
Navigation and record states were tightened around post-launch client operations.
15Inventory
Workflow inventory without connector lock-in
Agencies can bring live workflow records into AgentHub even when a direct connection is not available.
CSV workflow inventory import with validation before records are created.
Clearer connection states when a provider token is revoked or stale.
A refreshed client operations workspace for ownership, health, and open work.
16Connections
Connections and the first narrow public API
The build gained additional ways to connect workflow and business context without handing outside tools database access.
Read-only inventory connections for Make and Zapier.
HubSpot connection flow for client context.
Workspace API keys plus narrow endpoints for clients, workflows, and change requests.
Zapier Manager alerts can open an AgentHub incident through a signed webhook.
17Change control
The operating record closes with proof
A client change can now move through the accountable lifecycle and become a client-facing brief.
Request, ownership, approval, implementation, verification, and closure stay on one record.
Guided client brief creation from live workspace records.
