# Terminal, Files and Changes

> The panels for the chat's terminal, its files and the diffs the agent made.

Building software · Updated: 2026-11-16 · version 2.0.317 · https://nobreiniers.com/en/help/terminal-files-changes/

The right panel has three tools for coding: «Terminal», «Files» and «Changes».

## Open a panel

1. In the title bar, press «Terminal», «Files» or «Changes».
2. The panel opens on the right. ⌘\ opens or closes it.

## Terminal

Your own terminal in the chat's folder, like the Mac's Terminal app: type your commands there. It is yours alone: the agents do not use it or read what it prints. When you press «Update now», your terminals and what runs in them (a server, a build) keep running through the update, unless they hold files the update must replace; then they end, as when you quit. A link in the output opens with a click.

When a command asks for a password or a confirmation (ssh, sudo or git), the app shows you a card, «A command asks for your password», with «Send» and «Cancel». What you answer goes only to that program: no agent sees it.

## Files

«The chat’s files»: the files the chat worked with. Open them to read them.

### «To delete»: what the agents delete

An agent does not delete your files: it sets them aside. What it deletes with its commands (rm, rmdir, unlink, trash, or mv when it writes over another file) or with its file tools goes into a folder called «To delete» («Para borrar» if your app is in Spanish), at the top of the chat's folder. This holds at every permission level, «Full access» too.

- Each item keeps the place it had inside the folder: «To delete/src/old.swift». If that name is taken, a number is added.
- What it deletes outside the chat's folder goes into its working folder's «To delete», with its whole path.
- The agent tells you where each item went, and the app notes where it came from, which chat sent it and when.

### The bin in the title bar

At the top right, in the title bar, the first icon is a bin («To delete: what the agents deleted»). While items wait, it carries a number with how many. It shows what belongs to the chat on screen.

1. Press the bin. «To delete» opens: «What the agents deleted waits here, in case you want it back. Put back what you need; delete the rest.»
2. Each row says what it is, where it came from («From …») and who sent it and when. It has three buttons:
   - «Put it back where it was»: it goes back and the app says «… is back where it was.». If something with that name is there now, it does not write over it: it tells you and leaves it where it is.
   - «Show it in Finder».
   - «Delete it: it goes to the Trash»: confirm with «Delete», in the same place.
3. At the bottom, «Empty all: what is in your encrypted profile is deleted for good; the rest goes to the Trash». Press it and the app first lists every item that would go, measured right then, each with its name, where it is, its size and what happens to it, with the exact count and total: «Delete for good: … items, up to …, from your profile.» and «To the Trash: … items, …». What an earlier «Empty all» left unfinished in your profile's own trash is listed too, in a group of its own. Confirm with «Empty all». When something is deleted for good, a second question appears at the top of the window, with «Cancel» chosen: «This cannot be undone: … items in your profile are deleted for good, up to ….»; confirm with «Delete for good». A click or key that began before that question appeared does not count, and pressing Return or Space without moving to «Delete for good» does not confirm. Then it tells you what happened: «… items were deleted for good: up to … is free again inside your profile.», and when your Mac's disk gets that space back (the app compacts the profile when it opens). If anything changed between what you saw and the delete, nothing is deleted: it shows you the new list and you confirm again from the start. If it stops partway, it tells you where and why, with the system's code, and what is still in «To delete». Anything that leads outside your profile, like a link to another place, is left as it is, never deleted or followed, and the app tells you so. Outside your profile only the items listed go to the Trash; the «To delete» folder stays.

When there is nothing, it says «Nothing is waiting. When an agent deletes something, it comes here first.». What goes to the Mac's Trash you can still take back from there; what is deleted for good does not come back. In «Files», the «To delete» folder also shows whole.

Only you delete from there: no agent, nor your phone, nor a channel can delete from or empty «To delete»; only your click in the app's window. Agents cannot empty the Mac's Trash either.

What would delete for good without going through «To delete» is not done, at any level and with no card: the agent reads why and uses the way that keeps the files. For example rm named by its path (/bin/rm) or under sudo, find -delete, git clean, git rm, rsync's deletions, shred or emptying the Trash.

