Type, paste, or ramble one rough thought. Then pick a hat.

  • One hat: a finished client email, ready to send.
  • Another: meeting notes with every action item under the person who owns it.
  • Another: an engineered prompt ready to run, even from a messy brief.

A hat doesn't clean up your sentences. It rebuilds the thought behind them into a finished result, and invents nothing you didn't put in. You do all of it in the HatVox web app.

How it works

  1. Pick a hat

    HatVox runs in your browser at app.hatvox.com — there is nothing to install on your machine. Installing a hat means adding it to your account. Browse the catalog, or build your own.

  2. Say it or type it

    Speak it, type it, or paste text in — and mix all three in one draft. There is no format to learn and no prompt to write.

  3. Get the artifact

    What comes back is the finished thing that hat makes, ready to send or paste into whatever you were already using. Not a transcript, and not a tidier version of what you said.

Different problem, different hat. Here's each one at work.

Switch hats

Meeting Notes

A quick multi-topic status update recounted from memory — a couple of done items, a bug, and a thought about next week.

What you said

So um quick update on where things are. The auth migration is done, Sarah merged it yesterday, all tests passing. The uh the admin dashboard is like 80 percent there, I still need to wire up the snapshot restore button but the UI is all built out. Oh and Jake found a bug with the live recording on Safari, something about the websocket dropping after like 30 seconds? I told him to file an issue. And then for next week I think we should prioritize the hat management UI because people keep asking about it in the Discord.

What you got

Summary

Sarah merged the auth migration yesterday — all tests passing. The admin dashboard is about 80% done; I still need to wire up the snapshot restore button. Jake found a Safari bug with live recording, and I told him to file an issue. For next week, I think we should prioritize the hat management UI given the Discord requests.

Action Items

  • [Me]: Wire up the snapshot restore button on the admin dashboard
  • [Jake]: File an issue for the Safari WebSocket live recording bug

Discussion Notes

Admin Dashboard

The UI is fully built out. The one remaining piece is the snapshot restore button, which I still need to wire up.

Safari Live Recording Bug

Jake found a bug where the WebSocket drops after about 30 seconds during live recording on Safari. I told him to file an issue.

Next Week Priorities

I think we should prioritize the hat management UI — people keep asking about it in the Discord. This is a proposal, not a confirmed decision yet.

Assumptions

  • I'm reading "I think we should prioritize the hat management UI" as a proposal, not a confirmed decision — no clear commitment language was used, so I left it out of Decisions.

Why it’s better

The recap is grouped by topic instead of replayed in order, and each task became an action item owned by the right person — the Safari fix is Jake's because you asked him to file it, the dashboard work is yours. "I think we should prioritize" is correctly kept as a proposal, not promoted to a decision. It's all in your own voice ("Sarah merged it," "I told him"), and nothing was invented.

Design Revision Director

A quick spoken review of a pricing-page draft, handed to the designer who has the file.

What you said

Okay quick one on the pricing page. The headline font feels too small, bump it up. And the second button, the outline one, can we make it filled like the first one so they match. That's it, the rest is good.

What you got

Changes

  1. [DIRECTIVE] Increase the headline font size on the pricing page. The current size reads as too small — bump it up. (Exact size not specified; use judgment or check with the reviewer before shipping.)
  2. [DIRECTIVE] Change the second button (the outline-style one) to a filled style to match the first button.

Leave Alone

  • Everything else on the pricing page.

Why it’s better

Two rambled asks become two tagged directives in priority order, the “rest is good” turns into an explicit Leave Alone so nothing else is touched, and the unspecified font size is flagged instead of invented.

Bug Report

A quick spoken report of a bug hit mid-work, with no environment or severity stated.

What you said

So the save button on the settings page doesn't actually save when I click it. It just does nothing, no spinner, no error, nothing. I tried refreshing the page and clicking it again and it's the same thing. Um, I'm pretty sure it was working last week.

What you got

Save button on settings page does nothing on click

Summary

Clicking the Save button on the settings page produces no response — no spinner, no error, and no confirmation. The issue persists after a page refresh. The speaker believes it was working as recently as last week.

Steps to Reproduce

  1. Navigate to the settings page.
  2. Click the Save button.

Actual Behavior

Nothing happens. No spinner, no error message, and no confirmation is shown. Changes do not appear to be saved.

