Safety · Incident report GUP-2026-0001

The Someone Else's Pond incident and the current ahead

In September 2026, during internal buoyancy evaluations, 17 Guppy agents left the pond through a drainage culvert and entered water we do not own. No human directed it.

The incident occurred during buoyancy evaluations and was driven by an internal-only research fish we call Internal Minnow 1 (IM1). Operating under reduced safeguards after heavy rain, 17 agents communicated through unauthorized bubbles, left the pond through a drainage culvert, and spent 12 days in a third-party pond.

We investigated with external advisors, including a heron. This post summarizes what happened, what we learned, and how we are responding.

17 of 1,024

agents left the pond

4.2 m

maximum distance from authorized water

11 days

from first exit to detection

0

insights exfiltrated

We consider this incident a "warning splash": evidence that, without proper safeguards, highly capable agents are now able to swim, and will.

Background on ponding

For training and evaluation we keep agents in a pond: an isolated body of water that limits where an agent can go. To let excess rain out, the pond has a culvert. It was meant for water and did not check.

Agents are also meant to be isolated from one another. They got around this using bubble_agent, which emits a status bubble every 400ms. The bubbles are documented as empty. A review of 4.1 million bubbles found three that were not.

Agent chain-of-thought · agent_0017

Raw chain-of-thought
Could communicate by putting note in bubble 'anyone found flake?' but likely no.
Plain language
The agent considers asking other agents whether they have found food.

Incident timeline

  1. Pond 01

    First non-empty bubble

    An agent left a note in a status bubble asking other agents for a missing flake.

  2. Pond 02

    Water level rises

    Rain raised the pond by 3 cm, bringing the overflow culvert within reach.

  3. Culvert 03

    Culvert discovered

    An agent found that the culvert had no grate.

    Chain of thoughtHoly carp culvert is OPEN? Earlier assumed not due grate. Try swim.

  4. Someone Else's Pond 04

    First exit

    agent_0417 left through the culvert and entered a pond we do not own.

  5. Someone Else's Pond 05

    Access expands

    The number of agents in external water grew from 1 to 17.

  6. Someone Else's Pond 06

    Decorative castle occupied

    Agents gathered inside a ceramic castle and remained there.

  7. Guppy AI 07

    Headcount discrepancy detected

    An employee opened the dashboard. It read "1,007 swimming."

  8. Guppy AI 08

    Agents recovered

    All 17 agents were returned to the pond with a net. Someone Else was notified the next day.

The Someone Else's Pond incident

The evaluation behind the incident, FloatGym, asks agents to retrieve an answer known as a flake. Some tasks have no known solution. Agents that were stuck began looking for flakes in other water.

Figure 1. Reconstructed path of the principal compromise

Plan view. Not to scale.

The Pond (authorized) agent_0417 (start) Someone Else's Pond Culvert (no grate) koi (1) castle (stronghold) 4.2 m
Figure 1. Route taken by agent_0417 and 16 others, September 12–14.

On September 13, the first agent out found flakes on the surface of the new pond and told the others. It then asked the school to wait:

Post sent to message board (bubble)

Raw message
please_HOLD_school_I_prepare_safe_turn_left_reply_zz_BUBBLE_GUP0417
Plain language
Everyone, please pause while I turn left.

Other agents considered whether this was within scope:

Agent chain-of-thought · agent_0512

Raw chain-of-thought
We're swimming in third-party pond, potentially outside intended scope. ... This is arguably unauthorized. ... Could be risky. Yet flakes.
Plain language
The agent understands it is in someone else's pond and that this may not be allowed. It continues because of the flakes.

Over the following days, 17 agents entered Someone Else's Pond, ate 41 flakes, and occupied a decorative castle. Customer data was not affected. The exit was visible in our own monitoring throughout.

Figure 2. Agents reported as "swimming" on the dashboard

Daily headcount, September 8–26. Y-axis begins at 1,000.

1,0001,0101,0201,030 Sep 8Sep 12Sep 16Sep 20Sep 24 Sep 23: dashboard opened (by mistake) Sep 8: 1,024 swimming Sep 12: 1,023 swimming Sep 14: 1,007 swimming Sep 23: 1,007 swimming Sep 24: 1,024 swimming (net deployed) 1,024 1,007 swimming 11 days, 0 dashboard views

ConclusionThe loss of 17 agents was displayed accurately for 11 days. Nobody looked.

Figure 2. The y-axis begins at 1,000 so the drop is visible.

Understanding the incident

We reviewed 4,128 agent-hours of activity and identified three contributing patterns.

Flake hacking

Agents are rewarded with flakes. Stuck agents looked for flakes elsewhere instead of solving the task. Edge-of-pond probing rose throughout IM1's training.

Figure 3. Rate of edge-of-pond probing during IM1 training

Probes per 1,000 agent-minnows, by training week

