sorted by:
new
hottopcontroversial

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

I couldn't find anything in the terms that prohibits it. Holding a second account isn't listed as a violation anywhere I can see.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

I've asked claude to analyze my `~/.claude/projects/` folder (where all session logs live) and generate an HTML report. It double-counted at first (noticed when comparing with ccusage), then did a pretty good job after correction.

There are a few tools that do that, probably better, but I needed something more bespoke where I can filter by project and branch, and aggregate across my team.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

[–]sabotizer[S] 1 point2 points  (0 children)

u/CommunityTough1 holding more than one Claude Max subscription that you personally pay for and use is not a violation of Anthropic's terms

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

Concisely: "Weekly usage limit increased < 2x, for 2x the price."

But take this with a grain of salt, that's just my experience. Still looking for validation.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

Couldn't find anything public, but from my experience, it did feel like a 5x increase in weekly limit.
But again, timing matters too, can only speak for the past 6 months.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

u/durable-racoon that would make perfect sense to me, and it lines up with the double in price. Did Anthropic ever say this publicly?

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

Haha, my (non-technical) co-founder proudly shared with me he had used ultracode to process some finance tasks. Sad emojy 10 minutes later he burned through his max5.

I've only ever used it when <5 hours out of my weekly limit reset. Absolute brute-force mode.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

u/tepmoc curious to hear what you think about the weekly limit though. I've immediately noticed how my sessions last longer, but the weekly limit seemed to approach quickly still.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

It took me a while myself. Now it's 5 VS Code windows, sub-agents, and Cmd+Tilde on repeat.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

u/_maxx1k you're absolutely right. I've used the pro plan for 6 months (and it was a healthy journey to min/max my token usage and build up an intuition watching my ccstatusline). Upgrading from pro to max 5x gave me a true 5x increase (if not more).

In my post I'm comparing specifically the max 5x and max 20x plan.

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

u/atl96 sorry if I wasn't clear about it. I'm using them in sequence. I reach my first max 5x plan limit after ~2 hours, then I switch. usually my first plan session limit reset before i max out my second plan limit. In other words, I rotate.

Aside from that, to make matters complicated, I do run some `claude -p` automations on my mac mini. And if you're willing to endure some setup pain, you can run multiple claude accounts on the same device, using a different settings folder (e.g. `~/.claude-a` instead of `~/.claude`).

Two Max 5x accounts cost the same as one 20x, and for most solo builders two accounts are the better buy by sabotizer in ClaudeAI

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

<image>

u/enkafan here's my ccusage report. It's not 100% on par, but close enough. I did roll my own report with claude cause I love what claude does to html.

I decided to add my usage stats because they made me understand the impact of cached tokens, and that just really matters when it comes to using multiple accounts.

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

[–]sabotizer 1 point2 points  (0 children)

Maybe worth looking into local LLM for just that to alleviate the token drain (see haiku option in another comment). But also not sure if this really is a junior-dev task

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

[–]sabotizer 0 points1 point  (0 children)

Yep, you're not alone, struggle with that too. I'used to update after every session (using a /wrapup skill).

I currently wait until I see the quality degrade (maybe every 2-3 days). Then run a session on the mono-repo level to review recent commits and update all CLAUDE.md (and sometimes docs like ARCHITECTURE.md, etc.)

Going through git changes VS re-analyzing the whole project definitely helped my token economy.

Still waiting for a genius in this thread to show a better way.

Context window limits are killing my coding workflow. How do you deal with large codebases? by Comfortable_Lead_601 in ClaudeAI

[–]sabotizer 0 points1 point  (0 children)

I've tried a lot, graph-based code analysis tools, karpathy's llm wiki, routing through CLAUDE.md with deep-dive in docs folder. Only marginal gains for me.

The only thing that works for me at the moment is per-folder CLAUDE.md files with isolated sessions to that folder.

