HN user

bazhand

43 karma

Marketing

Posts0
Comments30
View on HN
No posts found.
Claude Sonnet 5 22 days ago

It was something that was used for token efficiency. Most of the settings and use cases are quite poorly communicated but asking Claude to review the latest release changelog (https://github.com/anthropics/claude-code/blob/main/CHANGELO...) is quite useful. Combined with @"claude-code-guide (agent)" to read it's own docs for settings/configs is super helpful.

The quite useful tool is to use /opusplan along with /codex:rescue (https://github.com/openai/codex-plugin-cc) means you get quite a strongly reviewed plan using native claude + codex without having to implement the mostly useless trust-me-bro plugins and other bs.

Claude Sonnet 5 22 days ago

Have you tried '/model opusplan' I've had strong results mixing opus for planning with sonnet implementing.

I ran into this exact problem building a MCP server. 85 tools in experimental mode, ~17k tokens just for the tool manifest before any work starts.

The fix I (well Codex actually) landed on was toolset tiers (minimal/authoring/experimental) controlled by env var, plus phase-gating, now tools are registered but ~80% are "not connected" until you call _connect. The effective listed surface stays pretty small.

Lazy loading basically, not a new concept for people here.

FWIW this isn’t new, using a Claude/Max subscription auth token as a general-purpose “API key” has been known (and blocked) for ages. OpenCode basically had to impersonate the official Claude Code client to make that work, and it always felt like a loophole that would get patched eventually.

This is exactly why (when OpenCode and Charm/Crush started diverging) Charm chose not to support “use your Claude subscription” auth and went in a different direction (BYOK / multi-provider / etc). They didn’t want to build a product on top of a fragile, unofficial auth path.

And I think there’s a privacy/policy reason tightening this now too: the recent Claude Code update (2.1-ish) pops a “Help improve Claude” prompt in the terminal. If you turn that ON, retention jumps from 30 days to up to 5 years for new/resumed chats/coding sessions (and data can be used for model improvement). If you keep it OFF, you stay on the default 30-day retention. You can also delete data anytime in settings. That consent + retention toggle is hard to enforce cleanly if you’re not in an official client flow, so it makes sense they’re drawing a harder line.

Letta Code 7 months ago

How does the memory scale (or not!) over time. If using Letta in a single agent mode, similar to just using claude - how does memory blocks stay relevant and contextual?

I guess what I'm asking is, if there is a memory block limit, is that an issue for self learning over time. Claude as you know just straight up ignores CLAUDE.md and doesnt self-improve it.

I like this approach, and it's very similar to what I'm currently using - albeit my use case is to get Claude to automatically invoke the relevant subagents during both planning and build stages.

Subagents using MCP would solve quite a lot of the context preparation required for a successful session. I'm using GLM-4.6 vision/web search MCP in claude code to relative success as the subagents can access these via API (not true MCP behaviour but close enough)

    Add these settings to your `.claude/settings.json`:

     ```json
     {
       "env": {
         "ANTHROPIC_CUSTOM_HEADERS": {"anthropic-beta":
     "context-1m-2025-08-07"},
         "ANTHROPIC_MODEL": "claude-sonnet-4-20250514",
         "CLAUDE_CODE_MAX_OUTPUT_TOKENS": 8192
       }
     }
     ```

Having used Claude daily for last year or so, I don't feel great about being pushed into quite expensive tiers of 5-20x cost. I already feel like I'm hitting the Pro limit 2x/day more often than recently, although no data to support this - but the feeling is there.

Mostly I'm disappointed that the higher tiers are just usage tiers rather than features.

If I understand correctly:

- you run advertising and lead gen on behalf of clients using their CRM (their domain email/outreach)

- and require Stripe for attribution, and to remit payment from client to you

That's most likely triggering Stripe's TOS.

For something so core to your business, did you have a discussion with Stripe if this was allowed?

I joined Proxify (on the list) recently and was pleasantly surprised to find a quite vibrant tech scene. As someone who followed the more traditional startup hubs like Amsterdam, Berlin or Dublin, I've found that there are many gems in the Nordics.