r/raycastapp

No need to fix Dictation on iOS, my broken arm is almost healed anyway

Three weeks ago I wrote here asking for a Raycast Dictation to be at least Wispr level quality. Especially annoying when you broke your arm, and this feature basically becomes accessibility requirement rather than convenience.

Almost a month in:
- same glitches: start dictation triggers recoding only half of the times, etc;
- same silly cringy transcription quality: I always start any message with «Sorry guys arm is broken using stupid dictation app that’s why text looks so weird” – made a snippet for that;
- same failure rate

Good news is that arm is almost healed and I’m writing this post without any Dictations features.

Stay safe really, armwrestling is not worth it…

reddit.com
u/valentinezubkov — 10 days ago

I think I’m done with Raycast - hidden token costs?

https://preview.redd.it/c95ubg3jt9th1.png?width=1469&format=png&auto=webp&s=46c0d6b3593e6c879c725a494d93c57a1aea2713

I noticed an increase in my OpenAI API spending and compared an older and a newer version of Raycast.

I used the same custom AI Chat preset with identical instructions and submitted the same text three times in each version. Each version had a fresh API key used only for this comparison.

The OpenAI dashboard showed:

  • Older version: $0.02
  • Newer version: $0.13

That’s approximately 6.5× higher spending, based on the displayed amounts.

Raycast’s documentation mentions server-side prompt processing and additional context in AI Chat. However, I haven’t found an explanation for this difference in a simple, repeated task.

I don’t know the cause yet. Can the Raycast team explain what might account for the increase, and how users can inspect the full token usage of a request?

Has anyone else noticed something similar? Unexpected API costs like this make me reconsider using Raycast.

reddit.com
u/Automatic_Error2978 — 12 days ago