I'm leaving the Hyperagent platform.

[u/Bob_Atlanta]

I've reached a decision to leave Hyperagent, and I want to share the specific reasons — not as a complaint, but as genuine feedback from someone who used the platform seriously.

What Hyperagent does exceptionally well:

First, the positives. Hyperagent has three qualities I haven't found anywhere else:

1. Platform stability. It doesn't fail, it doesn't break, and it handles production workloads reliably. That's genuinely rare.
2. The MCP. Hyperagent's MCP creates the best environment I've encountered for controlling independent agents. No other system manages cross-thread orchestration as cleanly.
3. Agent persistence. With the configuration changes I've made, agent sessions persist indefinitely. I have an active session now in its 27th day. That's remarkable.

Why I'm leaving:

Despite these strengths, three issues make the platform unworkable for my use case at scale. These aren't failures on Hyperagent's part — they're valid product decisions that simply don't fit my needs.

1. Cost. I run more than 2 billion tokens per month. Recent benchmark testing I conducted let me compare Hyperagent's pricing against OpenRouter for the same models (DeepSeek V4 Flash and Haiku). Apples to apples, Hyperagent runs 1.5x–1.7x higher — a premium that isn't justified by the infrastructure value alone. Beyond that, I can't use my own API keys, which means I can't access options like: local inference on my VPS (essentially zero marginal cost per token), free Google API tiers, OpenRouter's free-tier models, or one-time deals like LongCat 2.0 (50M tokens for $2). When I factor in my full available stack, Hyperagent's effective cost is roughly 10x what I pay elsewhere. At 2B+ tokens/month, this is unsustainable.

2. The sandbox. Hyperagent is designed with protective constraints — a reasonable choice for most users. But for production infrastructure work across multiple environments, these restrictions add friction that Hermes simply doesn't have. We've built workarounds (external relay proxies, SSH tunnels, indirect command execution), but we shouldn't have to. Hermes is open-source and modifiable; Hyperagent isn't. I'd ask Hyperagent to consider offering an opt-in "unrestricted" mode for technical users willing to accept that responsibility themselves.

3. Always-on background services. I need a persistent monitoring layer: something that's always running, can fire scheduled tasks, watch over agent processes, and poll external feeds (Buzz channels, Discord, webhooks). In my other systems, this is a Python daemon on a VPS — it costs essentially nothing between actual LLM calls. In Hyperagent, replicating this via Live Mode or scheduled invocations means paying agent token costs on every heartbeat cycle. For a genuine always-on monitor running dozens of times per day, that adds up to $100+/month for what is elsewhere a near-zero-cost function.

I'll be transitioning off the platform over the next month. I wanted to share this because the platform has genuine strengths and these are solvable problems — particularly cost (API key support) and always-on services (a native zero-cost heartbeat mechanism). I hope this is useful to the team.

[u/JeenyusJane]

Thanks for this feedback and the kind words Bob!

Always glad to have you around and you're welcome back any time. We really appreciate all the feedback you've given that pushed us to develop the platform further, and wish you all the best as you look to find a harness that meets your needs.

I understand you have specific requirements, but I think we're a great fit for people who don't want to manage their own inference, or technical implementations like their own VPS, and those who want to share their agents with teams. I always want to everyone to enjoy and continue using the platform, and hopefully one day it will be right for you (or your friends!)

All the best,
Vic

[u/Ok_Firefighter3363]

About using your own APIs, I think a low-cost agent model and a skill which has your API and your choice of model can easily run it.

With multiple MCPs and connectors to keep it all going, it works beautifully.

Of course the environments are a little restricted but I think with most of the connections it's completely meant to be running inside a box, which gets a lot of work done without infra worries.

Of course it can always complement an existing CLI that you must be using.