Update your AI agents from the portal — and a faster infrastructure behind the scenes
From this release, you can update Emma directly from your portal whenever a new version is available. Behind the scenes, token purchases, subscriptions, and container provisioning all work more reliably.
PlatformJuly 9, 2026
More control for users, more reliability under the hood
Version 1.4 puts a key action in your hands: updating Emma no longer requires contacting support. You can do it yourself, directly from your portal. The rest of this release focuses on infrastructure improvements that make token tracking, billing, and container provisioning more accurate and consistent across the platform.
1. Emma Agent
Update Emma yourself, whenever a new version is available
One-click updates from your portal
A new update button now appears in the Agents tab of your portal whenever a new version of Emma is available. Click it to update your instance immediately — no need to contact support or wait for a scheduled maintenance window.
As new AI agents are added to the platform, the same mechanism will apply to them too.
2. Token & Billing
Token purchases and subscriptions always linked to the right account
Token purchases are now tied to the right container
When you buy additional tokens, the resulting order is now automatically linked to the container and customer that triggered the purchase (using the container ID passed through the purchase flow).
No more manual matching. Billing and support teams can reconcile purchases instantly, even for accounts with multiple containers.
Subscriptions stay in sync with your containers
If a container is permanently deleted, its associated subscription is now cancelled automatically. This prevents billing for environments that no longer exist and eliminates manual cleanup work for your team.
3. Infrastructure
Faster provisioning and more balanced resource distribution
Container counts are retrieved faster
The process that checks container counts across infrastructure nodes (Proxmox) has been optimized to make fewer requests. This reduces latency during provisioning, especially noticeable when many containers or nodes are involved.
New containers are distributed more evenly across nodes
The node allocation algorithm now distributes new containers more evenly based on load and availability. This avoids overloading individual nodes, improves overall resource balance, and allows multiple containers to be provisioned in parallel more reliably.
Token usage is now tracked by individual user
Token consumption records now include the user ID and username alongside the container reference (stored in MongoDB). This enables more granular usage analytics (broken down by user and by container) and lays the groundwork for future reporting, billing detail, and anomaly detection.
4. Improvements
Platform and workflow improvements
This release also includes improvements to the communication layer between the platform and n8n automation workflows, making integrations more reliable and reducing the risk of silent failures in automated processes.
Ready to explore the latest Binhex Cloud features?
Start a workspace, try Emma, and see how the latest updates work in practice. All inside your own environment.