Back to Hermes Agent

Troubleshooting

skills/productivity/box/references/troubleshooting.md

2026.8.162.9 KB
Original Source

Troubleshooting

Capture the actor, object ID and type, exact command, status code, and safe error body before changing approach.

First checks

bash
box users:get me --json --fields id,name,login
box configure:environments:list
box files:get <FILE_ID> --json --fields id,name,parent
box folders:get <FOLDER_ID> --json --fields id,name,parent
box hubs --scope all --max-items 1000 --json
box hubs:get <HUB_ID> --json

Confirm the current actor, resource type, ID, resource-specific collaboration, app scopes, and selected environment. Do not use folder 0 as an access test: it cannot discover a Hub and may not list every shared file or folder.

Common failures

SignalLikely causeNext action
local OAuth reports EADDRINUSE, opens an unusable result, or never returns to the CLIoccupied or mismatched loopback callback portstop the waiting login process; for the official app, retry 3001, 4000, 5000, then 8080; for a custom app, register the exact new callback URI before retrying
remote OAuth browser ends on an unreachable localhost pageexpected --code redirect or wrong topologyif Hermes is remote, return the URL's code and state to the waiting CLI; if Hermes and the browser are on the same host, stop and restart without --code
401 or 403expired auth, missing scope, insufficient roleverify identity, reauthorize the app, and check folder role
shared file/folder absent from root or 404wrong actor, an access-only/shared item, or missing file/folder collaborationverify users:get me, then fetch the known file/folder ID directly; only change collaboration after confirming the target and actor
Hub absent from root or 404root listing cannot discover Hubs, wrong actor, or missing Hub collaborationrun box hubs --scope all and box hubs:get <HUB_ID>; verify Hub collaboration separately from underlying-file access
409duplicate name, existing collaboration, metadata conflictlist the parent/template and reuse or rename deliberately
429rate limithonor Retry-After, retry the same request, and reduce batch rate
Box AI access errorfeature disabled, plan/unit restriction, unsupported contentexplain the limitation and offer metadata/search, a sample, units, or approved fallback

If two Hermes profiles or sessions appear to change each other's Box actor, remember that a private npm installation does not isolate Box CLI environments for the same OS user. List environments, verify the current actor, and ask before switching. On Linux, if the CLI reports plaintext credential fallback, warn about ~/.box without reading or printing its credential files and recommend configuring Secret Service/libsecret or an isolated runtime user.

Do not diagnose missing content until identity and access are verified. Do not silently change actors, broaden sharing, or download confidential source files as a workaround.