You can open Cursor or Claude Code, type "add i18n to this app", and get something that works. For a small app with one page and a dozen strings, that may be all you need.
The trouble starts with a real app: a few hundred strings across dozens of components, a second language next month, and new features every week after that. Here is where a coding agent tends to go wrong, what you can do about it if you stay with an agent, and when a dedicated tool is worth it.
1. It only translates the files it reads
An agent works through a context window. It opens the files it thinks matter, wraps the text it sees, and stops when it decides it's done. What gets missed is predictable:
Attributes : placeholder , alt , title , aria-label . Easy to skip because they're not between tags.
Copy in data : arrays of feature cards, nav items, table column headers, select options defined at the top of a file.
Strings far from the UI : validation messages, empty states, toast text in a hook.
None of these break the build.…