box

Use the Box CLI login flow: run `box login --default-box-app` for a same-computer browser, or `box login --default-box-app --code` when the assistant runs on a remote or headless host. After authorization, verify the connected identity with `box users:get me`.

Use Box AI extraction commands: `ai:extract-structured` for known fields, `ai:extract` for exploratory fields, then persist results to the built-in `global.properties` metadata instance or a JSON sidecar file. Always read the metadata back and compare it with the intended values.

Yes, use the remote OAuth path with `box login --code`, which displays a URL to authorize in a browser on another computer and returns a code and state to the waiting CLI. Do not use the local callback flow when the browser is on a different host.

Box AI `ai:ask` handles Q&A over up to 25 selected files, while Box Hubs support recurring Q&A over a curated, indexed knowledge base of many more files. Hubs must have AI enabled before creation so their content gets indexed.

A file accessible via `files:get` can still fail through Box AI if the feature is disabled, the account lacks AI units, or the OAuth app is missing the AI scope. Verify the actor and file permissions first, then check Box AI enablement before retrying.

No, Box does not permit creating global templates, and enterprise template creation requires a Box Admin or authorized Co-Admin. Store flat extraction results in the schema-free `global.properties` instance or upload a JSON sidecar instead.