Work with files, terminal, and Review

Find files, changes, and the terminal#

These controls appear at the top of a conversation with a project open. Hover over an unfamiliar icon to read its tooltip.

A non-Git directory still supports All files, but has no Git change counter. Do not initialize Git in an unclear location merely to make a Review control appear.

Navigate and preview a file

Open a file and use its segmented path bar to browse a parent directory, choose another file, or copy the complete path. For example, move from src/booking.ts to a neighboring schema file and verify the new filename and contents before asking for edits.

Image previews provide zoom and fit-to-window controls. For an SVG, switch between source and preview to compare its markup with the rendered image. Audio files have playback controls: play a short sample and check that it is the intended file. Previewing media does not authorize modifying the original.

Prepare a document for the example#

This example requires an existing Git repository containing README.md and a working Git command. Run git status --short first and record existing changes. If another task is editing README, use a document with clear ownership instead.

An uploaded attachment and a project-file reference are different. An uploaded copy does not automatically identify the original file to edit. Specify the project-relative path when requesting an edit.

Paste a long log as an attachment

Paste a disposable test log into the composer. Text longer than 10,000 characters or 150 lines becomes a pasted-text-…txt attachment rather than filling the editor. Check that the attachment is present, then add a short request such as “Summarize the error and quote the relevant lines.” Review the content before sending; conversion creates an attachment, not a new project source file.

Make one small change#

1. Open README.md through Browse all files and confirm it belongs to the intended project.
2. Return to the conversation, choose README.md from the @ file list, and send the request below.
3. Wait for the edit result, then click the top +N/-N counter to open changes.

Append only this section to the project's README.md:

## Local checks
Before running the project, read the environment and startup instructions in this file.

If a section with this name already exists, report it without appending a duplicate.
Preserve all existing changes. Do not edit other files, commit, or push.
Report the actual file path changed.

This request authorizes a specific file write. If an approval appears, inspect the target path and operation before allowing it.

Check commands in the built-in terminal#

Click the terminal icon to expand the panel. Its + button creates a terminal tab. Closing a tab ends that terminal; collapsing the panel only hides its interface.

Terminals are reused by project. Returning to a project can reattach an existing terminal without resetting its directory or environment. Run pwd on macOS/Linux or Get-Location in PowerShell first. Once you are in the intended repository, run:

git status --short
git diff -- README.md
git diff --check -- README.md

These commands inspect file status, the unstaged README diff, and whitespace errors in that diff. They do not commit anything. Use managed services for a persistent preview instead of relying on an ordinary terminal tab for service management.

Verify the change in Review#

At the top-left of Review, switch between Changes and All files. Changes are grouped into unstaged, staged, and untracked files. Select a file to inspect the corresponding content.

The example should add only the requested section, preserving existing paragraphs and other files. If the file is already staged, inspect the staged section; the matching terminal command is git diff --cached -- README.md.

Review includes changes across the working tree, not just those from the current task. Separate pre-existing edits from new ones. Expand Review to use Previous change / Next change, or move to the previous or next file.

Add feedback on a specific code line

1. Hover beside a line in the modified side of the diff and click +.
2. Describe the problem or requested change and save the note. This entry is unavailable on deleted original lines.
3. Click the note count at the bottom to review notes across files. Click a note to return to its file and line.
4. With Send right away, no trip back to the composer off, choose Put in composer, add any instruction, and send. With it on, choose Send to agent to submit directly.

Direct sending includes any draft already in the active composer, so check that draft first. If no composer can receive the message, the notes remain queued for sending. Saving a note alone does not start a task. Review the resulting diff after the assistant responds.

The bottom-right commit control provides Commit and Commit and push. These are separate Git actions and are not needed for this example.

Troubleshoot files and commands#

Next steps#

Run a preview with the managed development service example. See permissions for action boundaries and projects and conversations for organization.