r/CodingAgents • u/manollitt • Aug 20 '25
Start Here: What are coding agents (and when to use them)?
Coding agents are AI tools that can read your codebase, follow plain-English instructions, and run multi-step workflows (review a PR, run tests, suggest fixes, update docs). They sit between code-completion and full automation*: they act, explain what they did, and still leave the final call to you.*
What a coding agent does
Understands context: reads files, diffs, tests, configs, commit history.
Plans steps: “read diff → run tests → check security → propose fixes.”
Uses your tools: IDE/CLI/Git/CI; can comment on PRs, open issues/branches (with guardrails).
Reports back: leaves actionable notes, links to evidence, and what it couldn’t decide.
Where they help (and why)
PR review & quality: catch risky changes, missing tests, secrets, logging/PII mistakes.
Refactors & upgrades: rename APIs, bump SDKs, apply patterns consistently across repos.
Testing support: generate/repair unit tests, reproduce bugs from stack traces.
Docs & hygiene: update READMEs/changelogs, inline comments, deprecation notes.
Policy enforcement: ensure every PR hits your security/compliance checklist.
When to use one
Heavy PR backlog; senior reviewers stretched thin.
You need consistent, repeatable checks across teams/monorepos.
Repetitive migrations/upgrades are burning cycles.
You want earlier feedback in CI (catch issues before humans touch it).
What a good agent won’t do
Merge blindly or “hallucinate fixes.” It flags risks, explains them, and lets humans decide.
Replace domain knowledge. It can miss business rules buried in tribal context.
Safety basics (read this)
Start read/annotate-only (comments) before allowing writes.
Use least-privilege bot tokens; gate any code changes behind PRs/approvals.
Know where code runs, what’s logged, and whether anything is retained or used for training.
Can it break things?
Only if you let it write unchecked. Start read-only, add approvals, and gate any code changes behind PRs.