Documentation

Security model

The practical security boundaries around workspace access, approvals, shell commands, secrets, remote endpoints and browser verification.

File scope

Project workspace is the normal scope. File scope narrows operations to a selected file. Full Machine requires explicit confirmation and still uses bounded outside-workspace reads rather than unrestricted file editing.

Approvals

Editing and command execution can require approval. Session grants are not permanent and can end on chat, scope, approval-mode or reload changes.

Commands

Approved commands run as your OS user. TuxNest policy can block or require confirmation for sensitive categories, but it is not an operating-system sandbox or firewall.

Secrets

Do not place API keys or SSH secrets in prompts, repositories or public logs. Use the extension's intended secret storage and endpoint configuration paths.

Browser boundaries

Local browser inspection is constrained to loopback URLs and rejects credential-bearing targets and unsafe redirects. That verification environment is intentionally different from unrestricted web browsing.