[FEATURE] Enhancement: expand thinking verb list to include user-configurable or more varied options

Resolved 💬 4 comments Opened Mar 29, 2026 by danielrodonnell Closed Apr 23, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I quasi-enjoy Claude Code’s quasi-humorous repertoire of quasi-present-participle euphemisms for “thinking” (“Gusting” is alllllmost a fart joke 😃). However, I’m pretty sure I’ve seen them all by now, and I’m bored.

Proposed Solution

I’m requesting that these verbs be user-configurable. I would like to be able to control/maintain Claude’s “thinking” vocabulary myself so I can introduce him to the wider world of fart jokes, toilet humor, penis pranks, etc. (for my eyes and personal amusement only, of course). You see, the task of telling Claude what code to write is significantly more boringer than actually writing my own code, so I feel that the least I should be able to expect of him is that he periodically punctuate the monotony of my day with a smirk/giggle/snort by informing me, apropos of nothing, that he is ball-fondling, fart-noodling, pocket-pooling, scrodaddling, slurping, drooling, Hershey-squirting…you get the picture. #blamecanada

Of course, the less cultured user may wish to adopt a more low-brow theme, something like poseying, kaleidoscoping, muraling, astro-planing, suntanning or some such filth. To each their own, I suppose.

All kidding aside, this seems like a fairly small lift, technologically, and I think Claude users everywhere would appreciate this feature.

Alternative Solutions

_No response_

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

User: create an R package for real-time calculation of winning odds during a baseball game, based on score, inning, outs, men on base, etc.

Claude:

Teabagging… (thinking)

Additional Context

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