box

Run `box login --default-box-app --name <env>` for a same-computer browser flow, or add `--code` when Hermes runs on a remote or headless host. After the browser authorization completes, verify the actor with `box users:get me --json`.

Use `box ai:extract-structured` with inline `--fields` for known schemas or `box ai:extract` for exploratory fields. Persist flat results to the built-in `global.properties` metadata instance or upload a JSON sidecar for nested data, then read back and compare every field.

Yes, use a Box Hub. Discover an existing accessible Hub with `box hubs --scope all`, then send one `single_item_qa` request with the Hub as the item via `box request /ai/ask`. Create or populate a Hub only after explicit user approval.

A file accessible via `files:get` can still fail through Box AI when the feature is disabled, the account lacks AI units, or a custom Platform App misses the AI scope. Verify the actor and file permissions first, then check Box AI enablement before retrying.

The `global.properties` instance is schema-free and untyped, so values are stored as strings and cannot be queried with the Metadata Query API. For typed reusable metadata, an existing enterprise template is required; only a Box Admin can create new templates.

Use an official Box SDK when building a shipped application, integration, or webhook handler that needs OAuth token management, retries, and idempotency in code. For one-off agent tasks, the Box CLI with the `box request` REST fallback is sufficient.