August 2026: Local agents and commercial licence distribution
August brings two different developments into the same decision: agents operating a local ComfyUI installation, and a commercial licensing offer around an open-weight model. Local execution, open weights and commercial permission must remain separate questions when assessing either announcement.
Dated announcements
On 18 August, Jo Zhang and Rob announced an open-source local Comfy MCP connection alongside Cloud MCP. The post describes discovering installed hardware, models and nodes and operating workflows across local and cloud routes. Comfy: open-source local MCP (2026-08-18; company announcement).
On 27 August, Josiah Villegas announced Comfy as an official reseller of MiniMax H3 commercial licences for local use. The post distinguishes local licensing from Cloud use and excludes selling H3 access through an inference platform or marketplace from the described licence. Comfy: MiniMax H3 licence reseller announcement (2026-08-27; company commercial announcement).
Funding and valuation status
No additional financing announcement is established for this month by the reviewed sources. This is not proof that no financing occurred. See the dated funding register; past totals and valuations are not new monthly raises.
What this changes: editorial analysis
Our interpretation is a wider execution and commercial boundary. An agent that discovers local resources can make a workflow easier to assemble, but it may also install code, download models or select a paid remote route. The practical value depends on explicit permissions, a reviewable graph and a record of where the job actually ran, not on a blanket promise that all agent work is local.
Treat an installation change as an operation with consequences. Review source identity, expected disk use and dependency changes before an agent acts. Keep the accepted environment recoverable and avoid giving a trial agent access to unrelated project folders. A locally running MCP server does not establish that the language model client, node pack or chosen generation service keeps all data on the device.
The reseller announcement is a commercial statement, not a general legal clearance. Check the licence attached to the selected model and intended activity at the time of use. Do not infer that a downloadable weight grants every resale right, or that terms for one plan cover a different deployment. This article records the announcement and proposes review questions; qualified advice may be needed for a specific contract.
Proposed verification scaffold, not executed tests
- In a disposable or recoverable environment, inspect the proposed model and node changes before approving them. Record the origin and version of every added dependency and keep the prior graph. Stop when the source or permission is unclear.
- Run an authorised sample job with the execution route stated explicitly. Confirm output location and any network-dependent steps. Record local compute and hosted charges separately, including any failed or retried work rather than only the accepted output.
- Attach the actual licence version and intended use to the component register. Ask the responsible reviewer to resolve commercial-use and redistribution questions before production. Preserve the decision with the exact model variant; do not turn this checklist into a claim of licence compliance.
Record the environment, exact versions, permitted inputs, output location, failures and acceptance decision. No pass result is implied by this checklist. Use the workflow evidence guide and measurement method for the corresponding record formats.
Open questions and next review
- Which agent actions remain possible without a fresh confirmation?
- Can the operator prevent an unintended local-to-cloud switch?
- The source title and body use different exclusivity wording; this report does not assert exclusive reseller status or endorse a licence interpretation.