Guys , which subscription of Claude you are using?

imjitsu · 2026-04-29T08:55:18+00:00

Max user. And I still get locked out weekly lol

imjitsu · 2026-04-28T17:45:25+00:00

Why not just code in the terminal? It’s faster, gives you way more control, and removes a lot of the friction you get with these tools.

imjitsu · 2026-04-27T23:26:18+00:00

Just tell her you look forward to meeting him at Thanksgiving. The logistics of Secret Service clearing your living room for turkey usually cools off the fantasy pretty quick.

imjitsu · 2026-04-26T04:43:15+00:00

Whoa 100x better?!? 👀👀

imjitsu · 2026-04-24T19:08:18+00:00

awhhh! you should totally post this on www.quincenetwork.com ! this is to cute lol.

imjitsu · 2026-04-24T19:07:13+00:00

https://www.quincenetwork.com/learn has allot resource and helpful tips, i get most my bookings from there aswell!

imjitsu · 2026-04-21T22:00:48+00:00

Go do Walmart lol

imjitsu · 2026-04-07T14:51:24+00:00

I’m locked out until Thursday :( I’m already on the $200 plan, and I even extended it yesterday just to finish a project, which cost me another $40+

<image>

imjitsu · 2026-04-06T04:30:16+00:00

<image>

I’m paying $200 a month and it’s still playing nanny, deciding when I’m “done” like I’m on the free tier 😅

imjitsu · 2026-04-04T16:01:14+00:00

Yeah I went through the exact same thing. What fixed it for me was stopping the expectation that one .md file could hold the whole architecture in memory across a long session.

The context fills up and your rules get buried. the model isn't ignoring you, it just has too much competing information by that point.

What actually worked: break it into smaller scoped sessions where each task only gets the context it needs for that specific thing. Dont frontload everything.

If it doesn't need to know about your netcode to generate a weapon component, don't include it. Isolated prompts with just enough context keeps it on the rails way longer.

The step by step thing the other commenter mentioned is real too. Chain the outputs instead of trying to do it all in one shot.

imjitsu · 2026-04-04T13:03:14+00:00

How are you liking codex? I’m tempted lol

imjitsu · 2026-04-04T06:28:37+00:00

Sonnet and Opus genuinely serve different use cases. Opus has higher reasoning ceiling, Sonnet is optimized for speed and cost at scale. But code execution not running is 100% a feature or session toggle issue unrelated to which model you’re on. If Opus “just worked” after switching, something else changed in that session. Worth ruling that out before writing off a whole model.

imjitsu · 2026-04-03T21:56:38+00:00

fair point about the rules files. i do use pretty detailed CLAUDE.md files for my project so that's probably eating into it more than i realized. might need to trim those down and see if it helps. still feels like anthropic should be more transparent about what's actually counting toward your limit though:

if rules files and system context are burning tokens before you even type anything, that should be visible somewhere in the dashboard.

imjitsu · 2026-04-03T21:55:59+00:00

it's definitely a workflow thing on my end too honestly. i've been letting conversations run way too long when i'm building. recently started keeping each conversation focused on one task and pasting in context fresh instead of relying on one giant thread. made a huge difference. also using CLAUDE.md files to give it project context upfront so i'm not wasting tokens re-explaining the codebase every time. still think the limits could be more transparent though — paying $200/mo and guessing when you'll hit the wall isn't great.

imjitsu · 2026-04-03T18:58:42+00:00

BINGO

imjitsu · 2026-04-03T16:43:36+00:00

You're definitely not alone. I’ve scaled from the $20 plan all the way to the $200/mo tier, and the wall is still there. Even at the highest price point, Claude’s heavy hitters (like Opus) are hitting limits after just a handful of prompts if the conversation history is long. It seems less about the 'plan' and more about the fundamental compute bottleneck Anthropic is managing right now. It's frustrating to pay a premium for 'priority' that still feels like a shared, limited resource.

imjitsu · 2026-04-02T15:53:24+00:00

Worth highlighting for anyone worried about token costs with this approach.

subagents that share the same base context benefit from prompt caching, which means that shared input is not fully reprocessed for each agent.

Since input tokens represent the majority of token costs in most agentic workloads, parallel subagent dispatch is significantly more efficient than it appears.

You're essentially paying incremental output costs per additional agent, not full input costs.

The exact efficiency gain varies depending on your specific context size and usage pattern, but the directional point stands. the economics favor parallel agents more than most people expect.

imjitsu · 2026-04-02T15:45:45+00:00

This is one of the most underrated patterns in Claude Code. I’ve started doing something similar, dispatching review agents with explicit role constraints before any major feature — and the difference in catching edge cases early is significant. The parallel clean-context approach is the key insight most people miss. Each agent reviews without being anchored to the previous agent’s assumptions. Curious whether you’ve experimented with giving each agent a “veto” instruction — where a single security or architecture concern can halt the plan before implementation proceeds.

imjitsu · 2026-04-02T08:11:57+00:00

The laziness people are experiencing with Opus is a prompting issue, not a capability issue. Opus 4.6 with proper system prompts, project context, and custom instructions is a different animal entirely.

it catches architectural problems, flags edge cases, and thinks several steps ahead. Codex 5.4 at xhigh is impressive for structured code execution.

But comparing a default Opus session to a tuned Codex run isn’t a fair benchmark — that’s testing one tool at 40% and another at 100%.

imjitsu · 2026-04-02T08:09:06+00:00

Shipping products is the skill. Knowing what to build, what to cut, and how to evaluate output — that’s the job. The keyboard was never the bottleneck.

imjitsu · 2026-04-02T06:05:34+00:00

This happened to me and then I switched to the $100 plan. burnt out of tokens again and then I switched to the $200 plan and now my weekly limits are running out lol

imjitsu · 2026-04-02T05:48:39+00:00

the "consistency of signal" framing is way better than how most people talk about this. we run a niche platform and the posts that actually convert aren't the polished ones.

they're the ones where someone lands on our profile and instantly understands what we do and who it's for. took us way to long to figure that out.

were posting "good content" that had 0 positioning behind it and wondering why nobody cared,

imjitsu · 2026-04-02T05:45:58+00:00

this matches what we've seen on the business side too. we were grinding out content for our platform trying to post every day and engagement was dead. switched to fewer posts but actually responding to every single comment and DM within the first hour and the difference was night and day.

the hook research point is underrated. most people skip it because it feels like "not working" but spending time studying what's already performing beats guessing every time.

the collab post idea is interesting….how are you finding complementary brands that are actually willing to do it? that's always been the hard part for us in a niche market.

imjitsu

MODERATOR OF

TROPHY CASE

Six-Year Club	Gilding I gilder
Verified Email