Video · Tech With Tim ·
I Gave My AI Agent My IDE. Here's What Changed.
In short
The video tests AI agents with and without IDE tools, showing that IDEs provide deterministic code understanding, faster feedback, and scalable refactoring on large codebases. It argues that IDEs now serve as both an agent toolbox and a human review desk for professional development.
Key points
- IDE tools identify real symbol usages, types, and refactoring targets instead of relying on text search.
- PyCharm static analysis found two errors in 0.5 seconds versus 74 seconds for the full test suite.
- Agents needed bundled IDE skills to use MCP tools instead of defaulting to grep and shell commands.
- On a 220,000-line Jellyfin codebase, Rider tools reduced a large refactor from 155 seconds to 63 seconds.
- The IDE-assisted agent cost about half as much on the largest refactoring test.
- IDE tools scaled close to constant time while terminal-based work increased roughly linearly with change size.
- Developers must still inspect diffs, run tests, and take responsibility for agent-generated code.
Written by an AI model from the video’s captions and description.
Some developers say AI killed the IDE. The agent writes the code and runs the tests, so why not just live in the terminal? On small projects that works fine. But in the terminal your agent is mostly coding blind: it searches through text and hopes it lands on the right thing. Your IDE actually understands the code.



