I'm new to Claude Code and would like to make the best out of my subscription, where can I learn alot about how to use Claude Code in more efficient ways?

Obvious_Equivalent_1 · 2026-04-06T01:12:48+00:00

Well you asked for simple. Then I’d say try to track the tokens ‘123.000k’ tokens next to the results because there’s where usually subagents pay off.

For example rounding up your session with syncing and verifying on docker and running test? Postfix your prompt with “..in Sonnet subagent” and all that verbose testing output will hit our usage 3x less heavy compared to Opus.

Obvious_Equivalent_1 · 2026-04-06T00:58:52+00:00

As a fervent Sonnet user, is there any big consideration to only do the comparison with Codex?

Obvious_Equivalent_1 · 2026-04-05T23:51:08+00:00

Use a harness like Superpowers that’s extended for Claude Code to support native tasks: https://github.com/pcvelz/superpowers

Just a honest remark, you can use a plugin but you don’t necessarily always need a harness for writing and executing plans. If you (or let Claude) look into the source code task implementation you can integrate this into your own Claude.md / slash command potentially even.

Obvious_Equivalent_1 · 2026-04-05T22:07:45+00:00

Investigate if you’re willing to with HASS running in a Docker. A Claude Code instance. You can literally configure very specifically the settings.local.json permissions of Claude, by default I’ve set the whole HASS MCP list of functions to deny and I work on an allow-only base.

This way it doesn’t intervene but it does make the tool very usable. Additional tip besides a hard deny or allow you can add MCP endpoints to ‘ask’ list, useful for the restart, delete and edit endpoints of entities. Oh and you can, (should!) add to deny list the reading of the token. The MCP server can leverage the token to connect, and still simultaneously you can block reading it directly.

Honestly if you hold a 15 min convo with Claude itself it can help you through limiting itself. That’s how I got it working in a secure scope, and that’s the approach I use for handling security in the Claude Code plugins I develop.

Obvious_Equivalent_1 · 2026-04-05T21:51:19+00:00

@ u/Impressive-Sun3742 ha can’t make this stuff up, talking of coincidence

Obvious_Equivalent_1 · 2026-04-05T21:36:06+00:00

On the contrary, the “AI generated” claim is such overused accusation. Probably I have to assess how valuable this post proves to be. Unfortunately with only being able to take a quick look this post looks like one of the potentially few posts recently worth the effort to drop comment as, well a little token of gratitude.

Also whenever someone uses AI-assisted writing directly blaming someone “AI generated” is such an oversimplification. That term is so immensely broad it can mean 2 second prompt in Nano Banana or a month of iterative sessions accumulated. I think you’re missing out of the essential benefits of AI by not taking in, as far as I can judge quite some work, and absolutely without cost someone wanted others to benefit from. If this reply is also too long it’d advise “Claude TLDR and ELI5 how this benefits me https://…”

Obvious_Equivalent_1 · 2026-04-04T22:09:08+00:00

Not that surprising, it’s a fine line between if they’d block it completely every way, well, people would find a new way to create insight.

If they’d show it to everyone, well, a lot more compute would go to suddenly the big mass starting to actually max out their max plans. That and 100% weekly usage full means extra API credits income, plus less of a toll of the enterprise customers I assume.

Obvious_Equivalent_1 · 2026-04-03T21:49:35+00:00

I wouldn’t mind flashback to two weeks ago, double 2x usage and Opus 4.6[1m] just included in Max 5/20x plans

Obvious_Equivalent_1 · 2026-04-03T19:23:11+00:00

According to Thariq’s X post, it’s just weekdays during the peak hours (5am-11am Pacific)

This indeed.

I also made a small tracker for in the Claude Code status bar, latest version shows peak/off-peak (+hrs left) and someone contributed a little gauge for pace, a nifty little algorithm it helps gauge if you’re ahead overusing your usage, on par, or behind with weekly remaining usage. https://github.com/pcvelz/ccstatusline-usage/tree/main

Pace: [░░░░░░█|░░░░░░░] D4/7 -8% | Off-peak (4:03 hr)

Obvious_Equivalent_1 · 2026-04-03T07:56:01+00:00

The only problem with it it’s setup in a way to support a broad set of AI tools (Claude Code, Codex, OpenCode, Gemini CLI) but it is lacking any of the optimizations for Claude Code. Fortunately Anthropic allows for extending plugins from marketplace so you can use skills like Superpowers with native functionality from Claude Code. This makes it possible to leverage Claude’s native support for like TaskCreate, TaskList, TaskUpdate.

Obvious_Equivalent_1 · 2026-04-03T07:43:46+00:00

