TL;DR
The Elephant-Goldfish Model (EGM) (google/elephant-goldfish-model) is an open-source plugin for AI coding agents. It makes the agent write a design document before it writes code, then sends that document to reviewers that have never seen your conversation. The “elephant” is your long-running session, which remembers everything. The “goldfish” are fresh subagents that remember nothing, so they catch the assumptions you and the elephant stopped noticing.
Last verified: November 15, 2026. Facts as of that date:
- 19,384 GitHub stars, 1,439 forks, 30 contributors, Apache-2.0 license. The repository was created on September 13, 2026 and is on GitHub’s weekly Trending page with 5,539 new stars in seven days.
- Latest release: v0.1.1, published November 6, 2026 (v0.1.0 shipped October 27).
- 72 open issues (GitHub’s combined counter shows 110 because it also counts open pull requests).
- Officially supported hosts: Antigravity CLI, Claude Code and Codex. Claude Cowork, ChatGPT, omp, Muse, Windsurf/Devin, Cursor, OpenCode and GitHub Copilot are partial or experimental.
- Google says “thousands of Googlers use this plugin every day to ship production Google code.” The README also says it is “not an officially supported Google product.”
Not run by us: our hands-on lab (a throwaway GitHub Actions container) could not start on November 15, 2026 because GitHub refused the job over a billing limit on the account. Even with the lab running, EGM’s actual workflow (brainstorm, draft, review) needs a signed-in coding agent that can spawn subagents, such as a paid Claude Code or Codex account, which the lab does not have. This review is built from the README, the design docs, TESTING.md, the FAQ, the release notes, the issue tracker and Google’s announcement post.
Our verdict: EGM is the most disciplined packaging of “spec-first” agent work we have seen from a big vendor. The core idea, reviewing a plan with an agent that does not share your blind spots, is sound and cheap to try. What makes it worth installing is less the metaphor and more the details: reviewer personas with narrow jobs, written quality standards, a hard stop if your agent cannot create truly fresh subagents, and documentation that is unusually honest about what has not been verified. The costs: a full review runs many subagents and burns real tokens (one recorded run hit a usage limit), the project has no published benchmark showing it beats a normal workflow, and on Codex and Antigravity the “fresh” reviewers can still see your AGENTS.md. Use it for consequential, uncertain changes. Skip it for small fixes.
Quick Reference
| Field | Value |
|---|---|
| What it is | Plugin (skills + reviewer personas) for spec-first design and fresh-context review |
| Hosts with end-to-end fixtures | Antigravity CLI, Claude Code, Codex |
| Partial / experimental | Claude Cowork, ChatGPT, omp, Muse, Windsurf/Devin, Cursor, OpenCode, Copilot |
| Skills | 7 (brainstorm, draft, review, review-loop, resolve, bootstrap, drift-report) |
| Reviewer personas | 10 files in agents/ |
| Document standards | 5 (feature spec, Heilmeier, implementation readiness, re-implementation, zoom-out) |
| Claude Code minimum | 2.1.271 (for omitClaudeMd reviewer isolation) |
| Account / telemetry | None; runs on your host’s model account |
| License | Apache-2.0 |
| Price | Free; you pay your model provider |
What problem EGM is trying to solve
The pitch comes from an essay by Dave Rensin, one of the plugin’s authors, titled Elephants, Goldfish, and the New Golden Age of Software Engineering. Its line “Design is the new code” is quoted in Google’s launch post. The argument: coding agents made writing code fast, but they also made it fast to write the wrong code. Google’s announcement calls this “auto-scaling our mistakes.”
The specific failure EGM targets is self-review. EGM’s own review design document lists three problems when the same context window drafts and checks a plan:
- Blind spots persist. The model assumes things it holds in memory are obvious from the text.
- Hallucinated APIs survive. Assumptions made during discussion are never checked against the real source code.
- Weak plans get approved. Implementation plans without file paths or a test strategy get waved through.
Ask an agent to “review the plan you just wrote” and it mostly agrees with itself. EGM’s answer is structural: the reviewer must be a new subagent that sees only the document and the source files it references, nothing from the conversation.
How the workflow works
EGM splits work into three roles:
| Role | Sees | Job |
|---|---|---|
| Elephant | Your project, requirements and earlier decisions | Explore the problem, draft the spec |
| Goldfish | Only the document and referenced source files | Find missing assumptions, unclear requirements, risks |
| You | The goals and constraints | Make trade-offs, approve the design, decide what to build |
The default path has three phases, each a skill:
egm-brainstorm: you and the agent discuss requirements with a “no code” rule. Fresh reviewers challenge the proposal, and the agreed direction is saved toconcepts_brief.md.egm-draft: the agent turns the brief intodesign_draft.md, pausing after each section for your feedback. Google’s post says the draft covers the problem, the technical plan, alternatives considered and an implementation plan that lists the specific files to change.egm-review: the Goldfish protocol.
The review is the interesting part. According to docs/designs/review.md, it runs five stages in order, each with different personas:
| Stage | Reviewers | What it checks |
|---|---|---|
| Strategic review | zoom_out, inventive_catalyst | Is this the right approach at all? Can abort. |
| Comprehension test | comprehension | Can a stranger explain the design back? If not, it is ambiguous. |
| Critic review | design_critic, structural, style | Edge cases, hidden dependencies, logical gaps |
| Intermediate zoom-out | zoom_out | YAGNI and defensive over-engineering |
| Implementation readiness | implementation_readiness, codebase_details, style | Are file paths, data structures and signatures concrete? |
Between stages, egm-resolve lets you choose which findings to act on. The inventive_catalyst reviewer, added in v0.1.1, applies TRIZ (a structured problem-solving method) to look for a different solution rather than a patched one.
Two design choices stand out. The comprehension test is a cheap check: if a reader with no context cannot summarize your plan, it is not ready. And the review skill refuses to fake it. From skills/egm-review/SKILL.md: “If your harness has no subagent tool, stop and tell the user: a review in the same context is not a Goldfish review.”
The other four skills are useful on their own:
egm-reviewon an existing doc, README or PR plan, checked against live code.egm-review-loopruns a chosen group of reviewers against your chosen standard, which also works for non-software documents.egm-bootstrapwrites or updates documentation for an existing codebase.egm-drift-reportcompares checked-in design docs with the current source and lists where they diverge.
Getting started
Install the whole plugin. The docs warn that skill-only installers that copy skills/ alone break EGM, because the skills read agents/ and resources/document_standards/ at run time.
Claude Code (2.1.271 or later):
claude plugin marketplace add google/elephant-goldfish-model
claude plugin install egm@egm
Codex CLI:
codex plugin marketplace add google/elephant-goldfish-model
codex plugin add egm@egm
Antigravity CLI:
agy plugin install https://github.com/google/elephant-goldfish-model
Start a new session after installing. The easiest first use is reviewing an existing document:
/egm:egm-review docs/designs/webhooks.md
Or check whether your docs still match the code:
/egm:egm-drift-report docs/designs/
For a new feature, the README’s example is webhook delivery:
/egm:egm-brainstorm Add webhook delivery to this project.
/egm:egm-draft
/egm:egm-review design_draft.md
Keep the /egm: prefix in Claude Code and Antigravity. The README notes that agy CLI 1.4.10 completes unprefixed names but 1.4.8 does not. In Codex, pick the EGM skill from the skill picker instead.
If you lock down Claude Code permissions, docs/claude.md gives Read(...) rules scoped to the plugin’s cache folder; use * for the version segment so they survive updates.
What it costs
EGM itself is free: no hosted service, no account, no telemetry. docs/privacy.md says the runtime “does not operate a hosted service, database, analytics client, or telemetry endpoint,” and declares no MCP server. All model calls go through your host’s account.
The real cost is tokens, and the project does not yet tell you how many. Issue #385, opened November 10, says it plainly: “New users cannot find the expected cost or duration of an EGM review. Public hands-on reports of EGM repeat one concern: token cost.” It is still open.
What we can infer from the design: one full egm-review spawns at least ten reviewer runs across five stages, and each reads your whole document plus any referenced source. The Muse test record mentions an uninterrupted review with 15 fresh-context reviewers. TESTING.md logs a Claude Cowork run on Opus 5.5 where a “usage limit interrupted stage 8.” If you are on a subscription plan rather than an API key, expect a full review on a large doc to take a noticeable bite of your window.
Honest limitations
- No benchmark yet. Issue #61, “Benchmark review quality against a baseline,” is open. The FAQ is candid: “Completing the EGM workflow alone does not demonstrate a productivity improvement.” Google’s “thousands of Googlers” claim is usage, not measured outcome.
- Fresh is not fully fresh on every host. Per
docs/harnesses.md, issue #237 reports that Codex CLI 0.166.0 passed project and userAGENTS.mdfiles to reviewers, and Antigravity CLI passedAGENTS.mdandGEMINI.md. Parent conversation turns did not leak, but your house rules did. Only Claude Code has a verified exclusion control (omitClaudeMd). - Release bundles not natively verified. The v0.1.1 notes say checksums and attestations were verified, but “native end-to-end verification of these exact release ZIPs remains open in #60.”
- It slows small changes. The FAQ again: design and review “may not pay off for a small, well-understood change.” It recommends using EGM for “What’s important now?”, not everything.
- Review overload moves to you. More design docs means more human reading; the FAQ admits this “can” become a bottleneck.
- It is young. Two months old in public, 72 open issues, version 0.1.x. The plugin itself is Markdown skills and personas (the Python is only its test suite), so there is nothing to self-host.
Community reactions
Coverage since the October 22 launch has been mostly explainers. On Hacker News, EGM has been submitted several times; the threads we found were small relative to the GitHub star count. On Reddit, threads in r/ClaudeAI, r/OpenAI and r/google_antigravity share setups across Claude Code, Codex and Antigravity. The recurring skeptical take is that EGM formalizes spec-driven development and plain old design review rather than inventing something new. That is fair, and the FAQ agrees: asked whether there are alternatives, it answers “Yes. Many.” The token-cost concern is common enough that the maintainers opened #385 to address it.
Open issues point at the right next problems: tagging each finding with its evidence (#433), checking code against the approved design (#436) and giving reviewers recorded decisions so they stop re-litigating them (#408).
EGM vs the alternatives
| Option | Approach | When it fits better |
|---|---|---|
| EGM | Spec first, then staged review by fresh-context personas | Consequential or uncertain changes where a bad assumption is expensive |
| GitHub Spec Kit | Spec, plan and tasks templates that drive implementation | You want a spec-to-tasks pipeline more than adversarial review |
| OpenSpec | Lightweight change proposals kept alongside code | You want specs as living repo artifacts; EGM has an open issue (#383) for interop |
| Plan mode in Claude Code / Codex | Agent writes a plan in the same context | Small, well-understood changes |
| Manual “new chat” review | Paste the doc into a fresh session yourself | You want the goldfish idea with zero setup |
The honest comparison is with the last row: a new session asked to tear your design apart gets you much of the benefit. EGM adds repeatability: narrow personas, written standards, a comprehension gate and a refusal to run in a shared context.
FAQ
What is the Elephant-Goldfish Model?
It is an open-source plugin from Google for AI coding agents. A long-running “elephant” session holds your project context and drafts a design document. Fresh “goldfish” subagents, which have no memory of the conversation, review that document to find hidden assumptions and gaps before any code is written.
Which coding agents does EGM work with?
As of November 15, 2026, Antigravity CLI, Claude Code and Codex pass the project’s automated installation and end-to-end workflow fixtures. Claude Cowork and ChatGPT have working installs with open verification gaps. omp, Muse and Windsurf/Devin have partial support, and v0.1.1 added experimental Cursor, OpenCode and GitHub Copilot adapters.
Is EGM free?
Yes. It is Apache-2.0 licensed, needs no EGM account and sends no telemetry. You pay for the model usage on your own host account, and a full review runs many subagents, so token use is significant. The project has not published a measured cost per review yet (issue #385).
Can I use EGM without writing a new spec?
Yes. Run /egm:egm-review on an existing design doc, README or PR plan saved as Markdown, or /egm:egm-drift-report on a folder of design docs to see where they no longer match the code. You do not have to follow the full brainstorm-draft-review sequence.
Does EGM make development faster?
Not proven. The project’s FAQ says design and review take time and may not pay off for small changes, and that completing the workflow “does not demonstrate a productivity improvement.” A baseline benchmark is an open issue (#61). Measure total time, useful findings and rework on your own tasks.
Are goldfish reviewers really context-free?
They never see your earlier conversation. On Claude Code 2.1.271+, reviewers also skip CLAUDE.md. On Codex and Antigravity, issue #237 reports that project instruction files like AGENTS.md still reach reviewers, so their context is not completely clean.
Bottom line
EGM is a well-engineered answer to agents grading their own homework. Start with two install commands and one egm-review on a doc you already have, budget for the tokens, and judge it on your own rework rates rather than the star count. If you take one idea from it, take the comprehension test: if a fresh reader cannot explain your plan back, your agent is not ready to build it.
Sources
- google/elephant-goldfish-model on GitHub
- Introducing the Elephant-Goldfish Model plugin — Google Open Source Blog
- EGM v0.1.1 release notes
- Goldfish Review Protocol design doc
- Harness setup and support status
- EGM FAQ
- EGM testing playbook and harness test record
- Issue #385: Document review cost, duration, and plan limits
- Issue #237: Exclude host instructions from Codex and Antigravity reviewers
- Dave Rensin, “Elephants, Goldfish, and the New Golden Age of Software Engineering”
- egm.dev