Gary Marcus Observation First said 2025-08-17

“the user has the option to accept a code change or not, but with so many changes to make at such a rapid pace, a developer in hurrry (which is almost every developer) could easily miss an attack, and ok the change or run a command”

LLMs + Coding Agents = Security Nightmare, paragraph 17. The full statement is at the source.

Our reading, the sentence that was checked:

Even with manual approval, hurried developers could easily approve malicious changes suggested by coding agents.

Assessment: Can’t be checked Not checked against evidence

Where and when Gary Marcus wrote it

Marcus on AI, LLMs + Coding Agents = Security Nightmare, paragraph 17.

Said: 2025-08-17
Source observed: 2026-10-28live page, full text, public
Evidence: Not checkedboth screens found it cannot be checked
Assessment recorded: 2026-10-29assessment marcus-llms-coding-agents-security-nightmare-270450-a1

We recorded 9 claims from this post. See every claim from this post.

The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2025-08-17. This page does not claim the wording was captured then.

What the claim commits to

Kind: Observation
Deadline, as the speaker wrote it: None stated. This site does not add one.
Deadline state when assessed: No horizon
Deadline state on 2026-10-29: No horizon (the release’s reference date)

Conditions

even with Auto-Run off (qualifier, stated by the speaker)
developer in a hurry (qualifier, stated by the speaker)

From the speaker

even with Auto-Run off
developer in a hurry

Our interpretation

None added.

This claim is not graded on evidence. The record checks that the words are quoted correctly and attributed to the right person, and that the claim is classified correctly.

Current assessment

Not graded on evidence

Outcome: Can’t be checked

Both AI providers screened this claim on their own and found that public evidence could not settle it. It is recorded and attributed, not scored.

Why it can’t be checked

Both screens gave the same reason:

Stated as a chance or a possibility, or at medium or low confidence.

Evidence: Not checked
Deadline state when assessed: No horizon
Assessment recorded: 2026-10-29
Policy version: 2026-10-28.7

Rationale

Not checked against evidence. Two independent screens, one from each provider, both found this stated as a chance or a possibility, or at medium or low confidence.

Limitations

None recorded.

Evidence (0 items)

No evidence was searched for. Both screens found that public evidence could not settle this claim.

This claim was not checked against evidence. claude-opus-5-5 (Anthropic) extracted it from the post and wrote the sentence at the top, our reading of the claim. claude-opus-5-5 (Anthropic) and gpt-6-astra (OpenAI) then screened it independently, without seeing each other’s answers. Both confirmed that the sentence says what the author said, and both found that public evidence could not settle the claim. No model wrote the assessment: code composed its text from the two screens, so there was no separate check of the final text. Code, not a model, decided whether it could be published.

Agreement between models is a check on the record, not proof that the assessment is right. Anthropic and OpenAI make these models, and some claims on this site are about those companies. How the method works.

Where it was said (1)

Said once in the sources this register covers.

2025-08-17: Marcus on AI, LLMs + Coding Agents = Security Nightmare
the user has the option to accept a code change or not, but with so many changes to make at such a rapid pace, a developer in hurrry (which is almost every developer) could easily miss an attack, and ok the change or run a command
Where
paragraph 17
Published
2025-08-17
Source observed
2026-10-28, live page
Access
full text, public

History

Assessment versions

Assessment marcus-llms-coding-agents-security-nightmare-270450-a1: Current. Outcome: Can’t be checked. Not checked against evidence. Public date not recorded.

Recorded events

2026-10-29
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.
About assessment marcus-llms-coding-agents-security-nightmare-270450-a1.