Plandex CLI Cheatsheet - Terminal Planning AI Coding Agent (pdx)

The split between coding agents today is less about model quality than about how changes reach your files. Plandex, invoked as pdx, takes the conservative route: edits accumulate inside a protected plan, you review them, and only then are they applied to the project, with rollback available at every step. What separates it from agents that write straight into the working tree is that a plan is a first-class artifact, created with new, extended with tell, and scoped with load so only chosen files enter context. This table is grouped by installation and auth, planning and loading, execution and iteration, and branching, showing how to append requirements across turns and how to break one large change into independently verifiable batches. Reach for it before a refactor spanning a dozen files, when requirements are still moving but you want the shared understanding written down, or when a migration decision needs to stay auditable. The dividing line is that you no longer write snapshot scripts to guard against a bot rewriting your files.