Skip to content

Load extra tools from your hat

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.5.0 on 2026-11-08.

Can you load the evidence tools for this chat?

Ask for the tools a job needs, then read which bundles your hat can load and what is in each.

What you get: one conversation carrying the extra tools a job needs, such as receipts and audit evidence, without switching hats. You need: a signed-in profile. About 3 minutes.

Ask in plain words:

quox · talking to Quox

I'm about to dig into receipts and audit evidence in this chat. Load the evidence tools from my hat so you have them ready.

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 8ms

◐ HAT │ catalogue ✔ HAT │ catalogue │ 4 other hats, 5 hat names, 2 privileged hats · 4.0s

⛓ AEE │ envelope opened · ops.tool · hat_catalogue ok

◐ HAT │ load bundle ✔ HAT │ load bundle │ ok: true, 1 loaded bundles, already loaded: false · 521ms

⛓ AEE │ envelope opened · ops.tool · hat_load_bundle ok

⛓ AEE │ envelope opened · stream_success

I've loaded the evidence bundle, "Governance & evidence (read)", on your Default hat.
Its tools become available from your next message, so they aren't usable yet.

The bundle has 11 read-only tools:

• Governance and compliance: governance, compliance and QuoxLens reads.
• Receipts: WARD receipt verification and WARD status.
• Audit trail: envelope search, envelope chains, and captured evidence artifacts.
• Security and tool activity: the security audit log, tool outcomes, and delegation
  routing advice.

Send your first question when you're ready. If you have an envelope id, objective id or
time range, include it and I can start straight away.

22.7s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.5.0, 8 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 8 Nov 2026 · test report mw7ugl

Quox read the hat catalogue, then loaded the evidence bundle from the hat it was wearing. It said plainly that the new tools arrive with your next message, not part way through this one, and listed what the bundle covers. Every tool in it only reads.

bundles
quox hat show defaultDefault (default)  01K6GM…General conversation with discovery and delegation; reaches every capability without carrying every tool. Revision:     3 (current)Mode:         permissiveTransitions:  confirm=none privileged=no Bundles (11, loaded per conversation with hat_load_bundle):notify: send_notificationawareness: lucid_situation, lucid_item, org_directory, agent_directory, identity_status, install_status, license_status, plugin_list, spend_status, reach_agent, standing_grants_list, llm_status, llm_policy, backup_overview, live_sessionsevidence: governance_read, compliance_read, quoxlens_read, noc_tool_outcomes, ward_verify, ward_status, delegation_router_advise, query_envelopes, get_envelope_chain, list_evidence, security_auditinfra: docker_status, proxmox_cluster_status, tls_cert_info, doneengine_readiness, core_health
From a real run on a test organisation. Trimmed to the bundles.
  • Explicit tools (above the bundles in the full output) ride along on every turn under this hat.
  • Bundles are loaded only when a conversation asks for them, and only for that conversation. The evidence line is the eleven tools Quox loaded above.

There is no shell command for this: a bundle belongs to one conversation, so you ask for it in that conversation, in plain words, as above. Name the job (“receipts and audit evidence”) or the bundle (“the evidence bundle”).

Loading a bundle changed which tools this one conversation carries, nothing else. The hat itself did not change and no other conversation saw the tools. A hat only says which tools a conversation carries; what Quox may actually do with them still comes from your own grant, so loading a bundle never widens your permissions.

quox hat show <hat> lists every bundle a hat can load. If a tool you need is in none of them, switching hats is the next step: see Change the hat for one conversation.

Nothing to undo. The bundle stays with that conversation only; a new conversation starts with the hat’s explicit tools again.