본문으로 건너뛰기

Understand agent permissions

Desktop chat runs on macOS and Linux. On Linux, the agent's sandbox needs bubblewrap at /usr/bin/bwrap with unprivileged user namespaces. Windows Desktop has no agent chat.

What the agent can do in Desktop​

Desktop chat in a project uses the Default access, shown in the composer. The agent reads and edits files in the project and runs commands there in a sandbox without asking. For example, ask “Run the tests and fix what fails.”

  • Commands start from your login shell's environment, so your usual tools work.
  • Commands can read elsewhere on your computer, except Grida's own data and saved credentials. They can write only in the project and the system's temporary folder, and they cannot reach the internet.
  • Existing version-control and agent settings folders, such as .git, stay read-only. The agent can start a new repository but cannot commit to an existing one, so run commits yourself.
  • With the Plan badge on, the agent only reads and asks questions; it does not run commands or change files.
  • The agent's own settings file is the exception to working without asking: it can read the file, but every change to it asks for your approval, and commands cannot reach it. Change agent settings

Choose Full access​

In a project's chat composer, open Default and choose Full access. Confirm the in-app dialog for that chat. You can make the choice before sending its first message; opening the chat does not start the agent.

Full access lets the agent run commands without the filesystem or network sandbox. It can fetch resources, install packages, change existing Git metadata, and reach files and local services available to your OS user. This includes readable credentials and Grida's own state. It does not grant administrator privileges, supply missing service credentials or automatically configure a program's proxy support.

The choice belongs to that chat and survives reopening. Other chats keep their own choice, and new chats begin with Default. Change access while the chat is idle, its queue is empty and it has no running command processes. Use the Processes controls to stop those processes before changing access. Accepted work and subagents keep the permissions captured for their assignment.

Choose Default again to restore restricted access for subsequent work. Plan continues to withhold commands and file changes in either mode. Process output, cancellation and cleanup reporting remain available in Full access, but an unconfined program can escape normal process-group cleanup; Grida does not promise isolation from hostile same-user code.

Full access needs a compatible native Desktop build. Older builds keep Default and do not offer the choice. Before opening a project, the welcome composer cannot grant access to a chat. Automatic approval review, sometimes called Approve for me, is not offered by Desktop.

What the agent cannot reach​

With Default access, the agent's file tools work only inside the project, and its commands cannot reach the internet. Desktop does not ask to extend this for one action. To use a file from elsewhere, copy it into the project or attach it to your message. Attach an image or a file

A question the agent asks about what you want is separate from access: answer it in its card, and it grants nothing.

Run with your own folder rules​

When you run the agent from a source build on macOS or Linux, a permission profile chooses the project folder, adds folders the agent must ask before reading, and allows commands. When the agent asks, the run waits with a request that shows the action, folder and relative path; the client answers with Allow once or Decline, and each approval covers that one action. If no one is there to answer, the request waits in the chat until a client answers it. Work with selected folders · Run a confined command

A profile can also let the model answer one specific file-read request per turn. If the model cannot decide or its review is interrupted, the request waits for you. Pause and Stop still apply during the review. Configure automatic read review

A trusted native launcher can separately opt into Full access. That authority comes from the launcher, not a workspace file or model request. See the native permission profile for its opt-in fields and the private per-chat selection contract.