Desktop quickstart

Goal: create a file in a chosen directory, open it, and verify the result. This first task uses Markdown for easy inspection.

1. Prepare a working directory

Install and launch the application. Create an empty practice folder, select it on the home screen, choose an available model, and select Request approval. The directory identifies the files relevant to this task.

2. Submit a precise request

Create “getting-started.md” in the current working directory with three sections: goal, steps, and acceptance criteria. Create only this file. Report its saved location and read it back to verify its contents.

The request defines scope, output, and verification.

3. Inspect progress and approvals

Review the plan, tool activity, and file changes. For approvals, check the operation, directory, and purpose. If you decline, explain an alternative such as a different output location.

Add requirements in the same conversation, for example: “Include the saved location in the acceptance criteria.” Wait for feedback to avoid duplicate submissions.

4. Verify the result

• The chosen directory contains “getting-started.md”.
• The file opens with all three sections.
• No unrelated files were changed.
• The response describes execution and verification.

A completion message alone does not establish a correct save. Inspect the Diff and tests for code, open final office documents, and check page state after web submissions.

Task flowchart

flowchart TD
    S([Start]) --> A[Choose directory, model, and permissions]
    A --> B[Send goal and acceptance criteria]
    B --> C[Inspect execution activity]
    C --> D{Approval required?}
    D -->|Yes| E{User approves?}
    E -->|Yes| F[Execute tool and return result]
    E -->|No| G[Explain limit or revise approach]
    D -->|No| F
    G --> C
    F --> H{Task complete?}
    H -->|No| C
    H -->|Yes| I[Check file and verification results]
    I --> J{Criteria satisfied?}
    J -->|No| K[Refine the request in this conversation]
    K --> C
    J -->|Yes| T([End])

Legend: rounded endpoints mark start and end, rectangles mark processing, diamonds mark decisions, and branches name outcomes.

Next steps

Read Tasks and permissions, then explore Coding, Office documents, or Computer automation.