I’m discovering the Ai integration in CM 1.2 and have a few questions.
I connected a Claude Sonnet 4.6 API key and enabled Ai Features + Ai Agent.
No Vision / Image Provider is added.
When working in the chat, i can add an image (screenshot to expose info) via an ‘Upload’ button close to the prompt field but it’s not uploaded to the chat, why is that?
I asked Claude to create a simple PHP shortcode and add it to a CM snippet field that was opened in the same window. It wasn’t possible because “No Abilities Available”, i had to copy-paste the shortcode manually, is that the expected behaviour in CM?
For a simple short text chat, Claude spent 13K input and 2K output tokens which seems huge. Is there a way to limit the expense without sacrifying quality?
A few exchanges later in Claude chat: 46K input / 3.3K output
In my Claude Console, caching seems disabled:
You are not using prompt caching.
Add a cache_control block to your requests to reuse expensive context. Most organizations see a 50–90% reduction in entry costs.
Would it help saving tokens?
Is it to enable at the CM plugin’s level or in Claude account?
How to proceed?
[EDIT] Claude answer:
Where do you enable it? In the Classic Monks plugin settings, not in the Anthropic Console. The Console only informs you that you’re not using it—the application (the plugin) must add the cache_control blocks to its API requests.
→ Look for a “Prompt Caching” option in the Classic Monks settings or open a support ticket to ask if it’s implemented.
Hey @avanti really appreciate you sharing this, especially catching that prompt caching wasn’t active. That one detail is a huge help.
We’re already working on implementing it. The cache_control blocks need to be set on our end in the API requests, not through the Console so that’s on us to fix. Once it’s in, you should see a solid drop in those input token counts, especially after the first message or two in a conversation.
Will keep you posted when the update is out. Thanks again for digging into this!