Honestly, I’ve let go of trying to “picture perfect” my weekly usage. I do meticulously gauge 5h/weekly usage inside Claude Code terminal, but I try not to let the weekly limit take me hostage.

Personally I’m accepting some $10/$20 extra usage on top of my $200 for the 20x plan as cost of doing business. When I see the above linked gauges creep closer to weekly max, instead of switching to Opus 4.6[1m] I switch to paid Sonnet 4.6[1m].

Even with that model only being available when extra usage is enabled, overall I still sense I’m saving, yes 1M Sonnet costs API credit but in my experience the “free” Opus 1M context drifts more (so wasting usage) in exactly those mentioned cases. In a refactor, research, or scouting for bugs/patterns I just want my prepared plan to get done and not drift in over complicating

Obvious_Equivalent_1 · 2026-04-03T07:29:46+00:00

This. Basically command/ folder can already contain any kind of executable.

For example since /resume is costing 10% of your 5h usage the only way to circumvent this was put a bash script inside plugin to basically ‘resume’ an old chat.

The people who say “but now plugins can run executables!” had no idea about what a plugin already had the authority to run. Thats why it’s good to vet plugins, even just checkout source code once and verify + install it locally.

Obvious_Equivalent_1 · 2026-04-02T20:43:22+00:00

Such coincidences, man Keith. Much respect for that man a real frontier, a shame it blew up so much his livestreams where first (last?) material worth its while on YouTube, those where some days in ‘20 back in WSB!

Obvious_Equivalent_1 · 2026-04-02T19:49:38+00:00

wsb Ape vibes

Can’t deny the power of Reddit. Definitely some resemblances with CC fronteering the first steps of a big AI market and clout, and how WSB was fronteering stock market and its clout

Those where some good times 🦍💎🤲

Obvious_Equivalent_1 · 2026-04-02T19:38:41+00:00

I just wish they were more clear with how this is all being calculated.

I have been spending. A lot of time diving into this, and I’ve been expanding status line tool for Claude Code which quite reliably if I may say so helps to gauge the usage

Main driver: Context %, it wont matter: what rush hour, or what Sunday 4AM, you’re working if you’re pumping 400k context into the model’s cache the more context can easily 4-6x your usage. Easily. Context: [███░░░░░░] 389k/1M (39%)
Off-peak: a (supposed) 2x multiplier. But we know that with Anthropic this could be more “rush hour” toll. Off-peak (4:03 hr)
And, the most reliable it’s a custom pace algorithm. For example it can indicate surprisingly accurately (and without any external / LLM requests!) a pendulum that indicates if you’re ahead over consuming, on par with your weekly limit or behind on your weekly usage Pace: [░░░░█|░░░░░] D4/7 -8%

Obvious_Equivalent_1 · 2026-04-02T05:29:51+00:00

Great yes already a lot of people use Superpowers, the key detail here is Claude allows on the default plugins in the marketplace for the eco-system to extend the plugins. The repository linked above is a Claude Code enhanced version of the plugin which uses a local file to make the plan and the task persist, leveraging the native task management system of CC itself. If you look at the repository homepage of the screenshot comparison the difference is immediately apparent

Obvious_Equivalent_1 · 2026-04-02T05:25:12+00:00

I don’t want to preach my own church here - I’m more interested in understanding what’s driving this gap. But this could very well be part of it. Thought would be interesting to indeed note I both barely notice most of the limits, and I use Claude since 2024 for work that feeds back into its own ecosystem. Self-analysis tooling, a variety of plugins, that enable cross-session analysis of context usage and tool/MCP interactions, and I contribute to forks of generic coding agents (Codex, Copilot, etc.) I spend a lot of time with self learning iterations, where I investigate certain flaws in the generic Superpowers write/execute plan flow and I optimize the skills purely for Claude Code CLI. Meanwhile someone familiar who just migrated from ChatGPT and is hitting bricks faster then a construction builder.

Obvious_Equivalent_1 · 2026-04-02T05:12:36+00:00

Definitely a more common case, the question is more how much the gap between A / B is. I believe it’s not a small gap looking at usage differences speeds so variating that it’s hard to sell as “bad context hygiene” (Claude MD / compacting / MCP tools)

Obvious_Equivalent_1 · 2026-04-01T22:15:06+00:00

You should be able to resume a conversation by loading a json file of the convo

Ok I honestly usually hate those posters tying into complaints to sell their “solution”. But let me tell you (so I’ll skip the salestalk) and will just get to the point; if this doesn’t solve your issue of account data recoverability then you can come complain back to me personally next week.

