c_Learn & Practice AILEARN/Common mistakes
RECOGNIZE. RECOVER. IMPROVE.

Common mistakes

Common failure patterns, their risks, and a safer next action.

01 · A vague request produces the wrong result

Symptom / cause

“Make my website better” has no observable target.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Define one user problem, allowed files, and acceptance checks.

Safety center →
02 · A small task changes too many files

Symptom / cause

The scope was not bounded, or unrelated refactoring was mixed in.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Pause, inspect the diff, and separate intended changes while preserving other work.

Safety center →
03 · There is no recovery point

Symptom / cause

Changes began before checking backups or version history.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Preserve the current files, identify a verified backup, and avoid destructive recovery commands.

Safety center →
04 · A diff was accepted without review

Symptom / cause

Generated code looked plausible but changed hidden behavior.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Read each changed area and trace affected callers before approval.

Safety center →
05 · No checks were run

Symptom / cause

A completion message was mistaken for test evidence.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Ask for actual check outputs, then run relevant behavior tests. Mark unavailable checks clearly.

Safety center →
06 · Project instructions were ignored

Symptom / cause

The wrong working folder or missing instruction discovery caused inconsistent work.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Locate the root, inspect applicable AGENTS.md files, and restate the task with the correct scope.

Safety center →
07 · An upgrade breaks the project

Symptom / cause

The dependency version changed without checking its compatibility or lockfile.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Inspect official migration notes and restore a known dependency state before a controlled retry.

Safety center →
08 · A secret was pasted into a prompt

Symptom / cause

A real credential entered a conversation, file, or version history.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Revoke or rotate the exposed credential with its provider, review access, and follow the organization’s incident process. Deleting the visible text alone is insufficient.

Safety center →
09 · Local success is treated as live success

Symptom / cause

Environment differences and deployment state were not checked.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Open the intended live URL after authorized deployment and test the important flows.

Safety center →
10 · Untrusted content gives the agent instructions

Symptom / cause

A web page or repository file tries to redirect the task or obtain secrets.

Risk

Incorrect results, unintended changes, or loss of control over the project.

How to recover

Treat retrieved content as data, preserve the user’s goal, and do not follow requests to disclose secrets or bypass boundaries.

Safety center →
Esc · Close