Work with files, terminal, and Review
Browse project files, run terminal commands, review code changes, and send line-specific feedback to the AI in Onevium.
Your workspaceFind 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.
| Control | What it opens |
|---|---|
| Folder icon: Browse all files | The Review workspace's All files view; select a file to read its content |
Green +N and red -N: Show changes | Changes in the current Git project; this is not a commit button |
| Terminal icon | The built-in terminal panel below the conversation input |
File upload action under the composer's + menu | File attachments for the message you are preparing |
Files group in the composer's @ list | Search and reference paths within the project |
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#
- Open
README.mdthrough Browse all files and confirm it belongs to the intended project. - Return to the conversation, choose
README.mdfrom the@file list, and send the request below. - Wait for the edit result, then click the top
+N/-Ncounter 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#
First identify the source of the changes:
| Entry | Scope |
|---|---|
| Conversation header +N/-N → Working changes | The repository's unstaged, staged, and untracked files, including edits left by other tasks |
| A reply's file-change card → Review changes | Recorded file snapshots from that request; the source menu can switch to Current Git changes or another recorded request |
| Bottom-left Compare branches in Review | Differences and a merge preview between a source and target branch |
The example should add only the agreed section. Inspect staged edits in the staged group; use git diff --cached -- README.md in the terminal. A request's record may omit shell commands, plugins, or external edits. Check current Git status when verifying the whole project.
Navigate several repositories and files
When a project contains multiple repositories, check the repository selector first. All repositories provides an overview; choose one repository before committing or comparing branches.
Switch between Changes and All files in the left rail. The bottom navigation steps through changes within a file or moves between files, including in All repositories. Toggle unified and split diffs when a side-by-side comparison is easier to read.
Add feedback on a specific code line
- In the current Git diff, hover beside a line on the modified side and click +.
- Write and save a specific request, such as “Keep the existing message when this value is empty.” Deleted original lines do not support this entry.
- The note appears directly in the active composer. Click it to return to its file and line, or use its remove button to delete it.
- Check the draft and all notes, then send. Saving a note does not start an edit; inspect the resulting diff afterward.
Undo only the recorded file changes from one request
Click Undo recorded changes on a reply's file-change card, inspect the restore preview, then choose Restore recorded changes. This keeps the conversation and historical change record while restoring files that can be safely restored. If a later task changed those files or a conflict appears, resolve the notice first.
To remove subsequent conversation history as well, use message rewind. Undoing recorded files and rewinding a conversation have different scopes.
Compare Git branches before merging#
- Select a repository in Review, then click Compare branches at the bottom-left.
- Choose the Source branch to bring in and the Target branch to receive it. Click Preview merge.
- Check incoming commits, file differences, and conflicts. For AI assistance, choose Prepare AI handoff in the more-actions menu, review the request, and click Add to chat draft. Send it when ready.
- If you intend to merge, commit or stash working changes, select a local target branch, then click Merge locally and confirm.
Previews use branch snapshots already on your machine; they do not fetch remote updates automatically. Remote targets are review-only. A local merge may switch branches and create a merge commit, but does not push. Commit and Commit and push under Working changes are separate Git actions; this example only requires inspecting changes.
Troubleshoot files and commands#
| Symptom | What to do |
|---|---|
| Review shows no change | Confirm the file was saved and the path is correct; inspect staged and untracked files too |
| The file tree and conversation seem to use different projects | Check the active conversation and working directory before reopening the file |
| Terminal output appears to belong to an earlier task | Check its directory and running command. Use + for a fresh tab when appropriate rather than relying on an old log |
| The diff includes someone else's changes | Preserve them and inspect within your task's scope. Do not revert everything |
| A check fails | Record the command and error. A passing whitespace check is not a passing project test suite |
For manual Markdown, text, and CSV edits, saving and conflicts, plus read-only PDF/Office previews, see File preview and editing.
Next steps#
Run a preview with the managed development service example. See permissions for action boundaries and projects and conversations for organization.