Box Cloud Filesystem

Overview

Operate Box through numeric file and folder IDs, narrow sharing defaults, and verified receipts. The plugin's Write/Edit hook only queues local workspace changes for review and never uploads automatically; see the reviewed sync pattern for the complete flow.

Prerequisites

box version
box users:get me --json

• Install the current supported Box CLI 4.x through an operator-approved Node package workflow; do not install packages automatically.
• Use box login for interactive OAuth. JWT and CCG require a Box Platform App, appropriate scopes, secure configuration, and enterprise admin authorization.
• Never request or pass access tokens through chat or the CLI --token flag.
• The bundled workspace scripts require Bash and jq.

Workflow

1. Classify the request as discover, read, create, update, expose, synchronize, or destructive.
2. Verify the active Box identity with box users:get me --json and report the account or enterprise without exposing credentials.
3. Discover the target by listing or searching. Use Read, Glob, and Grep only for the local files the user placed in scope.
4. Resolve every remote target to a numeric Box ID. Names are not unique.
5. Preview the operation:

• uploads: local path, size, parent folder ID, and collision result;
• updates: file ID, local path, and remote content_modified_at;
• sharing: target ID, access level, download/edit flags, and expiry;
• deletion or bulk moves: every target and recoverability.

1. Execute only the operation the user authorized. Ask before public/open links, deletes, bulk reorganizations, overwriting remote changes, or widening app access. Use Write or Edit only for requested local artifacts.
2. Re-read the affected Box item and return the receipt contract below.

Trust zones