Select a coding workspace

Coding agents operate inside a workspace selected by the owner. The selected folder becomes the read-write boundary for current and future coding sessions.

Select the folder

Open the workspace control in the conversation context bar. Browse from the server-provided root, choose a directory, or enter a folder path within that root. Enable Create the folder if it does not exist only when a new project directory is intended, then select Use this folder.

The picker cannot move above its configured root. A direct path is still validated by the backend; entering .. does not grant broader access.

What the coding agent can do

An allowed coding profile can list, search, read, create, edit, test, lint, and apply patches inside the selected workspace. Additional commands and deployment actions depend on its tool profile and approval policy.

The workspace is mounted into a persistent coding container. Container resource, network, and idle limits are controlled by the runtime.

Repository credentials

Do not put GitHub or other publication tokens in the workspace or container environment. Use a marketplace connector to publish an immutable reviewed change bundle. This keeps the repository credential in the connector secret store.

See GitHub for governed pull-request publication.

Switch projects safely

Changing the selected workspace updates current and future coding sessions. Before switching:

1. stop or finish tasks still writing to the previous folder;
2. inspect uncommitted work;
3. record the intended repository and branch;
4. select the new folder;
5. ask the coding agent to report its working directory before edits.

Network boundary

A sandbox with no network can still edit and test local code. Bridge networking permits internet and may also reach host or LAN services. Keep network-capable command execution under approval and avoid running untrusted project scripts with broad network access.