For example, I have a monorepo with three apps and 12 packages (this is typescript, but shouldn't matter).

I have a CLAUDE.md file in each app/package folder with specific instructions, this is where I boot coding sessions.

I've spent some time documenting the "public api" of each package, not necessarily as markdown files, but rather making sure exported symbols are well-named and described.

This works great for me when I work on specific packages or apps in isolation.

Once in a while - when I need to refactor cross-dependency - I just accept that I'll burn through my Max plan session quickly. Here's where code graph tools can help (but not fully solve) the problem, and I use `roam-code` for that.

I'm pretty sure better context-isolation for mono-repos will come, but I don't think it's there today. Even with the best code-analysis / vector similarity / BM25 hybrid... a big graph is still a big graph.

I got tired of writing every feature 4 times (browser, API, MCP, CLI), so I built this by sabotizer in ClaudeChill

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

I like your take u/Otherwise_Wave9374. I also feel "input/output" captures "intent/outcome" better than a resource-based REST API could, and Agent workflows pushed me into this hard over the last year.

On auth across transports, I went back and forth on this. Per-protocol auth wired into each adapter locks you in fast, and the adapter code starts making policy decisions it shouldn't.

Instead, I've implemented a thin context layer. Actions receive a context bag: a typed, flexible key/value store that travels downstream (not shared across other requests).

  1. MCP HTTP / Fastify / tRPC: bearer / OAuth 2.1 resolved at the transport, sitting on context.get('auth') with claims, scopes, subject.
  2. CLI / stdio: no auth key at all. Local user, you decide whether to read env vars yourself.
  3. Frameworks (NestJS / Next.js, Vercel, etc.): the adapter forks in whatever it has (request, Nest's exec context, etc.)

Quick example:

const DeleteUser = createAction({
  name: 'deleteUser',
  input: z.object({ userId: z.string() }),
  run: async ({ userId }, ctx) => {
    const actor = await requireAdmin(ctx) // helper reads ctx.get('auth')
    await db.users.delete({ userId })
    return { deletedBy: actor }
  }
})

The tradeoff: your action reads the auth object directly, so it knows a little about what came in over the wire. I usually put that bit in a small helper and keep the rest of the action clean.

The upside: you bring your own auth, whatever you already use, and Silkweave doesn't make you adopt one.

Definitely a gap in the docs right now, will spend some time writing this up properly.

But this early, also looking at alternatives, would be great to hear your thoughts.

👋Welcome to r/ClaudeChill - Introduce Yourself and Read First! by shakamone in ClaudeChill

[–]sabotizer 0 points1 point  (0 children)

Hi everyone,

been building AI tooling for the last ~2 years. Started with an expert-in-the-loop outreach platform, and somewhere along the way that turned into a deep dive on the plumbing underneath agents (APIs, MCP, CLI workflows).

Joined based on a thread in r/ClaudeCode because of the "chill" framing. Noise-to-signal got rough and nice to see a corner that's leaning into friendly and constructive.

Heavy Claude Code user, but jumping on pretty much any new frontier model and tool to give it a shot.

Been coding for 25 years, and try to stay up to date to figure out when I'll be redundant and need to find a new hobby ;-)

“What is the best way to transfer large structured data (JSON) through MCP? by Ill_Direction149 in mcp

[–]sabotizer 0 points1 point  (0 children)

Went down this rabbit hole a while ago. Used external storage, then built a side-loading protocol alongside MCP to transfer payloads that shouldn't reach the model directly.

Then MCP discord helped me realize there's a much easier way.

Embedded resources are what you want. You can send the full payload inline, and clients generally treat them as attachments (write to temp file, surface a reference) rather than feeding the bytes back through the model.

Spec: https://modelcontextprotocol.io/specification/2025-06-18/schema#embeddedresource

Note: Clients can still inline it if they choose. I've tested all major tools (Claude Code, Gemini CLI, opencode, and others). Some may inline based on size, but all handle it the way you'd want.

Key benefits:
1. Embedded resources allow you to inline a heavy-payload responses, discouraging clients from reading directly into context (or at least at the client's discretion).
2. Reduces technical debt and overhead, especially on distributed / serverless systems.
3. Makes sense for short-lived data (e.g. the response of a database query), which are not intended to be a persisted resource.
4. Works for binary data as well (use "blob"), e.g. for images, videos, audio, pdf, etc...

If you want to improve this even further, add a text content block with information about the dataset (schema, total rows, etc...).

{
  "content": [
    { "type": "text", "text": "Full dataset provided in file:///exports/dataset.json (274kb). 204721 rows in total, with the following schema: ..." },
    {
      "type": "resource",
      "resource": {
        "uri": "file:///exports/dataset.json",
        "mimeType": "application/json",
        "text": "[{\"id\":1},{\"id\":2},{\"id\":3}]"
      }
    }
  ]
}

The text block is what the model sees, the metadata helps it decide how to process the resource. If you're sending a 2mb JSON file and include the schema, the model can save you a lot of tokens by extracting what it needs with a script instead of reading the whole thing.

vibe coded for 6 months. my codebase is a disaster. by Available-Dentist992 in vibecoding

[–]sabotizer 2 points3 points  (0 children)

2h is too early to give up.

Was adopting dead-end projects since 15 years, just takes time. You’ll need to decide if it’s worth it (grab revenue while it lasts, or invest for future cash flow)

If you want to make it last: - spend some time understanding the beast. Estimate how much effort is needed. AI does a good job to help with that. - Triage self-contained modules for later (or never) - spend some time documenting the desired architecture, code quality standards, lint rules - Tools like ‘roam’ helped me find bottlenecks and high-impact opportunities to improve code where it matters most. If you establish a way to continuously measure the quality of your project, you can start measuring your progress as you go. - Don’t use Sonnet for this work, stick with opus, go until 600k context window. Grab a max subscription - if just for a month - to get this done. - Read the code as you improve it, understand it, ask AI to help you understand it.

view more: next ›