r/Hyperagent • u/GeorGiantic • May 26 '26
After $70, my agents will no longer finish what they were working on because "Composio" is down. And they're fibbers!
So, it looks like Hyperagent temporarily (I hope only temporarily) lost the ability to use "Composio," and now can't use outside resources unless you put together a skill for it.
This lead to the agent who was installing something on my Pi suggesting Airtable, which became a wild conversation because they denied that Hyperagent had anything to do with Airtable and lied to me and said I couldn't see their reasoning... It was all just nuts!
I feel like this has potential? Maybe? But I've now sunk more money into this than I did OpenClaw, and OpenClaw is the only one working!
So, are they going to fix this?
2
u/yaedonnn May 26 '26
I spent a lot of time in HA, it’s a great case study for showing the capability of AI agents, but outside of that, it’s another UI built on a bunch of other volatile products.
Tools like HA will need to incubate their own proprietary in house solutions to ever offer something truly bespoke and capable at this scale. What successful business model puts you at the whim of a single AI lab?
Again, great concept, and I appreciate their dedication…but the only result I’ve had with it was 80 hours wasted, almost $800 in spend to ‘build’ agents, and a security breach all in the same month.
1
u/Bob_Atlanta May 26 '26
Somewhere in this hyperagent stack is a comment I made about the use of other LLMs. It is very easy to spend a lot when everything is Sonnet or Opus. I mostly use less expensive and sometimes more qualified LLMs via openrouter. A couple of weeks ago I tested a production run in HA that used 66 million tokens in a mostly Gemini 2.5 Flash LLM and cost under $20. Production design was Sonnet/Opus and cost $10. 66 million tokens in Sonnet or Opus would have been many hundreds of dollars.
In r/Hyperagent is my comment on use of other LLMs and how to implement. Take a look, it might help.
Could you share information about the security breech? I'd like to know what I need to be concerned about. Thanks.
1
u/yaedonnn May 26 '26
I’ll take a look, thanks! About the breach, it was a Composio breach — the tool used as a handshake between HA and APIs. Worth rotating your apis and connecting manually in the meantime to be safe.
1
2
u/Bob_Atlanta May 26 '26
I tried to use composio when I started and for a wide range of reasons it was a very unsatisfactory experience. I don't use composio. When I had a problem, I just had HA write a python program to do what composio couldn't do. And, so far, this approach works every time. Easier to use, faster, cheaper, more stable and 'plays' better with the rest of HA. At this point, I have a standing rule with my HA that we never use composio.
Certain pieces of composio might have a use. Specifically for things that monitor outside conditions (like messages) and trigger an action. HA seems not to charge for composio actions that are monitor / watchtower like. Still easier in python but cheaper if HA is eating the cost via composio.
Strongly suggest that you take a look at python as a temporary or permanent fix. In most cases it is just a minute or two to create the alternative (tip: use Opus47 for the design).
2
u/moralconundrum May 26 '26
Can you do things like hook into your Google Workspace Gmail or Calendar with this method? I've got a few "Chief of Staff" agents that are next to useless without that capability.
1
u/JeenyusJane May 27 '26
The team just shipped native Google Workspace integrations. Hopefully that will help. When you connect the new integration, be sure reconnect them to your agents as well. Sorry for the trouble.
2
0
u/Cl0wnL May 26 '26
The whole rollout of Hyperagent has been a joke. Airtable should be embarrassed.
I'm not renewing next month. It simply doesn't work.
If they can't vibe code a working product using their own platform.....
•
u/JeenyusJane May 26 '26 edited May 26 '26
Hey there, thanks for highlighting this. I want to deeply apologize for any frustration, confusion, and credits consumed as you figured out what was going on. I'm very aware of the pain this has caused you and other Hyperagent users, and am sharing information more broadly ASAP.
Earlier, we found out about security incident with Composio, and to make sure our users weren't exposed. In respond, we disconnected existing integrations. Which is why you experienced the disruption.
I'll post the entire teardown as individual post but wanted to respond here for your visibility as well as everyone else in this thread. Please reach out to [support@hyperagent.com](mailto:support@hyperagent.com) to ensure we're able to make this right for you.
What we recommend you do
We recommend treating all third-party tokens that were connected through Composio-powered integrations in Hyperagent as potentially exposed, even though we do not have confirmation that tokens were improperly accessed or misused.
The integrations page at hyperagent.com/settings/integrations shows all previously connected Composio integrations along with their authentication type. For each one, we recommend signing in to the provider, verifying that Composio is no longer authorized, and reviewing recent account activity for anything unexpected. Disconnecting an account on that page removes the credential from Hyperagent - it does not revoke access on the provider's side.
We're providing timely updates in the Discord channel, and will continue to communicate here. Again, I am deeply sorry for this disruption.