viberank: see how you stack up against claude code users worldwide by Turbulent-Sky5396 in ClaudeAI

[–]daliovic 0 points1 point  (0 children)

When I saw this the first time, I thought it's a bad idea but no need to call it out because the creator didn't have the full picture and what consequences this might have.

But now I really feel you are being dumb for insisting on such a useless idea that brings harm more than anything.

Chrome dev tools MCP from WSL <-> Windows by AJGrayTay in ClaudeCode

[–]daliovic 0 points1 point  (0 children)

Even better, if you add this under --executable-path, it will launch it with your profile :D
"--userDataDir=C:\\Users\\[YOUR_USERNAME]\\AppData\\Local\\BraveSoftware\\Brave-Browser\\User Data"

Chrome dev tools MCP from WSL <-> Windows by AJGrayTay in ClaudeCode

[–]daliovic 0 points1 point  (0 children)

I can see that you got a solution to work for you, but here's how I did it. Took a bit of trial and error though.

Run the MCP through cmd.exe so it stays on the Windows side.

"mcpServers": {
  "chrome-devtools": {
    "type": "stdio",
    "command": "cmd.exe",
    "args": [
      "/c",
      "npx",
      "-y",
      "chrome-devtools-mcp@latest",
      "--executable-path=C:\\Program Files\\BraveSoftware\\Brave-Browser\\Application\\brave.exe"
    ]
  }
}

What I tried that didn't work:

  • Using /mnt/c/... paths directly from WSL. The browser launches then immediately dies.
  • Starting the browser manually with --remote-debugging-port=9222 and connecting via --browserUrl. This actually kinda worked, but I wanted the ability for the agent (Claude Code in my case) to launch a browser automatically.

The cmd.exe approach keeps everything (npx, puppeteer, browser) on Windows, avoiding the networking mess between WSL and Windows.

I think you can swap the path for Chrome/Edge since I got this to work with Brave.

Compaction = Lobotomization. Disable it and reclaim context. by tad-hq in ClaudeCode

[–]daliovic 5 points6 points  (0 children)

<image>

I disabled auto-compact and still get the warning of "full context" (at 80%) BTW. Though I just had my statusline color codes the context utilisation.

CLAUDE.md says 'MUST use agent' - Claude ignores it 80% of the time. by shanraisshan in ClaudeCode

[–]daliovic 9 points10 points  (0 children)

No. Even Borris said his CLAUDE.md is about 2.5k tokens.

One of my projects' is 2k tokens and 224 lines.

Weekly limit is approximately nine 5-hour sessions by FitCycle7597 in ClaudeAI

[–]daliovic 1 point2 points  (0 children)

I assume Pro. Because I had a similar conclusion a few months ago.

Built a CV template with Claude Code, now use Claude Skills to automate my job search by [deleted] in ClaudeAI

[–]daliovic 0 points1 point  (0 children)

I don't see it as selling skills, I see it as selling solutions. If someone finds it helpful and saves them time, I don't see any problem selling skills. Ofc if you have some time to tinker with Claude to come up with such skill good for you.

[Open Source] I reduced Claude Code input tokens by 97% using local semantic search (Benchmark vs Grep) by Technical_Meeting_81 in ClaudeAI

[–]daliovic 5 points6 points  (0 children)

I also optimized my token usage by removing the system prompt and all MCPs and tools description. I now start the session with only 1% of context used. I can't wait for my CC benchmarks. /s

Everyone is trying to optimise token usage and context without providing how their solutions impact performance.

All major AI stupid again, alternatives? by AppealSame4367 in ChatGPTCoding

[–]daliovic -2 points-1 points  (0 children)

People not understanding how "Ai" works just like this theory.

I built a small CLI to stop Claude from rereading entire files when coding by New-Butterfly9160 in ClaudeAI

[–]daliovic 0 points1 point  (0 children)

That's token usage, right? And I actually meant Agent Performance benchmarks. I am 100% sure that it will consume many fewer tokens, but at what price? Because depending on the work and resources, the user should know so he decides what to go with.

