Try it when you want to walk through a plan and check edits as they happen. A repository that needs changes in several callers is a better trial than a blank editor.
Read-only Ask mode helps you trace unfamiliar code before requesting edits.
Plan mode gives you a chance to agree on the affected files.
Good fit for
Developers who want an editor organized around working with a coding agent.
Skip it if
Your debugger or extensions make an editor move impractical.
Try it on a developer’s existing setup before switching anyone’s IDE. If the team also wants issue delegation, make sure a cloud-generated PR can enter your normal review process.
Try inline suggestions without changing editors.
A cloud task can come back through the GitHub review process.
Good fit for
Developers keeping a supported IDE and teams reviewing work through GitHub pull requests.
Skip it if
Your cloud tasks regularly require coordinated edits across several repositories.
Run one known regression and one small issue. Compare time to an acceptable patch, including review, and check what the session cost. Evaluate the existing editor setup and cloud delegation separately, since either could be enough on its own.