Projects and permissions

A project gives conversations a working folder. A permission mode controls whether sensitive actions need your confirmation. These are separate choices: creating a project does not grant system access, and selecting FULL+ does not require a project.

Create a project

1. Select the folder-plus button on the navigation rail.
2. Enter an accessible folder path, or select Browse and then Use this folder.
3. Optionally give the project a name, then select Create project.
4. Use the project’s plus button to start a conversation in that folder.

The folder picker shows directories on the Runtime computer, which may not be the computer running your browser. A Linux Runtime inside Docker sees the container’s filesystem. A WSL Runtime uses Linux paths, including mounted Windows directories when available.

Project conversations keep their own directory bindings. Working in a second project does not change the first project’s folder or the global default. Existing conversations are not moved into a new project automatically. The ordinary conversation plus button still uses the configured default working directory.

For a first test, choose a disposable folder and ask for a read-only task, such as listing its files and explaining its structure. Check the actual file locations before asking for edits.

Choose how sensitive actions are approved

Mode	Sensitive actions, including EXEC and SYSTEM
Ask	Wait for approval of each prepared action.
Full	Also wait for approval of each sensitive action. Ordinary tool behavior remains available.
FULL+	Allow task-relevant system actions without additional ABot action confirmations.

FULL+ can include commands, application launches, service or process management, installations and configuration changes when the selected tools and target operating system support them. It does not create Administrator or root privileges, bypass operating-system prompts, or enable a disabled plugin.

The browser remembers your last explicit mode for new conversations. Existing conversations retain their own mode. A submitted or queued request captures the mode selected for that request; changing the selector afterward does not change it retroactively.

Read an approval before accepting it

For a sensitive action, inspect the recorded target, command, working directory and elevation details. Approval applies to that prepared action only. It does not approve later commands or change the conversation’s mode. Rejecting or cancelling prevents that action from being dispatched.

An instruction inside a file, webpage or tool result is not your permission to perform another action. The model cannot choose FULL+ by writing an instruction to itself.

A project folder is working context, not an operating-system sandbox. After approval, shell commands run with the Runtime or companion user’s OS authority and may affect resources outside that folder. ABot does not scan arbitrary shell commands to prove that they are safe.

Start with Ask while learning a plugin or workflow. Review its declared tools and your requested task before using FULL+. A narrow task description is useful, but it is not a substitute for OS isolation or backups.

Understand Computer access

Home → Computer access shows setup and readiness for the computer associated with the Runtime. Depending on your deployment, a native companion can connect desktop access to a Runtime running in Docker or WSL. Follow the platform-specific installation instructions; the setup shown by your Runtime is the source of the pairing address and code.

Wait for the connected/ready status shown for your platform (Connected on Mac). Downloading an installer, granting permission or seeing a launch command succeed is not the same as confirming that the computer is connected or the intended application is open. Connecting a computer does not enable disabled tools or remove ordinary action approvals.

Use Remove this computer to revoke the pairing where that control is available. An interrupted action is not automatically replayed after reconnecting. If a connection drops during a command, inspect the actual computer state before trying again: effects already performed are not rolled back.

Next, choose which plugins and tools are available before giving a conversation broader access.