inkbox-ai/hermes-agent-plugin/inkbox-troubleshooting

Inkbox troubleshooting

Use this skill when an Inkbox tool fails, the user asks why Inkbox is not working, or a channel readiness problem blocks email, SMS, calls, contacts, notes, or vault access.

Common errors

Vault unlock pattern

Vault tools respect native tool policy. The plugin never persists the vault key. Metadata listing needs no plugin key; each decryption/TOTP operation reads INKBOX_HERMES_VAULT_KEY and uses fresh SDK reads. Migrate SDK-global Vault auto-unlock settings out of this gateway process: they can affect unrelated clients before the plugin handles a tool.

If vault access fails, do not ask for the vault key in chat. Tell the operator which env var needs to be set in this plugin's gateway process.

Identity checks

Use inkbox_whoami when you need to confirm the active Inkbox identity, mailbox, phone number, SMS status, auth subtype, sending domain, or call routing state.

If inkbox_whoami fails, surface the exact error and suggest this plugin's Inkbox doctor command (<host> inkbox doctor) for a local diagnostic pass.

When you need more

If a config field, error message, or setup flow here does not match what the user is seeing, go to the source:

• https://inkbox.ai/llms.txt — LLM-friendly index of Inkbox docs.
• https://inkbox.ai/docs/all.md — the full Inkbox documentation concatenated as one markdown file.

Optional channels

Native iMessage replies require INKBOX_IMESSAGE_THREADED_REPLIES=true and SDK 0.7.13+. Slack requires INKBOX_SLACK_ENABLED=true; Slack Companion requires SDK 0.7.14+. A paused Slack subscription needs operator attention, not a duplicate subscription. Run hermes inkbox doctor for read-only checks. Never delete native/Companion checkpoints or resend an unknown-outcome delivery to force recovery.