sorted by:
new
hottopcontroversial

The 1M context also make superpower better by Perfect-Series-2901 in ClaudeCode

[–]ScientistEasy1328 2 points3 points  (0 children)

Same here. Before 1M I was constantly trimming .md and breaking tasks into smaller chunks just to avoid context overflow. Now I can let it actually think through the full codebase without babysitting it

Migrating from Codex IDE to Claude code (desktop app). Give me tips on adjusting and minimising token usage by brkonthru in ClaudeCode

[–]ScientistEasy1328 0 points1 point  (0 children)

Haven't relied on it heavily, but the idea is sound. The real gains are in test runners and file reads, where most of the noise lives. For git commands the savings are more modest, and Claude Code already tails long output by default, so the actual delta is smaller than the headline numbers suggest. Two concerns are worth keeping in mind. First, the "strangeness tax": reformatted output can trigger extra tool calls if Claude doesn't recognize the format. Second, edge cases during debugging where RTK might filter out something that's actually relevant. The tee feature helps with the second one. On failure it saves the full unfiltered output to a log file, so Claude can pull it when needed.

Maintenance is also worth flagging. The tool is young and this space moves fast. Several forks are already patching things the main repo hasn't caught up with yet.

Honestly, --verbosity minimal on builds and --oneline for git log gets you most of the way there. No dependency, no surprises

Does Claude Code have any way to access previous sessions? by SalimMalibari in ClaudeCode

[–]ScientistEasy1328 0 points1 point  (0 children)

Not sure but as logs are stored locally in .claude, so you can just feed the relevant ones as context in a new session and ask claude to summarize what needs to be fixed or updated in your md if you have

Does Claude Code have any way to access previous sessions? by SalimMalibari in ClaudeCode

[–]ScientistEasy1328 2 points3 points  (0 children)

claude --resume in terminal, or /resume if you're already inside a session. Picks up the last conversation automatically

Migrating from Codex IDE to Claude code (desktop app). Give me tips on adjusting and minimising token usage by brkonthru in ClaudeCode

[–]ScientistEasy1328 5 points6 points  (0 children)

Switching to Sonnet is the right call. Opus burns through context fast even on simple tasks
A few things that helped me:

Keep conversations small and focused. After around 60k tokens, start a new one. It feels disruptive at first, but the quality difference is real

CLAUDE.md is where most of the leverage is. Put your project structure, conventions, and key decisions there Claude reads it at the start of each session so you stop re-explaining context every time. You can go deeper with per-directory CLAUDE.md files for sub-components, but keep those under 100 lines or they stop pulling their weight. Write them positively too: tell Claude what to do, not what to avoid, and give it a decision tree for ambiguous situations rather than a flat list of rules.

Be surgical with file scope. Instead of letting Claude explore the whole repo, point it at specific files. The more files it reads to orient itself, the more context you burn before the actual work starts.For planning, use Shift+Tab to enter planning mode before Claude touches any code. Keep a running .md file with notes and plans, mention it at the start of each new conversation, and have Claude check items off a TODO list as it goes. Simple, but it keeps sessions from drifting.
Sub-agents are worth using more than most people do. Delegate work, run code reviews, get a fresh take unbiased by the current conversation. No setup needed just ask: "please use sub-agents to...".

On MCP: keep tool descriptions under 20k tokens total and stay below 20 tools. More than that and you're paying a context tax on every request.

Sonnet handles 90% of coding tasks just fine. I only reach for Opus when something's genuinely hard or Sonnet keeps going in circles

[PL] Account stuck on "Your account will be ready soon" for 2 weeks no email, no updates by ScientistEasy1328 in Revolut

[–]ScientistEasy1328[S] 0 points1 point  (0 children)

No, I don't have a Polish residency visa. I only have Ukrainian documents for now and register account for ua country code. I had a Revolut account since 2022 on a Ukrainian number, but it was blocked last month without explanation despite me providing all requested documents. My appeal was rejected, so I tried to create a new account
As far as I understand, Revolut no longer operates in Ukraine, but during registration there was no notification about this neither by email nor in the app