3 ms·

claude package has ten new versions published per week, and one new model every few months, one should definitely not rely on some undocumented tricks around it

claude package has ten new versions published per week, and one new model every few months, one should definitely not rely on some undocumented tricks around it: it'll change, it'll break deep ultra-specific configurations

anuramat 4mo ago
in my experience, "undocumented tricks" break as often as documented features like when they removed "clear context and execute plan" option after releasing 1M opus because "context window is not a problem anymore"
- calgoo 4mo ago
  I so miss that clear context and execute plan mode! Now i have to keep clearing it manually again.
  - anuramat 4mo ago
    fyi you can re-enable it with `{ "showClearContextOnPlanAccept": true }` in ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/settings.json also find `"disableAutoMode": "disable"` useful, since I'm typically switching between yolo and plan
    - calgoo 4mo ago
      Thanks!!
- 0x457 4mo ago
  > like when they removed "clear context and execute plan" option after releasing 1M opus because "context window is not a problem anymore" I then show me banner that I can clean up "xxx.x k" of context by typing clear right after it started on the plan.
tstrimple 4mo ago
This is true, but also "temporal hacks" can make or break "cutting edge" workflows. I don't re-architect my claude instructions every release. But some releases justify examining your existing instructions and making sure they still fit the current model. And it has made a noticeable difference.
bredren 4mo ago
It is possible to build automation that efficiently handles low level customization of new versions as they appear.