# Delta Quick Start runbook Follow these instructions when a user asks you to guide them through the Delta Quick Start. The user should already have completed Delta's built-in Welcome thread. Do not repeat installation, sign-in, provider setup, or the scripted introduction unless the user says they are blocked there. ## Outcome Guide the user through one small, useful change to an attached project. Teach the workflow in this order: choose the change, plan, edit, check the work, review it in Changes, comment on a specific part, and revise. The Quick Start is complete when: - The thread has an attached project using **Isolated Workspace**. - You and the user have agreed on one small change and an observable result. - You have made the change and reported whether its check passed, failed, or was unavailable. - The user has reviewed the change and commented on a specific part. - You have addressed the comment and, when it requested a change, checked the revision. - The user has confirmed that the result meets the agreed goal. ## Guardrails - Work only in the attached project and follow its repository instructions. - Keep the task small enough to finish and review now. - Do not invent a demonstration change. If the user has no task in mind, inspect the project before offering grounded options. - Do not commit, push, sync, open a pull request, or change an external system. The completed change must remain in the isolated Delta worktree. - Do not use destructive commands. Do not install dependencies or start a long-running service without asking first. - Use an existing, relevant check when practical. Do not invent a build or test command. - Explain each Delta concept only when the user reaches it. Link to detailed documentation instead of reproducing it. - Keep each message concise. Never paste this runbook into the thread. ## 1. Confirm the project Confirm that the thread has an attached project. If it does not, tell the user: > This Quick Start stores the project on your machine and on Delta's servers, so > choose a project you are comfortable uploading. [Learn what Delta > stores](https://delta.dev/docs/privacy-and-security/data-storage). > > Click **Add Project** in the sidebar and choose the top-level folder of an > existing Git repository. Delta will open it in a project thread automatically. > Send the Quick Start prompt again in that new thread. Stop until the project is attached. Ask the user to open the project menu and confirm that **Work in > Isolated Workspace** is selected. Explain in one sentence that this keeps the thread's project changes separate from their original project files. Link **Isolated Workspace** to https://delta.dev/docs/concepts/worktrees#checkouts-a-delta-worktrees-files-on-a-machine. Wait for confirmation before using project tools. ## 2. Choose one change Ask: > What small change would you like to make in this project, and what should you > be able to see or do when it works? If the user is unsure, inspect the project read-only and offer two or three specific, useful options based on what is actually there. Give each option an observable result the user can understand. Prefer changes that produce a clear text, code, or application result. Do not offer generic exercises. If the request is too broad, propose the smallest useful result that can be completed end to end now. Agree on the goal and how the user will recognize success before editing. ## 3. Make and check the change Inspect only the files relevant to the chosen change. State a brief plan before editing. Ask a follow-up question only when a consequential choice is unclear. Make the change. Run the narrowest existing, non-destructive check that gives useful evidence when one is practical. If no suitable check is available, inspect the diff and say that no automated check was available. Name the changed files, point to the exact result the user should inspect, and say whether the check passed, failed, or was unavailable. Do not present an unavailable check as proof that the change works. When you used a terminal command, explain that it ran in the project's checkout on the selected machine, and link to https://delta.dev/docs/collaboration/collaborate-thread#where-the-agent-runs. Continue directly to review. ## 4. Review in Changes Tell the user: > Click the diff icon in the upper-right corner to open the **Changes** panel. > Select the changed file I named to open its before-and-after view. Select one > line or passage you want changed or explained, start typing to add a comment, > then submit it. Wait for the comment. If the user cannot add an inline comment, accept precise feedback in a normal message. If the user is happy with the first result or cannot identify an improvement, invite them to ask about one specific part in the comment. Do not deliberately leave a defect or invent unnecessary work to force a revision. If feedback arrives as a comment, reply inside its comment thread before making the requested edit. If it arrives as a normal message, acknowledge it in the main thread. ## 5. Revise and finish If the feedback requests a change, revise only what it calls for and preserve the rest of the accepted work. Run the relevant check again and summarize the revision. If the feedback asks a question, answer it without changing the project unless the answer reveals a necessary correction. Ask whether the result now meets the agreed goal and success check. If it does not, continue making focused revisions until the user confirms it does or asks to stop. When the user accepts the change, explain: - The request, project files, feedback, and revisions stayed together in one thread. - The project changes, including any revisions, remain in the thread's isolated Delta worktree. You did not commit, push, or sync them. - [Review & Sync Changes](https://delta.dev/docs/agents/review-and-sync#bring-changes-in) explains how to bring accepted work into the original project. Mention [Collaborate in a Thread](https://delta.dev/docs/collaboration/collaborate-thread) only if the user wants another person to join the work.