Language and sandbox

What it's for

This page gathers the settings you rarely change but need to know where to find. Tools → Language… chooses, separately, the language of the screen and the language of the text PrumoGrid writes for the agents. Tools → Advanced options… holds the rest: terminals, agent profiles, end-of-turn notification, writing in projects, layouts, limits, extensions, sandbox and updates. Every choice is saved in the app profile.

When to use it and when not to

Change the agent language when the repository is shared with a team that reads another language and you want the block written to CLAUDE.md or AGENTS.md to come out in that language. Change the screen language when you are recording a tutorial or working with someone who reads English.

Turn on the sandbox if your company's policy requires the interface to run isolated and you have already confirmed that the machine's antivirus or EDR accepts it. Don't turn it on expecting it to protect what runs in the terminals: it does not isolate the commands run in them.

Language

In Tools → Language… there are two choices, and they don't have to match.

What you wrote is never translated. An instruction typed in Portuguese reaches the agent in Portuguese, whatever the choice. The setting applies only to the text the product generates around it.

In Automatic, PrumoGrid chooses based on the language it detects in what you type, and the screen shows the current choice, such as right now: Português do Brasil.

Change the screen language

1. Open Tools → Language….
2. In What you read, choose English.
3. Almost everything changes right away: menus, Help, the bars, the project list and the Central. The pane and the dialog that were open stay in the previous language.
4. To fix those two, click Reload the window. No session is lost, because the terminals live in the terminal service, outside the window.

Write the guidance in English in a team repository

The example: portal-web is shared with a team that reads English, and its AGENTS.md goes into Git.

1. Open Tools → Language….
2. In What the agent reads, choose English.
3. Create the next portal-web stage as usual. You can keep writing the instruction in Portuguese.
4. After the stage, run git diff AGENTS.md and check that the block generated by PrumoGrid, between the markers, came out in English. The text of your instruction and the rest of the file do not change.

To add another interface language, put a <tag>.json file in %APPDATA%\TerminalGrid\idiomas. No new version of the app is needed.

Enlarge screenshot ↗

Advanced options

Tools → Advanced options… opens on the first section, Terminals, with the side menu in three groups:

The Tools menu items with matching names open the matching section directly: Agent profiles…, End-of-turn notification…, Project file writing…, Saved layouts…, Memory and CPU limits… and Extensions…. It is the same screen, not a second copy of the setting. Terminals, Sandbox and Updates you open from Advanced options….

Enlarge screenshot ↗

Scrollback lines per terminal

In the Terminals section, Scrollback lines per terminal sets how many lines each terminal keeps for you to scroll back up: from 1,000 to 50,000, default 5,000. The change applies to terminals opened after it; conversations that are already open are preserved. This is the terminal's scrollback. The agent's conversation stays in the CLI itself.

Increase it if you often read long output, such as an entire test suite. Remember that scrollback is not a backup: to keep an output, save it to a file.

Sandbox

In the Sandbox section, the Enable Chromium sandbox checkbox turns on interface isolation. It is off by default.

1. Open Tools → Advanced options… and choose Sandbox.
2. Read This launch and Next launch. The first says how the current window is running; the second, how it will open next time.
3. Check Enable Chromium sandbox. The choice is saved right away.
4. Close and open the app. Reloading just the window does not apply the change.
5. Go back to the section and check that This launch changed.

The sandbox limits the interface's access to the computer's resources. Terminal commands and agents keep running with your account's rights. Corporate policies, antivirus or EDR may be incompatible with it and prevent the interface from opening; that is why it is off by default. If the attempt fails, the app opens again without the sandbox and reports the failure. The option does not create exceptions in Windows or change antivirus rules.

An older profile may show the Automatic preference. It is still supported, and the screen explains what it does.

Enlarge screenshot ↗

Updates

In the Updates section, Check now looks for a new version. When there is one:

1. Read What changed and, if you want, Full release notes.
2. If This version changes the license. appears, open Read the full license and check I have read and accept the license for this version. Without accepting it, the update does not proceed.
3. Click Download update. When it finishes, the screen shows the size and signature verified. The installer is used only if the signature checks out.
4. Read whether the update replaces the terminal service. This update does not replace the service means terminals and sessions carry on; This update replaces the service warns that open sessions will end on restart.
5. Choose Reopen now or On close.

What happens to sessions during an update is covered in Resume after restart.

Tips

• If the screen ended up half in one language and half in the other, use Reload the window in Language…. The terminals carry on.
• For shared repositories, agree on the agent language with the team before committing CLAUDE.md or AGENTS.md, so you don't get translation-only diffs.
• If the interface doesn't open after you turn on the sandbox, the app should come back without it and tell you. Uncheck the option and talk to whoever handles the machine's security.

Known limitations

• The agent language does not translate what you typed or the agent's answer.
• A change to scrollback lines does not apply to terminals already open.
• The sandbox applies to the interface, not to the terminals, and only on the next app launch.
• Updating from inside the app depends on a build with the publishing key configured; without it, the section says updates are unavailable.