Change the hat for one conversation
Can this chat wear the Marketing hat?
Ask for the hat you need, then switch a conversation yourself and see which hats wait for your yes.
What you get: one conversation working under the hat that fits the job, with every switch recorded. You need: a signed-in profile. About 3 minutes.
Ask Quox
Section titled “Ask Quox”Ask in plain words:
I'm going to draft a few social posts in this chat. Can you switch this conversation over to the Marketing hat?
▤ 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 · 1.4s
⛓ AEE │ envelope opened · ops.tool · hat_catalogue ok
◐ HAT │ propose switch ✔ HAT │ propose switch │ no switch needed: true · 1.5s
⛓ AEE │ envelope opened · ops.tool · hat_propose_switch ok
⛓ AEE │ envelope opened · stream_success
Nothing needed switching, so I made no formal switch. Marketing is a non-privileged hat, and because you asked for it directly, its tools work on your request without a hat change or an approval. For your drafts, that covers: • X posts and threads: I can draft these, and each one files an approval card for you before anything is published. • Images: I can generate images and capture screenshots to go with the posts. • Research: I can check the posting budget, pull SEO data, and search the brain and past conversations for context. Send over the first post whenever you're ready, with the topic, tone, and any link or image you want attached.
17.0s · 2 tools · 0 approvals
quox.✔ Machine verified against the CLI on 5 Nov 2026 · test report mw404f
Quox read the hat catalogue, then asked to switch. Marketing is not privileged, and you had asked for its work directly, so no switch and no approval were needed: Quox said so rather than claiming it had changed hats, and listed what the Marketing tools cover. A privileged hat, such as DevOps, is different: Quox proposes the switch and waits for your yes.
Do it yourself
Section titled “Do it yourself”1. See what the hat carries
Section titled “1. See what the hat carries”quox hat show marketingMarketing (marketing) 01K5QA…Research, content preparation and governed channel publishing; drafting and publishing stay distinct. Revision: 5 (current)Status: previewTemplate: v36Mode: permissiveEnforcement: preview (org)Transitions: confirm=none privileged=noAgents: orchestrator=quox specialists=linkedin, youtube, xtwitter, facebook, instagram, tiktok Explicit tools (6):hat_catalogue, hat_load_bundle, hat_propose_switch, delegate_to_agent, memory_search, memory_saveBundles (3, loaded per conversation with hat_load_bundle):draft: quoxbrain_search, gemini_image_generate, screencap_capture, quoxchat_search_knowledge, recallops: screencap_status, screencap_list_pages, screencap_compare, screencap_validate, quoxchat_read, quoxseo_summary, quoxseo_issues, quoxseo_changes, quoxseo_urlspublish: x_post, x_thread, x_budget_status, send_notification, x_delete, x_like, x_repost, screencap_uploadprivileged=no means Quox can wear this hat without asking you first. Drafting and publishing sit in separate bundles, so a conversation can draft posts without carrying the tools that publish them.
2. Switch a conversation
Section titled “2. Switch a conversation”In a chat, type /hat marketing. You typed it, so there is no approval card, and your next message runs on the new hat. From the shell, name the conversation; quox conversation list shows the IDs.
quox hat use marketing --conversation QXC_3681e2b9-e4c3-41cb-a0a9-9f519ef50478Ⓠ QUOX │ conversation QXC_3681e2b9-e4c3-41cb-a0a9-9f519ef50478 now wears marketing │ rev 5 · seq 0 ✔The line names the hat revision the conversation now wears and the switch’s place in that conversation’s sequence.
3. A privileged hat waits for your yes
Section titled “3. A privileged hat waits for your yes”quox hat use devops --conversation QXC_3681e2b9-e4c3-41cb-a0a9-9f519ef50478✖ 'devops' is a privileged hat. Re-run with --yes to wear it.The switch was refused, so nothing changed until you confirm it with --yes. In a chat, /hat devops asks y/N first.
What just happened
Section titled “What just happened”A hat decides which tools a conversation carries. Switching it changed only that one conversation, and each switch was recorded on the server. What an agent may actually do still comes from its own grant, whichever hat it wears.
Check it yourself
Section titled “Check it yourself”quox hat list marks each hat privileged or not, so you know before you switch which ones will ask you. In a chat, /hat alone lists the hats with the one this conversation wears marked.
quox hat use default --conversation QXC_3681e2b9-e4c3-41cb-a0a9-9f519ef50478Ⓠ QUOX │ conversation QXC_3681e2b9-e4c3-41cb-a0a9-9f519ef50478 now wears default │ rev 5 · seq 1 ✔Switching back is another recorded switch, so the sequence moved on to 1.