# Builds, tests or runs its own changes (`verify.self_testing`)

Feedback Bench, coding agents, built 2026-10-19, window 2026-08-31 to 2026-10-18. Web page: https://feedbackbench.com/coding-agents/#/criterion/verify.self_testing

Area: [Checking and finishing](https://feedbackbench.com/coding-agents/criteria/checking.md)

**Definition.** The post says whether the agent built, tested, ran or checked its own change before handing it back: it ran the test suite, skipped tests, did not run the app, or verified in proportion to the change.

**Boundary.** Not this: see [Claims work is done or fixed when it is not](https://feedbackbench.com/coding-agents/criteria/verify.false_completion.md) when the agent claims success that did not happen. Not this: see [Agent-performed code review finds real issues](https://feedbackbench.com/coding-agents/criteria/verify.agent_code_review.md) for a separate review mode or review agent.

Rated user-weeks, all agents: 646. Complaint share: 40%.

## The brief

Written by large language models from this page's numbers and the posts it quotes, then checked: every number in the text is in the build. Interpretation, not measurement.

Claude Code leads on testing its own work. Its users praise its checks more often than they fault them, and it is the only ranked agent better than the category norm here. The topic is a small part of what users rate: it is the 50th most rated of 63 criteria. Claude Code users raise it more often, rating it 5.02 times as often as other users, and they write 55% of the category's complaints here. OpenAI Codex is 3rd of 3, and its complaints nearly match its praise.

### What separates the best from the rest

No agent ranks high and none ranks low on this criterion. Among the three ranked agents, Claude Code users praise its testing in 258 user-weeks and complain in 141. OpenAI Codex users are split almost evenly, at 71 praise to 67 complaints. Google Antigravity users complain more often than they praise. Users of all three agents describe the same complaint: the agent hands back a change it never built, ran or tested, and the user finds basic breakage.

- **Ranks high**: no agent
- **Ranks low**: no agent

## How it breaks

Rule: A separate pass sorts complaints into failure modes. For each criterion with at least 30 complaining user-weeks, a large language model reads 150 complaint posts drawn at random and names 4 to 8 failure modes; a second large language model then puts every complaint post on that criterion in one mode, or in Other when it fits none. Modes are fixed once named, and new posts are sorted into them each week. A mode counts distinct user-weeks with a complaint in it, per agent; across agents, one user-week per agent. Modes do not change the labels or the Feedback Score. Examples: up to 3 posts per mode from different users, chosen and checked as receipts are.

The largest named failure is re-testing out of proportion to the change. Users say the agent reruns the full suite or checks the same thing again and again, which uses up time and quota. It accounts for 21% of complaining user-weeks and splits almost evenly between Claude Code and OpenAI Codex. Two failures belong mostly to Claude Code: tests it writes that pass by construction, at 73%, and running tests the user said not to run, at 78%.

257 complaining user-weeks.

| Failure mode | User-weeks | Posts | Agents (user-weeks) | Definition |
|---|---|---|---|---|
| Disproportionate re-testing that burns time and quota | 53 | 54 | Claude Code 23, OpenAI Codex 22, OpenCode 4, Google Antigravity 1, GitHub Copilot 1, Cursor 1, Devin 1 | The agent reruns the full suite, re-verifies the same thing many times, or piles up redundant tests for trivial changes, wasting time and usage; this excludes verification that is proportionate but just slow. |
| Self-written tests that pass by construction | 44 | 46 | Claude Code 32, OpenAI Codex 6, Cursor 4, Cline 1, Devin 1 | The agent writes tests alongside its own implementation that mirror the code, mock everything, or would pass without the fix, so a green suite proves nothing; this excludes skipping tests entirely. |
| Claims done without running any checks | 41 | 41 | Claude Code 17, OpenAI Codex 11, Google Antigravity 9, Cursor 3, OpenCode 1 | The agent hands back a change it never built, ran, or tested (or says it ran tests when it didn't), so the user finds basic breakage; this excludes cases where checks ran but were weak. |
| Green tests while real behavior is broken | 28 | 32 | Claude Code 15, OpenAI Codex 6, Cursor 5, Amp 1, Google Antigravity 1 | The agent reports success because its unit or mocked tests pass, but it never exercised the running app, UI, real request, or deployed resource where the bug actually shows up; this excludes cases where test quality itself is the complaint. |
| No built-in way to run and test | 14 | 14 | OpenAI Codex 5, Claude Code 4, Google Antigravity 3, Amp 1, OpenCode 1 | The agent or product lacks the ability to build the project, run the app, or use a browser or device to check its own change, so it falls back on asking the user to verify by hand; this excludes cases where the capability exists but the agent didn't use it. |
| Skipped or abandoned verification steps | 10 | 10 | Claude Code 6, OpenAI Codex 3, Cursor 1 | The agent leaves tests skipped, stops partway so tests or audits never run, or starts long test jobs and never checks their results; this excludes never starting verification at all. |
| Ignoring user instructions about when to test | 9 | 9 | Claude Code 7, Google Antigravity 1, OpenAI Codex 1 | The agent runs tests or verification steps the user explicitly told it not to run, or overrides set limits on testing scope; this excludes excessive testing when no instruction was given. |
| Other | 61 | 62 | Claude Code 39, OpenAI Codex 15, Google Antigravity 3, OpenCode 2, Cursor 1, Devin 1 | Complaints that fit none of the modes above. |

#### Disproportionate re-testing that burns time and quota

- Claude Code, 2026-10-02, r/vibecoding (Reddit): “i've noticed claude code with opus 5.5 on ultracode sets up agents for many of the tasks you mentioned. sometimes i find it even too thorough and using up tokens on checking and checking again and again unnecessarily.” [source](https://www.reddit.com/r/vibecoding/comments/1wvq0py/unpopular_opinion_vibe_coders_are_shipping_better/pde593b/)
- OpenCode, 2026-09-30, r/opencode (Reddit): “it often double check/triple checks things, i think it is being too cautious.” [source](https://www.reddit.com/r/opencode/comments/1wtgjq0/space_bunny_free_period_is_extended_to_1005/pcy2l0n/)
- Claude Code, 2026-09-28, r/ClaudeCode (Reddit): “so many checks and re checks. we need our os up and running. every corner must be checked. new feature? 100 checks. old feature deleted? 100 checks” [source](https://www.reddit.com/r/ClaudeCode/comments/1wqnh3q/me_after_opus_55_release/pck9k69/)

#### Self-written tests that pass by construction

- Claude Code, 2026-10-18, @ClaudeDevs (X): “@claudedevs kind of wish it would natively reviewed in a neutral unbiased way though. most of the time, unless instructed, it will test to pass rather than test to failure so things slip through the cracks.” [source](https://twitter.com/2102840901856890880/status/2111803927914291487)
- Claude Code, 2026-09-26, r/ClaudeCode (Reddit): “oh man the 3am forensics shift. lived this. the thing nobody warns you about is the agent grades its own homework, so of course the tests pass. green suite stopped meaning "it works" the second the thing writing the code also got to decide what passing means.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wnfj10/claude_code_deleted_a_failing_migration_at_3am_so/pc7bi25/)

#### Claims done without running any checks

- Google Antigravity, 2026-10-16, @antigravity (X): “@antigravity but why gemini do i give task edit it's done as compare to other first think where and which then edit and test then gives , so fix your system prompts related that.” [source](https://twitter.com/2077305807457411073/status/2110890762770829379)
- Claude Code, 2026-09-23, r/ClaudeCode (Reddit): “asking it to review its own work is like asking my dog if he ate the bin bag. he's gonna say no and he's gonna look real confident about it.eview its own work is like asking my dog if he ate the bin bag. he's gonna say no and he's gonna look real confident about it.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wnsg36/for_people_giving_claude_code_entire_features/pbhgx8y/)

#### Green tests while real behavior is broken

- Cursor, 2026-09-24, @cursor_ai (X): “@cursor_ai the agent writes the code, writes the monitoring plan, then verifies its own deploy. we reinvented grading your own homework and gave it a dashboard” [source](https://twitter.com/2005670519929249792/status/2103035100581798283)
- Cursor, 2026-09-02, @cursor_ai (X): “@cursor_ai self verification is the part i trust least. a model checking its own work shares the context that produced the mistake. what catches things in my builds is a separate script that can fail the run, with no model in it.” [source](https://twitter.com/1537733038200786944/status/2094981420091613388)

#### Skipped or abandoned verification steps

- Claude Code, 2026-10-15, r/ClaudeCode (Reddit): “i stopped trying to check what it ran and just made the stop hook run the full suite itself. if it fails, the hook exits with code 2 and the error output, which blocks the stop and sends claude back to fix it. learned that one the hard way after a partial test run let a typo through that broke a few paid runs on my server.” [source](https://www.reddit.com/r/ClaudeCode/comments/1x6lyim/all_tests_pass_in_the_summary_vs_what_it_actually/pgwoshj/)
- Claude Code, 2026-09-13, r/ClaudeCode (Reddit): “something like that! you have no idea how sick i am of hearing “you’re right and that’s my fault.” every 20 minutes. it started some tests that finished 30 minutes ago. didn’t even bother to check. just sat there.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wfih9c/opus_not_right_today/p9ng5ja/)
- Claude Code, 2026-10-02, r/ClaudeCode (Reddit): “haha that’s fair and i’m not saying it’s not without flaws. but my problem was way more central, it didn’t even consider half of the decision, it broke rules, it didn’t run all tests, generally absurd amounts of degraded performance. have you tried ponytail btw?” [source](https://www.reddit.com/r/ClaudeCode/comments/1ww61pb/opus_fixing_sols_mess/pdhx8eg/)

#### Ignoring user instructions about when to test

- Claude Code, 2026-09-16, @ClaudeDevs (X): “@claudedevs cool, everything is good, aslong as you don't ask it to check its own work/abilities? [link]” [source](https://twitter.com/465988775/status/2100310571660755421)
- OpenAI Codex, 2026-09-09, r/codex (Reddit): “one thing i usually ask astra, is to not test anything. in my use-case, testing is just a couple of minutes, but astra keeps testing for very long periods of time, consuming more tokens.” [source](https://www.reddit.com/r/codex/comments/1wbf3cc/codex_usage_saver/p8phdk9/)
- Claude Code, 2026-09-06, r/ClaudeCode (Reddit): “i changes the comments like you requested, rerunning the test suite why” [source](https://www.reddit.com/r/ClaudeCode/comments/1w8ssvd/claude_code_crossexamines_my_repo_like_i_killed/p853u6j/)

#### Other

- Claude Code, 2026-10-17, r/ClaudeCode (Reddit): “its so random .. sometimes clause tests everything.. sometimes it doesn't test at all.. i have no clue what triggers it” [source](https://www.reddit.com/r/ClaudeCode/comments/1x7zbvd/claude_runs_1800_useless_tests_creates_more/ph97d3s/)
- OpenCode, 2026-10-15, r/opencode (Reddit): “yea i even asked other ai models to give me instructions and it didn't work, but i was looking at that option bcz of the output space bunny free was giving me using the opencode cli, like claude automatically went on a hardcore verification loops, but my opencode did none so i had to manually ask it to do them and ended up using up my usage for that.” [source](https://www.reddit.com/r/opencode/comments/1x6h2ed/using_opencode_free_tier_in_claude_code/pgw134m/)

## Top requests

What users ask to add or change, most asked first. 60 user-weeks ask for something. Requests do not change the Feedback Score. Rule: A separate pass by a large language model reads every counted post and extracts what the user asks the agent or its vendor to add or change, with the criteria it maps to and a short normalised wording; it does not touch the labels or the Feedback Score. A large language model groups the wordings within each criterion (the first criterion the request maps to) into themes, and a second pass merges themes that ask for the same change under different criteria; a merged theme sits under the criterion most of its requests map to, and code counts it once. A theme counts distinct user-weeks that ask for it, per agent; across agents, one user-week per agent. Themes asked in fewer than 2 user-weeks, and requests that share no theme, are not shown. Examples: up to 3 posts per theme from different users, without slurs: whole posts of 60 to 450 characters with at least 8 words beyond handles and links, posts of at most 280 characters first, then the newest.

| Rank | Request | User-weeks | Posts | Agents (user-weeks) |
|---|---|---|---|---|
| 1 | Mandatory verification before claiming done | 17 | 18 | Claude Code 5, OpenAI Codex 4, Cursor 4, OpenCode 2, Google Antigravity 1, GitHub Copilot 1 |
| 2 | Automatic checks after every change | 4 | 4 | Cursor 2, Claude Code 1, OpenAI Codex 1 |
| 3 | Eval and prompt testing tooling | 4 | 4 | OpenAI Codex 1, Cursor 1, Factory 1, Pi 1 |
| 4 | Run only relevant tests, skip redundant runs | 4 | 4 | Claude Code 2, OpenAI Codex 2 |
| 5 | Verify against live runtime or deployed state | 4 | 4 | Cursor 3, OpenAI Codex 1 |
| 6 | Built-in end-to-end testing system | 3 | 3 | Google Antigravity 1, Claude Code 1, Cursor 1 |
| 7 | Prove regression with failing test first | 3 | 3 | Cursor 2, Claude Code 1 |
| 8 | Toggle to disable automatic browser testing | 2 | 2 | OpenAI Codex 1, Cursor 1 |

### 1. Mandatory verification before claiming done

- Claude Code, 2026-10-16, @ClaudeDevs (X): “@claudedevs i’d trade that head start for one extra check before “done” 😂” [source](https://twitter.com/2006571612439773184/status/2111211753120145826)
- OpenCode, 2026-10-10, r/opencode (Reddit): “splitting the plan per task is the right move. add one done-check line to each file, a command or an assertion, otherwise the agent marks a task done because the file changed rather than because the work works.” [source](https://www.reddit.com/r/opencode/comments/1x03juj/some_quick_lessons_about_agent_orquestration_i/pf1j5bt/)
- Claude Code, 2026-10-02, r/ClaudeCode (Reddit): “you should have both regardless, imo...but they guard the repo, not the agent. i want this caught at the end of the turn, while it still has the context to fix it...” [source](https://www.reddit.com/r/ClaudeCode/comments/1ww3knt/claude_kept_telling_me_all_tests_pass_after/pdhtjgw/)

### 2. Automatic checks after every change

- Cursor, 2026-09-02, @cursor_ai (X): “@cursor_ai self-verification matters more than the bench number. tip: give the repo a single check command (lint + tests) so verifying is cheap - otherwise the model just re-reads its own diff and declares it correct.” [source](https://twitter.com/1225465205896794112/status/2095142600743252049)
- Claude Code, 2026-09-15, r/ClaudeCode (Reddit): “yeah exactly. deterministic and outside the coding agent is what i’m aiming for. claude can create/change whatever it wants, but it shouldn’t be able to change the thing deciding if login/payment/etc still works. automatically running those after relevant changes would be ideal. i’m still experimenting with where to draw the line though - running everything after every small change gets wasteful pretty quickly.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wdgt78/how_are_you_verifying_claude_codes_changes/p9ycxuf/)

### 3. Eval and prompt testing tooling

- Factory, 2026-10-01, @FactoryAI (X): “@droid @factoryai i’d love to see a built-in way to batch test prompts without manual copy-pasting.” [source](https://twitter.com/2029192070183960579/status/2105448016417329162)
- Cursor, 2026-09-02, @cursor_ai (X): “@cursor_ai self-verification is valuable only when it is independent of the first solution. i’d measure how often the agent writes a failing test first, catches its own regression, and recovers without human hints. end-to-end completion is a stronger signal than first-pass code quality.” [source](https://twitter.com/1574567751494107136/status/2095019847054991812)

### 4. Run only relevant tests, skip redundant runs

- Claude Code, 2026-09-30, r/ClaudeCode (Reddit): “now that the merge queue is live, drop the full run on main after each merge - the queue already tested the exact commit that lands, so that's 10-15 min per pr spent proving the same thing twice. keep main to the staging deploy + a browser smoke.” [source](https://www.reddit.com/r/ClaudeCode/comments/1wtplm6/whats_your_preferred_review_and_debugging_workflow/pd0rt3s/)
- Claude Code, 2026-09-28, r/ClaudeCode (Reddit): “i typically run with lots of top level agents with specific tasks. i also have noticed that they do a lot of testing. it might be worth splitting your tests up into different parts so that they can be easily targeted to the changes and not have to run the entire suite of tests. it should be automatic though, don't even let the agent decide. make test -> find relevant changes -> only run tests on files that are in the change tree [link]” [source](https://www.reddit.com/r/ClaudeCode/comments/1ws4qmd/anyone_else_does_30_hours_of_unattended/pcir3lv/)

### 5. Verify against live runtime or deployed state

- Cursor, 2026-10-03, @cursor_ai (X): “@cursor_ai after a cloud agent patches a regression, can rollouts verify the fix against the production condition that triggered it, as well as the test suite?” [source](https://twitter.com/2073791950856282112/status/2106337818578751701)
- Cursor, 2026-10-02, @cursor_ai (X): “@cursor_ai the useful boundary is rollback scope: verify the fix against the deployed state, not just the changed diff.” [source](https://twitter.com/2078041339099578369/status/2106079230975193437)
- Cursor, 2026-09-05, @cursor_ai (X): “burning ai usage fixing the same bot-introduced ui bugs again and again isn’t a workflow. visual changes should require build + on-device proof before “done.” this needs to be a product-level reliability issue, not user babysitting. @bot @cursor_ai” [source](https://twitter.com/1630452238593437696/status/2096139574087196770)

### 6. Built-in end-to-end testing system

- Cursor, 2026-10-03, r/cursor (Reddit): “importing files into chat is kinda busted, and i cannot select elements in the browser view. you guys have got to add some kind of comprehensive e2e system. these are features that have been a part of cursor for a long time. please fix it.” [source](https://www.reddit.com/r/cursor/comments/1wwb9eq/latest_update_what_the_heck_did_you_do/)
- Google Antigravity, 2026-10-06, @antigravity (X): “@adhidesign @googledeepmind @antigravity *an attached window/browser that is able to open apps or sites...annotations like how codex has *e2e testing suite which is visible. *skills under customizations are too unstructured and random.. bring better ux for it. *interactive artifacts like claude.” [source](https://twitter.com/1867830882163208193/status/2107343879150469486)
- Claude Code, 2026-09-28, r/ClaudeCode (Reddit): “testing is the one thing i don't rely on agents fully for. unit tests, sure, ux and functional end to end testing, hard no. they don't understand ux in all situations and they say stuff works that doesn't work or doesn't work exactly how a human would expect it to. i'd love to be able to offload testing fully, it's the final frontier in agentic coding for me at least, it's what i spend the most time actively doing.” [source](https://www.reddit.com/r/ClaudeCode/comments/1whdo6u/today_i_lost_any_shred_of_self_respect_that_i_had/pcj10wl/)

### 7. Prove regression with failing test first

- Claude Code, 2026-10-17, @ClaudeDevs (X): “@claudedevs for the pre-pr verification step, i’d run the new regression test on the pre-fix commit too. that catches a test which passes with or without the fix, and gives the reviewer a concrete failing-to-passing result to inspect.” [source](https://twitter.com/902711003762245632/status/2111313249476227301)
- Cursor, 2026-10-02, @cursor_ai (X): “@cursor_ai i'd want the agent to write a failing test before touching the fix. can the handoff include a repro, not just the offending pr?” [source](https://twitter.com/1905022193588752384/status/2106075167688421408)
- Cursor, 2026-09-18, @cursor_ai (X): “@cursor_ai automatic tracking of pr is very worry-free, but i will add another layer: can the failed tasks be reproduced, and does it really pass regression after being fixed.” [source](https://twitter.com/1628996445654188033/status/2100827337873047880)

### 8. Toggle to disable automatic browser testing


## Every agent

| Agent | Overall rank | Reading | Customer love | 95% interval | n | Praise | Complaint |
|---|---|---|---|---|---|---|---|
| [Claude Code](https://feedbackbench.com/coding-agents/agents/claude-code.md) | 1 | 1st of 3 | 0.563 | 0.516–0.607 | 399 | 258 | 141 |
| [Google Antigravity](https://feedbackbench.com/coding-agents/agents/antigravity.md) | 14 | 2nd of 3 | 0.481 | 0.463–0.498 | 31 | 13 | 18 |
| [OpenAI Codex](https://feedbackbench.com/coding-agents/agents/codex.md) | 10 | 3rd of 3 | 0.461 | 0.429–0.491 | 138 | 71 | 67 |
| [Cursor](https://feedbackbench.com/coding-agents/agents/cursor.md) | 7 | Too few posts | – | – | 25 | 10 | 15 |
| [Devin](https://feedbackbench.com/coding-agents/agents/devin.md) | 2 | Too few posts | – | – | 16 | 13 | 3 |
| [OpenCode](https://feedbackbench.com/coding-agents/agents/opencode.md) | 3 | Too few posts | – | – | 15 | 7 | 8 |
| [Amp](https://feedbackbench.com/coding-agents/agents/amp.md) | 5 | Too few posts | – | – | 10 | 8 | 2 |
| [Cline](https://feedbackbench.com/coding-agents/agents/cline.md) | 11 | Too few posts | – | – | 4 | 3 | 1 |
| [GitHub Copilot](https://feedbackbench.com/coding-agents/agents/copilot.md) | 9 | Too few posts | – | – | 3 | 2 | 1 |
| [Pi](https://feedbackbench.com/coding-agents/agents/pi.md) | 4 | Too few posts | – | – | 2 | 2 | 0 |
| [Factory](https://feedbackbench.com/coding-agents/agents/factory.md) | 6 | Too few posts | – | – | 2 | 2 | 0 |
| [Kiro](https://feedbackbench.com/coding-agents/agents/kiro.md) | 13 | Too few posts | – | – | 1 | 1 | 0 |
| [Zed](https://feedbackbench.com/coding-agents/agents/zed.md) | 8 | Too few posts | – | – | 0 | 0 | 0 |
| [Conductor](https://feedbackbench.com/coding-agents/agents/conductor.md) | 12 | Too few posts | – | – | 0 | 0 | 0 |
| [Warp](https://feedbackbench.com/coding-agents/agents/warp.md) | 15 | Too few posts | – | – | 0 | 0 | 0 |
| [Grok Build](https://feedbackbench.com/coding-agents/agents/grok-build.md) | 16 | Too few posts | – | – | 0 | 0 | 0 |
| [Augment Code](https://feedbackbench.com/coding-agents/agents/augment.md) | 17 | Too few posts | – | – | 0 | 0 | 0 |

## Posts

Receipts rule: Up to 5 praise and 5 complaint posts per area and 3 per criterion. Each is a whole post of 60 to 450 characters (700 for areas) with at least 8 words beyond handles and links, that judges the criterion, whose labels are all praise or all complaint, and that contains no slur. Posts that touch the fewest criteria come first, then posts of at most 280 characters, then the newest. A second large language model reads the first 3 candidates per slot and keeps a post only if it clearly praises, or clearly complains about, the agent on that criterion. Links and personal details removed by the source show as marks such as [link].

### Claude Code

- Praise, 2026-10-14, r/ClaudeCode (Reddit): “claude handles all of this for me, and checks for bugs after. it’s been a part of my workflow for ages.” [source](https://www.reddit.com/r/ClaudeCode/comments/1x5zktq/new_claude_desktop_look_is_awful/pgr2l9c/)
- Praise, 2026-10-08, r/ClaudeCode (Reddit): “the apology is nice, but ‘i added a regression test so i can’t do it again’ is the real love language 😂” [source](https://www.reddit.com/r/ClaudeCode/comments/1x0leat/youre_right_and_i_was_wrong_i_love_seeing_that/peljo3h/)
- Complaint, 2026-10-18, @ClaudeDevs (X): “@claudedevs kind of wish it would natively reviewed in a neutral unbiased way though. most of the time, unless instructed, it will test to pass rather than test to failure so things slip through the cracks.” [source](https://twitter.com/2102840901856890880/status/2111803927914291487)
- Complaint, 2026-10-17, r/ClaudeCode (Reddit): “its so random .. sometimes clause tests everything.. sometimes it doesn't test at all.. i have no clue what triggers it” [source](https://www.reddit.com/r/ClaudeCode/comments/1x7zbvd/claude_runs_1800_useless_tests_creates_more/ph97d3s/)

### Google Antigravity

- Praise, 2026-10-10, @antigravity (X): “@antigravity pulling designs, building native components, verifying in an emulator and running tests is the full loop rather than a code snippet. closing verification inside the agent flow is what separates a coding demo from something you can merge.” [source](https://twitter.com/1985864228339924995/status/2108932911617769799)
- Praise, 2026-09-03, r/google_antigravity (Reddit): “the thing i like is ,it finally test before doing work and modifies until what is correct thing is found by testing before changing code whereas, 3.7 was just changing code and not testing.” [source](https://www.reddit.com/r/google_antigravity/comments/1w5xdio/positive_of_38_flash/)
- Praise, 2026-10-18, @antigravity (X): “@antigravity also, seeing it review and verify its own work using the browser plugin in antigravity was very cool too! [link]” [source](https://twitter.com/1987543750323933184/status/2111840138213163211)
- Complaint, 2026-10-16, @antigravity (X): “@antigravity but why gemini do i give task edit it's done as compare to other first think where and which then edit and test then gives , so fix your system prompts related that.” [source](https://twitter.com/2077305807457411073/status/2110890762770829379)
- Complaint, 2026-09-03, r/google_antigravity (Reddit): “nah like claude will check what is actually happening. while gemini will be like yeah that works without even checking it (it will check after i point that it did not check, which is weird af), feels like its rushing to do something and not actually be grounded to truth.” [source](https://www.reddit.com/r/google_antigravity/comments/1w5i29e/review_of_gemini_38_flash_from_a_person_who/p7nusiq/)
- Complaint, 2026-10-07, r/google_antigravity (Reddit): “i do that, it's still not good at making secure apps and testing” [source](https://www.reddit.com/r/google_antigravity/comments/1wzp89q/did_38_flash_get_better/pedz5tt/)

### OpenAI Codex

- Praise, 2026-10-07, r/codex (Reddit): “yes, that was cancelled thoroughly. what also helped me a lot is giving codex access to the emulator and just letting him test a lot of things there.” [source](https://www.reddit.com/r/codex/comments/1wzr5on/codex_helped_me_launch_my_football_tycoon_testing/peeaaz8/)
- Praise, 2026-10-03, X search: OpenAI Codex, Codex CLI, Codex app (X): “chance to win an openai prize. i’m entering the openai devday side quest sweepstakes. #openaisidequest codex cli took a deliberately insecure reset-token generator, switched it to cryptographic randomness, added a focused pytest and proved the patch passes. [link]” [source](https://twitter.com/2076219635909660672/status/2106325125276569679)
- Praise, 2026-09-15, r/codex (Reddit): “i love it, makes sanity and smoke tests and even generates a report... i like quality, no matter how trivial” [source](https://www.reddit.com/r/codex/comments/1wgzmul/coding_benchmarks_should_also_reward_the_leanest/pa07r9c/)

### Cursor

- Praise, 2026-09-02, @cursor_ai (X): “@cursor_ai self-verification is the part that changes agentic coding. the agent does not just produce a diff; it checks the work against a target. i still want a human review, but the first line of defense can finally be inside the loop.” [source](https://twitter.com/2086447538027073536/status/2095037549823643664)
- Praise, 2026-09-02, @cursor_ai (X): “@cursor_ai fable 5.1 in cursor is a game changer self verification makes all the difference.” [source](https://twitter.com/2030308839644704768/status/2095055085566914759)
- Praise, 2026-10-12, @cursor_ai (X): “@poteto yes yes yes.... the first time i woke up to my @cursor_ai cloud agent's video demo verifying it's work i never looked back” [source](https://twitter.com/2520407760/status/2109459497416556842)
- Complaint, 2026-09-24, @cursor_ai (X): “@cursor_ai the agent writes the code, writes the monitoring plan, then verifies its own deploy. we reinvented grading your own homework and gave it a dashboard” [source](https://twitter.com/2005670519929249792/status/2103035100581798283)
- Complaint, 2026-09-02, @cursor_ai (X): “@cursor_ai self verification is the part i trust least. a model checking its own work shares the context that produced the mistake. what catches things in my builds is a separate script that can fail the run, with no model in it.” [source](https://twitter.com/1537733038200786944/status/2094981420091613388)
- Complaint, 2026-09-05, @cursor_ai (X): “burning ai usage fixing the same bot-introduced ui bugs again and again isn’t a workflow. visual changes should require build + on-device proof before “done.” this needs to be a product-level reliability issue, not user babysitting. @bot @cursor_ai” [source](https://twitter.com/1630452238593437696/status/2096139574087196770)

### Devin

- Praise, 2026-09-17, @DevinAI (X): “nice @devinai helping me test coworker in windows it makes recordings of the tests so i can replay and verify [link] [link]” [source](https://twitter.com/1946635320797347840/status/2100651879219044800)
- Praise, 2026-09-12, @cognition (X): “@roliumgens @cognition self-verification on a small prompt is a pretty good sign for day-to-day coding work” [source](https://twitter.com/2058565082628739072/status/2098766463712829447)
- Praise, 2026-09-29, @DevinAI (X): “@devinai 3/ what surprised me: i'd report a bug with a screenshot, and devin would reproduce it, fix it, click through the app to check, and ship the release. signed, notarized, auto-updating.” [source](https://twitter.com/2044489806516736000/status/2104875030651789570)

### OpenCode

- Praise, 2026-09-28, @opencode (X): “@iam_chonchol @opencode the fact that it tested, found bugs, and fixed them before handing over the game is the impressive part.” [source](https://twitter.com/313123169/status/2104361222850158649)
- Praise, 2026-09-28, @opencode (X): “@iam_chonchol @opencode finding two bugs on its own makes bunny blast testing itself in code surprisingly impressive.” [source](https://twitter.com/1644781869844635650/status/2104428564435370444)
- Praise, 2026-10-17, r/opencode (Reddit): “i know im very very late to it. but i started using it today and wow. i can actually vibe code apps that work not just buggy ones now. i just let ai code and test it and compile it. i vibe coded a nice app with it today that im very happy with.” [source](https://www.reddit.com/r/opencode/comments/1x8j55b/opencode_is_insane/)
- Complaint, 2026-09-30, r/opencode (Reddit): “it often double check/triple checks things, i think it is being too cautious.” [source](https://www.reddit.com/r/opencode/comments/1wtgjq0/space_bunny_free_period_is_extended_to_1005/pcy2l0n/)
- Complaint, 2026-09-03, r/opencodeCLI (Reddit): “it seems like it's trained to check it's work alot to prevent mistakes. it's excessive like gpt 5.4 used to be.” [source](https://www.reddit.com/r/opencodeCLI/comments/1w5zifw/meta_muse_spark_13_is_free_on_opencode_zen/p7kuyzm/)
- Complaint, 2026-10-15, r/opencode (Reddit): “yea i even asked other ai models to give me instructions and it didn't work, but i was looking at that option bcz of the output space bunny free was giving me using the opencode cli, like claude automatically went on a hardcore verification loops, but my opencode did none so i had to manually ask it to do them and ended up using up my usage for that.” [source](https://www.reddit.com/r/opencode/comments/1x6h2ed/using_opencode_free_tier_in_claude_code/pgw134m/)

### Amp

- Praise, 2026-10-15, @AmpCode (X): “quinn showed this at frontiers! his talk make me give it another shot. its crazy funny enough i was trying to grok with how you gain the confidence in a push to main, and it really comes down to the little features in amp. such as the screenshots, or effectively built in demos. you're all crushing it” [source](https://twitter.com/3339946989/status/2110804677457781028)
- Praise, 2026-10-18, @AmpCode (X): “"give me irrefutable proof that this works" is a huge lightbulb moment for me on @ampcode full video walkthroughs and screenshots in an actual browser. damn, that's good.” [source](https://twitter.com/54493959/status/2111794088353644954)
- Praise, 2026-10-12, @AmpCode (X): “this is why orbs are powerful: @ampcode could test this feature end to end on linux, windows, and mac, and was sending me regular videos of how things work. my work was thinking at high level through all the "what if..." scenarios and guiding the agent toward a solution. [link]” [source](https://twitter.com/1969028246/status/2109673411697934406)

### Factory

- Praise, 2026-10-13, @droid (X): “a real bug: clockedin's tests passed. its attendance tab crashed. @droid reproduced it on the iphone simulator with @swmansion's argent, fixed it, got overruled by lint, fixed it again, and checked the phone. run 3 of 3 · #closetheloop [link]” [source](https://twitter.com/947588323/status/2109992549452751114)
- Praise, 2026-10-11, @droid (X): “tap the heart in pocket-no. favorites stays empty. @droid reproduced it on the iphone simulator with @swmansion's argent, fixed it, caught that its first check proved nothing, and verified a fresh add. run 1 of 3 · #closetheloop [link]” [source](https://twitter.com/947588323/status/2109267781371760969)

### Kiro

- Praise, 2026-10-05, @kirodotdev (X): “built with kiro: an audit that checks every amazon bedrock managed kb chunk still matches its japanese source, per department. kiro-generated property tests caught a real unicode bug. @kirodotdev #kirouniversity #buildwithkiro [link] [link]” [source](https://twitter.com/1388323577582153731/status/2107194638306304368)