AutoHedge vs Vibe-Trading
Swarm-agent 'autonomous hedge fund': cooperating agents automate market analysis, risk management and trade execution. Python, from the Swarms ecosystem. — versus — HKUDS' personal trading agent: one command gives your agent market data, analysis and trading capability, with a shadow-account mode, API and MCP surface.
Same ambition — agents trading on your behalf — with opposite temperaments: Vibe-Trading (HKUDS) ships shadow accounts and an MCP surface for cautious integration; AutoHedge sells the autonomous hedge-fund dream. Both need your skepticism.
| AutoHedge | Vibe-Trading | |
|---|---|---|
| Stars | 3.8k | 24k |
| Forks | 643 | 4.1k |
| Language | Python | Python |
| License | MIT | MIT |
| Last activity | 2 months ago | yesterday |
| Topics | finance, agents | finance, agents |
| Curated connections | 1 | 2 |
AutoHedge — the curator's take
Multi-agent architecture applied to trading: director/analyst/risk agents deliberate before execution — as a reference architecture for agent-team decision pipelines it's worth reading. Now the cold water: 'enterprise-grade autonomous hedge fund' is marketing, not audit — no published live track record; the Swarms ecosystem runs hype-forward; the repo was quiet for two months at review. Paper-trade it, treat real capital as adversarial testing you pay for.
Vibe-Trading — the curator's take
From the lab behind LightRAG and VideoAgent: a full trading-agent stack with the two features that matter — a shadow account so strategies run against real markets with fake money, and an MCP surface so YOUR agent gains the capability rather than you adopting theirs. The team publicly disavows the fake tokens trading on its name — read that as both integrity and a warning about the space. NOT financial advice infrastructure: agents amplify whatever edge (or absence of one) you encode; stay in the shadow account until the data argues otherwise.