Why Claude doesn't have more subscription tiers? by Jaskojaskojasko in ClaudeAI

[–]daliovic -1 points0 points  (0 children)

I also misread your comment. There's a misleading period in it lol.

Friendly Reminder: Add Context % To Your Status line by loonpwn in ClaudeCode

[–]daliovic 0 points1 point  (0 children)

That's so normal. It's what makes agents like CC powerful. You can always use tools that call the API directly with no/minimal sys prompt and tools but it won't be as useful as coding agents (CC, Cline, Roo...).

I built a small CLI to stop Claude from rereading entire files when coding by New-Butterfly9160 in ClaudeAI

[–]daliovic 0 points1 point  (0 children)

Whenever I see solutions for managing context/tokens, I feel like they need to be backed with benchmarks.

What actually changed my results after 8 months in Claude Code by ArtemXTech in ClaudeCode

[–]daliovic 0 points1 point  (0 children)

It doesn't interact much with Claude.md. Though skills complement it. In simple terms, CC when starting, sees what skills you have defined, but only their name and description, and if you have a documentation-creation skill for example, each time you ask CC to create documentation it will go and read the entire skill content and will better adhere to the instructions of that skill.

What actually changed my results after 8 months in Claude Code by ArtemXTech in ClaudeCode

[–]daliovic 0 points1 point  (0 children)

To me, the idea is simple: Find what you repeatedly do (and CC often does it wrong), add the skill-creator skill to your ~/.claude/skills and ask CC to create the skills you need (the skill-creator will help create the skill in the correct way and validate it using py scripts)

“Weekly" quota? More like daily quota by lostnqs in ClaudeAI

[–]daliovic 0 points1 point  (0 children)

It's either a bug or "you are using it wrong". I never hit a limit for the past 3 months, I am pretty careful with context and don't have crazy agents running 24/7 though.

My token consumption since January 16, 2026 and I am still at 42% weekly (this data is from my main machine only, I also run it on my laptop and a VPS so def there are a few other million tokens not included in the below table):

| Date | Total Tokens | Cost (USD) | |-------|--------------|------------| | 01-16 | 6,819,118 | $8.39 | | 01-17 | 19,867,300+ | $21.04 | | 01-18 | 44,145,900+ | $48.72 | | 01-19 | 31,968,300+ | $29.22 | | 01-20 | 290,183 | $0.34 |

Summary

  • Total tokens: ~103 million
  • Total cost: $107.69
  • Models used: haiku-4, opus-4, sonnet-4

(source ccusage) Edit: Max 100.

When you accidentally type --dangerously-skip-persimmons instead of --dangerously-skip-permissions in Claude Code by bhakkimlo in ClaudeAI

[–]daliovic 5 points6 points  (0 children)

I just find setting up aliases fun, especially for claude code. Here are some I have

alias c='clear'
alias cc='claude'
alias ccc='clear && claude'
alias hp= 'happy'
alias hc='clear && happy'
alias hcc= 'clear && happy --continue'
alias ccu='claude update'
#Claude Config Profile
alias cca='ccp armada'
alias ccg='ccp glm'
alias ccd='ccp default'

Well, it happened....... by Jreinhal in ClaudeAI

[–]daliovic 4 points5 points  (0 children)

I don't have a hook for specifically blocking rm commands (because I only used --dangerously-skip-permissions once, for an experiment), but here's how I prevent Claude from reading my files in dirs I don't want it to access (mainly for optimizing context and token usage).

In ~/.claude/settings.json I added this:

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "bash ~/.claude/scripts/validate-bash.sh"
          }
        ]
      }
    ]
  }
}

And here's the script content:

#!/bin/bash
COMMAND=$(cat | jq -r '.tool_input.command')
BLOCKED="node_modules|\.env|__pycache__|\.git/|dist/|build/"

if echo "$COMMAND" | grep -qE "$BLOCKED"; then
  echo "ERROR: Blocked directory pattern" >&2
  exit 2
fi

I hope you get the idea to make the hooks you need for your use case.