Run a folder task or a coding session
Select the execution environment, limit the scope, and inspect actual outputs.
Use copies of practice files and an eligible plan. Keep a backup or Git history. Local tasks require the desktop app and access to the chosen folder; cloud tasks have different inputs and runtime availability.
1. Hand off a small folder task
In the new conversation experience, describe a file task and grant access only to a practice folder when prompted. On accounts with separate Cowork, open Cowork first. Specify the desired outputs and ask for a preview before changing originals. Keep the app open for tasks that use local files or apps.
In this practice folder, read the three notes and create summary.md.
Include the original filenames and unresolved questions.
Show the planned output first. Do not rename, overwrite, or delete the notes.2. Start Code in the intended environment
For software work, open Code. Choose Local for a repository on your machine, select its folder, choose a model and permission mode, and start with a read-only explanation. Cloud or SSH runs elsewhere and does not imply access to your local filesystem. Existing CLI configuration may carry over, so review it.
3. Inspect changes and output files
In Code, inspect the diff and relevant test results; use the app preview for a visible change where available. For a folder task, open the created file yourself and compare it to the originals. Confirm filenames, counts, facts, and formatting rather than relying on the completion message.
4. Troubleshoot without losing work
For a missing feature, check the account, plan, rollout state, and admin settings. For a missing local tool, check its executable path and session environment. For a stuck session, stop the task, preserve outputs, inspect the relevant logs, and check official service status. Do not delete configuration folders or local history as a first step.
Practice & self-check
Create a summary from three practice notes without modifying originals. If you use Code, run one small reviewed change and check the diff.
When you’re done, take a moment to check:
Read the official sources
CLI instructions checked against official documentation; API examples tested with simulated responses. Product-account walkthroughs were not performed.