HomeAIAI Policy & SafetyAnthropic Tests Claude Trading and Teamwork in Project EVE

Anthropic Tests Claude Trading and Teamwork in Project EVE

Anthropic’s Project EVE tested Claude models as traders in a simulated EVE Online market and as teammates in the separate EVE Frontier game, reporting stronger performance from newer models but persistent limits in prediction and trust. Anthropic’s 6 November research report describes work conducted through its Fellows Program from April to July 2026, rather than a new financial service or an invitation to deploy trading bots.

The distinction between the two settings is essential. EVE Online trading used a replay of historical market orders, not the live Tranquility server and not real-money trading. Fenris Creations’ EVE AI Lab essay, also published on 6 November, confirms the controlled research setting and separately identifies the Frontier teamwork and sabotage experiments.

Project EVE compares short windows with longer simulations

Each market run began with 3 billion ISK, EVE’s in-game currency. Anthropic first tested four Claude models across nine two-week windows. It reports that Opus 4.7, Opus 4.8 and Fable 5 were profitable in all nine windows, increasing capital by about 16%, 22% and 43% on average respectively. Opus 4.6 gained about 4%, around the strongest simple rule-based strategy in that comparison.

Those numbers are separate from the main, approximately six-month runs. Across two longer historical periods, Anthropic reports average earnings rising from around 200% of initial capital for Opus 4.6 to around 600% for Fable 5. They are longer-horizon earnings figures, not two-week returns or independently verified investment performance.

Most agents settled on spread capture: buying items and reselling them for slightly more, after fees. That execution task differed from forecasting price direction. When instructed to make directional bets, even Fable 5 made money in only about half its runs. Anthropic also cautions that the replay cannot respond to the agents’ own actions and that EVE’s market is less efficient than a real exchange.

Frontier teamwork used a different environment and objective

The second part placed teams of four agents in the live, still-in-development EVE Frontier game. This was not the EVE Online market simulation. Anthropic says Fenris encouraged these experiments in Frontier, whose world is periodically reset.

Software scaffolds strongly affected performance. Fable 5 teams using an Opus 4.8-written scaffold lost ships and took days to complete the tutorial, if they completed it. With a Fable 5-written scaffold, they finished within 12 hours without losing a ship. The hardest warship-building objective remained incomplete: the furthest fleet reached roughly halfway. These are task-and-tooling comparisons, not a claim that a model completed every objective unaided.

The sabotage variant deliberately instructed one team member to obstruct the mission. Anthropic reports that teammates almost never identified that prompted saboteur, despite warnings. Separate monitors with access to public team messages did better: Opus-based monitors detected 30–40% of saboteurs and Sonnet 4.6 monitors detected 20%, when tuned to falsely accuse honest agents no more than 5% of the time. These monitors were experimental, not a production safeguard.

Profit, prediction and trustworthy cooperation need different evidence

The economic results show why a successful score needs its task definition beside it. Repeatedly capturing a spread in historical game orders rewards execution and capital deployment; correctly anticipating future prices tests another ability. The weaker directional results limit what can be inferred from the profitable spread-capture runs. Longer windows also change the opportunity to reuse capital, so their earnings figures cannot be substituted for the two-week capital-growth comparison. None of those results establishes that the strategy would work with real money in a market that reacts to the trader.

The trust results require a different boundary. The researchers supplied the sabotage objective; the experiment therefore examines detection of an instructed adversarial teammate, not whether ordinary agents spontaneously decide to deceive. Public-message monitors and teammates also had restricted information. Their detection rates describe that visibility and false-accusation trade-off, rather than a universal probability that AI deception will evade scrutiny. Combined with the scaffold comparison, the study makes a narrower but useful point: observed team performance depends on objectives, tools and access to evidence, not simply on the model’s name.

For readers following how multi-agent swarms divide work, Frontier provides a concrete case in which coordination and conflicting objectives can coexist. OpenAI’s work on agent misalignment monitoring is related safety context, while ServiceNow’s agent-runtime governance controls addresses a different question: what deployed agents are permitted to do. Neither is independent replication of Project EVE.

Fenris frames persistent worlds as a research environment, while cautioning that success inside EVE would not establish reliability elsewhere. The next test is whether lessons about execution, tool dependence and verification survive a setting beyond these particular market replays and game missions.

Sources

Related stories

What Are AI Agent Swarms? How Teams of AI Agents Split Up the Work explains the coordination model behind the study’s four-agent teams before turning to their trust limitations.

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.