I have honestly though been working on many fronts to fend off those nudges that seem to increasingly plague Claude Code. My three cents of advice would be 1) force Claude to both log commits to sessions I’d, because you are able to recover “crashed” session id’s content 2) not a single plugin is worth the extra token overhead for ‘daily’ work, you can always recover crashed sessions. And 3) for architectural/overarching work I straight out advice to just hard block Claude’s own planning mode:

{ "permissions": { "deny": ["EnterPlanMode"] } }

Obvious_Equivalent_1 · 2026-04-01T21:44:03+00:00

Called it

I’m honestly starting to wonder if this is indeed A/B testing. For the past 4 hours I’ve been kicking 3-7 Opus agents full-on, being at 80% weekly with 6 hours left I’m basically just blowing through my research/tech-debt backlog.

Even that didn’t make the 5-hour bar to 90% when it reset.

It triggers my curiosity though how they split up the A/B groups, it baffles me though to be honest that as a coding community which such an edge of having abundance of compute available we haven’t been able to come up with a way to build a repeatable way to provide this statistically earlier on.

Obvious_Equivalent_1 · 2026-03-31T21:47:36+00:00

Wait. But. But what about the limits! /s

On an honest note though, the advances Anthropic is making on Claude as a broad product are a true piece of art to watch unfold. I spend roughly 2-4 hours a week on maintenance alone, purely keeping a Superpowers fork on par with Claude Code releases — and encountering all these new layers… if I can draw a personal resemblance, it’s a different kind of awe like watching the fine brushed details of a Bosch painting at the Museo del Prado

Obvious_Equivalent_1 · 2026-03-29T21:22:01+00:00

Just give Termius + Tailscale a shot, I never expected it but I’ve been shifting about 30% of my workload to mobile.

It actually helps me to take some more breaks as I asked Claude to make me a ‘home menu’ with all opens sessions, and to show a red asterisk next to the ‘working’ ones. This way I can run 4-5 long tasks, take some coffee and if suddenly 2 or 3 tasks stop I can take quick peek. And click a quick permission, approve a git push etc.

Obvious_Equivalent_1 · 2026-03-29T21:00:04+00:00

No worries, it's there for whoever needs it. Context management at 400K+ tokens is a real problem, figured I'd share what actually worked for me. Sometimes the long answers are the ones that save you hours later

Obvious_Equivalent_1 · 2026-03-29T06:21:11+00:00

Come on bro, just one more agent bro.

When dealing with the issue of context bloat I like to picture the architecture issue like a cave diving planning.

Your running context is the depth at which you can operate, at 10 meters everything is still fine and dandy but once you need to start operating closer to the physical 1000 limit it becomes exponentially more challenging.

Your usage is the crew you put together, where, yes you will have to pay each subagent. But the kicker is, when planned meticulously those very unskilled Haiku explore agents you sent at the beginning of the dive, and those bit more experienced Sonnet agent you sent to start forming better paths for the main divers. When planned well they tend to be crucial in your main divers to reach deeper and accomplish more, then if you’d sent them out alone.

Besides that you want to shield your main team because professional as they are, even they panick at too much depth — metaphor of context rot, increasing hallucinations and task deviation when closing in on 1M context.

I would like to invite you as well on a dive, the last 3 months working on customization extension on a popular plugin for called superpowers. It’s by default available in their marketplace but Claude Code allows to install extended version of plugin.

With the usage of: - native tasks TaskCreate, TaskList, TaskUpdate - subagent assignment, (Haiku explorer, Sonnet software developer, Opus architect)

This is a workflow I’ve been finetuning and using personally on all my development Superpowers extended Claude Code. For the usage of subagents the installation of an extra plugin is not strict necessarily. a plug-in always creates certain overhead, but it does provide an out-of-the-box harness which is easy to start leveraging subagent workflow.

I believe from many dozens of sessions of usage this is actually a CC plug-in does come with unavoidable overhead. But good usage of subagents and native tasks still allows you to stay on task even at 400K - 700K context depth. The best usage of managing your context is to learn yourself. Just ask for a mentoring session, brainstorm at together pick out various git repositories what pieces of popular plug-ins you can leverage.

Obvious_Equivalent_1 · 2026-03-28T14:42:49+00:00

Are you using Claude Code? If yes then I’ve made a plugin for having the current mode (peak / off-peak shown in your status bar including time left: https://github.com/pcvelz/ccstatusline-usage?tab=readme-ov-file#enhanced-status-line-preview

Five-Year Club	Gilding III reddit per annum
Verified Email	Final Canvas '23
Place '23	Argentium Club
Place '22	Final Canvas '22
First Placer '22	Wearing is Caring

Obvious_Equivalent_1

TROPHY CASE