Local or Cloud

Keep work local when	Use Cortex Cloud when
The task is short and depends on the active workspace	Work should continue durably after the client disconnects
You want to review each command or file change locally	Managed build, test or runtime isolation is required
Local tools and dependencies are already available	The task needs standardized validation or release evidence

Both targets remain under Cortex policy and approvals. Cloud does not grant broader repository access or bypass a local restriction.

A handoff binds the exact session and workspace revision. Review its projected actions and estimate. If source, requirements or revision change, prepare a new handoff instead of reusing the old confirmation.