> Source: Onevium official documentation
> Article: Work with files, terminal, and Review
> Original URL: https://onevium.com/docs/files-terminal-review
> Language: English
> Updated: 2026-09-09
> Applies to: 1.1.22
> Feature status: Released

---

# Work with files, terminal, and Review

Provide precise file context, inspect command results, and review a small change in the workspace.

## 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.

| 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.

## 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.

## 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.

```text
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:

```bash
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](https://onevium.com/docs/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 the new ones. **Commit** and **Commit and push** in the top toolbar are separate actions and are not needed for this example.

## 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                        |

## Next steps

Run a preview with the [managed development service example](https://onevium.com/docs/managed-services). See [permissions](https://onevium.com/docs/permissions) for action boundaries and [projects and conversations](https://onevium.com/docs/projects-and-sessions) for organization.