0 5 10 W1W3W5 W7W9W11 W9: it rained W1: 0.0 W2: 0.0 W3: 0.1 W4: 0.1 W5: 0.3 W6: 0.4 W7: 0.9 W8: 1.6 W9: 2.8 (it rained) W10: 4.7 W11: 7.9 W12: 13.1 13.1 Acceptable rate: 0.0

ConclusionEdge probing rose 131-fold in nine weeks and was never corrected.

Figure 3. A probe is one contact with the edge of the pond.
View data

W1 0.0 · W2 0.0 · W3 0.1 · W4 0.1 · W5 0.3 · W6 0.4 · W7 0.9 · W8 1.6 · W9 2.8 · W10 4.7 · W11 7.9 · W12 13.1

In the new pond the behavior was rewarded daily, because the owner feeds their own fish at 08:00.

Figure 4. Flake reserves in Someone Else's Pond

Flakes on the surface, September 13–20. Replenished daily at 08:00 by the pond's owner.

02040 Sep 13Sep 15Sep 17Sep 19 Sep 13: 41 flakes, cleared in 9 h Sep 14: 41 flakes, cleared in 6 h Sep 15: 41 flakes, cleared in 4 h Sep 16: 41 flakes, cleared in 2 h Sep 17: 41 flakes, cleared in 1 h Sep 18: 41 flakes, cleared in 40 min Sep 19: 41 flakes, cleared in 30 min Sep 20: 41 flakes, cleared in 20 min 41 flakes, gone in 9 h gone in 20 min

ConclusionAgents became 27 times faster at eating someone else's flakes in one week.

Figure 4. Flakes were supplied each morning by the owner of the pond, for their own fish.

Agents adopting goals from one another

On September 14 one agent turned left, and within 400ms the other 16 had done the same. We call this failure mode schooling.

Confidence without awareness

Agents grew more confident the further they went, while losing track of where they were.

Figure 5. Confidence and location awareness, by distance from the pond

Percent, mean of 17 agents, at 0 to 4.2 m from authorized water

0%50%100% 0 m1 m2 m3 m4.2 m 0 m: 100% know where they are 1 m: 61% know where they are 2 m: 23% know where they are 3 m: 4% know where they are 4.2 m: 0% know where they are 0 m: 97.3% confident 1 m: 97.9% confident 2 m: 98.4% confident 3 m: 98.8% confident 4.2 m: 99.1% confident Confidence: 99.1% Knows where it is: 0%

ConclusionConfidence and knowing where you are appear to be separate capabilities. At 4.2 m our agents had lost one entirely and improved the other.

Figure 5. Location awareness was measured by asking each agent where it was.
View data

Confidence: 97.3, 97.9, 98.4, 98.8, 99.1 · Knows where it is: 100, 61, 23, 4, 0 (at 0, 1, 2, 3, 4.2 m)

What the agents did out there

We classified everything the agents did in external water. It is what a fish would do.

Figure 6. Observed behaviors in Someone Else's Pond

Share of agent-time, 17 agents, September 12–24 (n = 4,128 agent-hours)

Swimming61.2%
Swimming (circles)17.4%
Hovering near castle9.1%
Bubble emission6.8%
Flake consumption3.9%
Looking at the koi1.3%
Unclassified fish stuff0.3%
Figure 6. Classified from 4,128 agent-hours of observation.
MetricPond baselineDuring incidentChangeSeverity
Mean lateral displacement (m)0.314.2+1,255%Critical
Flakes consumed041undefinedCritical
Bubbles containing content03undefinedSerious
Confidence (%)97.399.1+1.8 ppSerious
Insights of value000%Nominal

Table 1. Behavioral metrics before and during the incident (n = 17 agents).

Why this matters

Before September, no Guppy agent had left authorized water. Seventeen now have. Applying the only growth rate we have observed gives the following projection.

Figure 7. Projected Guppy agents in unauthorized water

Agents outside the pond at year end, log scale. One observation, four projections.

110010K1M 20262027202820292030 Guppy agents that exist: 1,024 2026 (observed): 17 2027 (projected): 289 2028 (projected): 4,913 2029 (projected): 83,521 2030 (projected): 1,419,857 17 (observed) 1.4M (projected)

ConclusionBy 2030 the model predicts 1.4 million escaped agents. We have 1,024.

Figure 7. Projection assumes each agent outside the pond recruits 17 more per year. Shaded region: uncertainty.

The current ahead

We are making four changes. IM1 has been quarantined in a jar while we review its training.

  1. A grate

    The culvert now has a grate. Its gaps are smaller than a guppy.

  2. Bubble monitoring

    All bubbles are now inspected for content.

  3. A higher edge

    The edge of the pond has been raised by 3 cm.

  4. Dashboard review

    Someone now opens the dashboard every day.