Token Usage HIGH #1473
Replies: 4 comments 2 replies
|
What's preventing you from adding the caveman skill directly to deepseek-tui? |
|
Tried making caveman work with v0.9.0. The root cause isn't the skill itself — it's that user-level communication preferences don't propagate to sub-agents. Tested five approaches:
The hierarchy gap: system prompt (role + SUMMARY/EVIDENCE format) sits at top, unchangeable. User preferences sit at bottom. Caveman or any style directive can't cross that gap. Any of these platform features would fix it: (1) constitution entries at equal rank to role prompt, (2) auto-discovery for custom Fleet profiles with a default profile config, (3) skill propagation from parent to sub-agents. I'll see what comes out of Issue #4195 before I make more noise about this though. |
|
|
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I’ve been using the Claude Code CLI with a DeepSeek API key, and the token usage there was surprisingly low compared to DeepSeek TUI. DeepSeek TUI is costing me almost 3× more for similar workflows, probably because I was using the Caveman Skill setup in Claude Code.
Is there any equivalent mechanism or optimization in DeepSeek TUI that can reduce token usage while maintaining similar performance?
All reactions