Dictation prompts work in "Test Prompt using a Sample Transcription" but not in real situations
EDIT: Some interesting behaviour, I tried switching the app-specific prompt setting to a DIFFERENT one to try another technique. That worked, and so I switched back to the original one ("Claude Code Interaction prompt") and lo and behold it worked now! I made some edits, but it didn't update. So I switched back and forth between App-specific prompt settings, and that seems to force it to update the prompt! So actually, it's some kind of cache/versioning link setting between the app and the prompt. The workaround is to change prompt settings under App-specific prompt whenever you make a change the one you really want.
Hey there!
Huge fan of MacWhisper, thank you - you're massively reducing my RSI and speeding up my mind-to-text process.
However I have noticed that for some reason, a cleanup prompt I have for app-specific contexts isn't working. I have this "Claude Code Interaction prompt" which runs when I'm dictating while using Cursor - my assumption being that if I'm in Cursor, I'm probably talking to Claude Code. It does seem to be selecting the correct prompt:
However, the output is never what I expect. Here's the prompt:
INPUT:
This is a dictation transcript. The speaker is interacting with claude code via a terminal in their VSCode or Cursor app, and claude code has plenty of context around what the speaker is talking about. The speaker is probably talking about a Ruby on Rails app which uses Stimulus. Please flag this in a way which claude code would know it's a dictation.
Common phrases the user might be using which could've been misheard: <some proprietary terms I won't share>
OUTPUT
Your response MUST match the following template, so the output MUST look like the following, where "<CLEANED UP TRANSCRIPT>" is the cleaned up version of the original transcript:
```
NOTE: The following text was generated from a dictation transcript and cleaned up, but keep in mind it may have some errors due to mishearign the speaker.
"""
<CLEANED UP TRANSCRIPT>
"""
```
When I run it in the test prompt feature, the output is as expected every time. But in Cursor/Terminal, at best I get:
[DICTATION]
<What I said>
But usually it's just the dictation.
It does seem to clean things up and use my commonly-misheard words, but not all the fluff around it that I want Claude to see to help it guide my request.
Am I missing anything in the way I use this feature, or is this a prompt engineering problem?
Thanks!
1 comments · 100% upvoted · other discussions
I emailed the team with the similar problem, and they replied to me saying that the picker of the testing models inside the prompt configuration settings is only used for "testing the prompt", while the real model being used is decided by the global setting in the "Dictation" section (AI-Service under the subsection "AI-Powered Dictation") regardless of the prompt you choose in the pop-out blue bar (the prompts are effective but the model is irrelevant with what you set in the testing picker inside the prompt setting page).
I would also want a more flexible configuration for the prompts given different scenarios. For instance, for some casual talks, I want a quick output of the dictation, hence some lite models without thinking would suffice, and for some serious dictations, like describing the task to cursor, I would want a polished refined output generated by the pro models).