> **Note:** What a program deletes on its own (a Python or Node script, a build tool's cleanup, or git when it turns back files it tracks) does not go through «To delete». To turn back a whole turn, see [Go back and undo files](https://nobreiniers.com/en/help/go-back-and-undo/).

### Sort or move your files

Ask Breini or a Nobreinier to sort a folder or to move some files, and nothing moves before you see the plan. It can sort the files of a folder by kind (images, documents, spreadsheets and so on), by the month of the file's date or by extension, or move the items you name into the folders you name. It never overwrites and never deletes: a name already taken in the destination is left where it is and reported, and a file a browser is still downloading is left alone.

1. A card shows the plan: which folder, how many files will move and into which folders. If a name is taken, the card lists it under «Not moved, the name is already taken there». A run moves at most 500 items; when there are more, the plan says how many wait for the next run.
2. Approve it. In «Full access» the plan card is not shown and the move is made at once.
3. When it is done, a card says what was organised, how many files moved and into which folders, with «Undo all». One press on «Undo all» puts every file back where it was. A file that changed since, or whose old place is taken, stays as it is and the card lists it.

### The card before something goes to «To delete»

When an agent wants to delete files, the approval card says «To delete:» and what, and adds that nothing is erased: it goes into the «To delete» folder («Para borrar» if your app is in Spanish) at the top of its project, and you can take it back from there. Your yes is on that card. The folder and the bin are described above.

### How your agent reads, searches and edits your files

- **Searching:** if a search pattern never ends in a file, stopping the agent stops it inside that file, and after 5 seconds that file is left. The agent is told which files were left, so it never takes the results as complete.
- **Very long lines:** a line over 2,000 characters is shown cut, with where to go on; the agent reads the rest piece by piece, to the end.
- **Saved with no change:** before it edits a file, the agent checks that the file is still the one it read. If the file was saved again with the same content (an editor saved it, a tool touched it), the edit goes ahead; if the content changed, the agent reads it again first.

## Files your agent made

When a turn makes documents (a PDF, a spreadsheet, a deck or another file outside the project's code) and the reply does not name them, a card under the reply lists them. Each one has «Open» and «Show in Finder». The card is there again when you open the chat later; in a long chat that was summarized, the older cards no longer show. Files of the project's own code show in «Changes» instead.

## Changes
A turn's card lists the files that turn changed; with two or more, «Save all as one zip» saves them as they are now in one zip (a file that is gone is left out and named).


1. «The chat’s changes» lists each changed file and its «File changes».
2. In «Which changes to see», choose «Uncommitted», «Whole branch», «Branch commits» or «Last turn». «Whole branch» and «Branch commits» start from the place where the branch began: the app finds it by itself (it shows «Since main (automatic)», for example) and you can pick another one with «Compare with», which lists your branches and commits. «Last turn» shows what the agent changed in its latest answer, even if you have no commits.
3. Press «Review» and the agent reviews these changes like a demanding reviewer, without touching anything. For a deep review, see [Code review](https://nobreiniers.com/en/help/code-review/).
4. To put a file back, see [Go back and undo files](https://nobreiniers.com/en/help/go-back-and-undo/).

The list comes sorted by kind of file: «Code», «Tests», «Configuration», «Documents», «Generated», «Assets» and «Other». So you see what matters first.

When a block of code only changed place, the app marks it instead of showing it as deleted and added: «… lines moved from …» or «… lines moved to …».

### Keep track of what you have read

- Press «Mark as reviewed» on a file when you have read its change. The list dims the files you read and counts them («3 of 12 reviewed»). If the file changes again, the mark goes away by itself, so you never trust a change you have not seen.
- Press «Side by side» to see each change in two columns, what was removed on the left and what was added on the right. The app remembers your choice. In a narrow panel it stays in one column.
- A changed picture shows «Before» and «After» next to each other; a new or deleted one shows «New picture» or «Deleted picture».

### Pictures, sounds and videos

A picture, a sound or a video in the panel opens in a viewer. Files of any size open at once: the app reads them from your disk as you look, it does not load them whole. On a picture, pinch or press plus and minus to «Zoom in» and «Zoom out», drag or use the arrow keys to move it, press 0 for «Fit to the view» and 1 for «Actual size». «Large view» gives a video the whole panel, and «Back to the changes» returns. If a file cannot play here, the viewer says so and you can show it in Finder.

> **Note:** The actions of «Files» and «Changes» are icon buttons. Hover over one to read what it does.

## Code to read: other projects’ code

When an agent has to know how a library really works, it is better to read the library’s own code than to guess. In «Settings» › «Storage», the section «Code to read» keeps other projects’ code on your Mac, under a name:

1. Paste the address of a public code repository (for example the one of a library you use) and press «Keep it here».
2. The copy refreshes itself every day. Press «Check for news now» to refresh it at once.
3. Breini and the Nobreiniers read it when they need it. It is only read: nothing in it is ever run.
4. To remove one, press «Move to the Trash».

Next to each one you see where it comes from, how much room it takes and when it was last checked. Your own files and settings are never part of these copies.

## Code helpers for your languages

For an agent to find exactly where things are defined and to catch mistakes while it writes, it uses a small helper for each language. If your project needs one that is missing, the agent asks once with a card: «… wants to install a helper for … code, with …». Press «Always allow» and it installs in the background with a program you already have on your Mac (you can keep working), and the app remembers your answer for that language; press «Not now» and nothing is installed, and it is not offered again unless you ask. When it is ready the chat tells you: «the code helper is installed and ready». The app keeps a list of what it installed, and the agent can remove it later behind its own card.

## Tidy the code when the agent finishes

In a project's settings, the switch «Tidy code with the project's formatter when an agent finishes» runs the formatter the project already has, once per answer, on the files the agent changed. It never installs a formatter of its own. You can also ask Breini in your own words.

## A new working copy gets your setup

When an agent works in its own working copy (a new git worktree), the app runs your own «Setup» hooks right after it is made, so the copy starts with what it needs. If one of them fails, the copy is still made and you are told which preparation failed. See [Hooks](https://nobreiniers.com/en/help/hooks/).

## Command

When the agent starts a long command, the «Command» panel shows its output as it runs and how it ended: «Running», «Finished», «Failed» or «Stopped». It opens by itself; see [One step ahead](https://nobreiniers.com/en/help/one-step-ahead/).

When the agent leaves a long command running in the background and waits for it, the wait ends with one clear answer: it finished, it is waiting for you to type something, it has gone quiet, or it is still running. The agent stops asking again and again: when a command is waiting for an answer, the app tells it once. A command that only prints for a long time, such as a server, does not wake the agent by itself.