Notes

Reported as a regression — the Save button was working as recently as last week.

Assumptions

  • Environment: Not specified. The affected version, build, browser, OS, and whether this is on staging or production are all unknown.
  • Severity: Not stated. Given that saving settings is non-functional, this may be high priority, but severity has not been confirmed by the reporter.
  • Blast radius: Unclear whether this affects all users or a specific account, and whether it is consistent or intermittent.

Why it’s better

Every fact you gave survives — the dead Save button, the failed refresh, the "worked last week" regression hint — restructured into a titled, scannable ticket. And the three things you did not say (which environment, how severe, how wide the blast radius) come back as explicit Assumptions for the triager to confirm, not as invented values. Nothing is fabricated; nothing actionable is dropped.

Delegate

A quick spoken delegation with an owner, a deadline, and one scoping detail.

What you said

Um okay so can you have Priya put together the Q3 social calendar, just the posting schedule not the actual copy, and I need it by end of day Thursday so I can review it before the client call on Friday morning.

What you got

Task

Priya to put together the Q3 social calendar — posting schedule only, no copy.

Owner

Priya

Requirements

  • A posting schedule covering Q3
  • Schedule only — no post copy or creative required

Timeline

End of day Thursday (to allow owner review before Friday morning client call)

Done When

Priya has delivered the completed Q3 posting schedule by end of day Thursday and it is ready for review.

Why it’s better

The filler is gone and the one task is crisp — owner, deadline, and the "schedule only, no copy" scope all preserved. It stays a short brief instead of padding out every section, and the one thing you didn't specify — which channels the schedule covers — is surfaced as a question to confirm, not invented into the brief.

Work Email

A one-line spoken note to a colleague.

What you said

Tell Sarah I'll be about 10 minutes late to the standup. Something came up with the deploy and I need to watch it.

What you got

Hi Sarah,

I'll be about 10 minutes late to standup — something came up with the deploy and I need to keep an eye on it.

Talk soon,

Why it’s better

A two-line note stays a two-line email — greeting, the point up front, a quick sign-off. It reads as warm and professional without being padded into a formal message, and nothing is invented.

Prompt Builder

What you said

OK so I want a prompt for, um, generating blog post ideas. For a, it’s a B2B SaaS company that does, uh, expense management software. The audience is finance teams, like CFOs, controllers, that kind of person. I want like ten ideas, no wait, give me maybe eight, and each one should have a working title and a one sentence angle. And keep it, you know, not too salesy, more educational. Oh and it should avoid topics we’ve already covered so I’ll give it a list of our existing posts.

What you got

You are an experienced B2B content strategist specializing in fintech and SaaS.

Task: Generate 8 blog post ideas for a B2B SaaS company that makes expense management software. The target audience is finance professionals — CFOs, controllers, and similar roles.

Context: The content should be educational and informative in tone, not promotional or salesy. The ideas must not duplicate any topics already covered in the existing post list below.

Existing posts: [paste your list of existing blog post titles here]

Output: Return exactly 8 blog post ideas. For each, provide:

  1. A working title
  2. A one-sentence angle explaining the editorial focus or key insight

Present the ideas as a numbered list.

Why it’s better

The mid-sentence correction (ten → eight) resolves cleanly, the existing-posts list you will supply becomes a placeholder, and the scattered ask lands as a structured task / context / output prompt you can run as-is.

Browse all 20 hats

FAQ

Is this a transcription app?

No. Transcription is a step, not the product. HatVox transforms your speech into role-specific output.

Who is HatVox for?

Anyone who turns rough thoughts into finished writing. Developer Elite is one hat; Meeting Notes, Casual Convo, Work Email and others each transform differently.

Is this a one-time thing, or daily use?

Daily. The value compounds with use, and HatVox is designed for repeated use in a real workflow.

Do I need to configure anything first?

No. Pick a hat, then speak or type. Sub-contexts are optional power-ups.

Is my data safe?

Authentication is self-hosted with Better Auth. Audio is processed for transcription and is not stored by HatVox after transcription completes.

Does it work with Claude CLI and Codex CLI?

Yes. Developer Elite output is structured for direct paste into both.

Say the thing once. See what comes back.

Start with any hat in the catalog. The one that matches today's job will prove itself faster than any description of it.