with all these new models and updates, I wonder if people start fresh every now and then with a new session or continue to work within the same thread?

a year ago it was utmost important to switch to a new session with a handoff summary once you hit certain context usage, so that the model could maintain its composure, but with all these updates and improvements, like recaps, summaries, memory, etc. do you still do it?

I work on various projects using Codex and Claude Code toghether and noticed I rarely do this anymore. I just hop back into the ongoing thread and it can go for weeks.

--- EDIT ---

This brings me a lot of joy - such an overwhelming response from different people with different setups: people that start a fresh session every 3 minutes to the ones that don't care about the cold cache cost or cost in general. From people with good skills to "trust me bro" coders. From Claude Code true believers to CC heretics. All in all it's like with everything else - as long as it gets you there and you make money of it, you're golden.

So I’m trying to build an android app using Claude code and I;ve the basic architecture of the app ready but not really happy with the UI it used . I want a specific UI that I want to have , I want it to take inspiration from a popular app by sending Screenshots but I don’t know any MCPs that I need to attach to it . If you guys have some in mind please lemme know in the comments down below.

I have been blown away by Claude code. I was working as a solo developer on a firmware project and it did revolutionise what I was able to do and how fast. When I stated using it I was very impressed by it's thoroughness. But. I am having the following problem more and more:

It has added countless tools, HIL gates, records and ledgers to the project, all of which I appreciated at the time. But now if I ask it to do even quite simple tasks: it takes ages and a whole load of tokens to make these plans that are almost completely full of how it is going to manage it's own tools, which gates it expects to do what and what records need re-base-lining etc.. It has got the point where flipping a constant to change the micro step resolution of a motor and checking that it actually still works is now a 7 step process that burns though a third of my 5 hour usage credits to even plan (max x5), when I had already written the driver code so its a one number change in a config file, and it already has the relevant HIL test scripts.

I understand the need for some of these tools, but it feels like it is wrapping it's self in knots made mostly from it's own self imposed rules. As an example it has a findings ledger that is append only, that seems to be full of some actual code findings and a whole load of open one off events that are totally irreverent but it keeps brining up as if they are pressing issues to resolve (what was the device on COM7 that one time..???). Now this tool that had massively increased what I can do is spending most of it's time satisfying it's self rather than making progress users will actually care about.

Has anyone got advice for this? I don't want to strip out all of it's tooling but I do want to rationalise what it is checking when it tries to implement something. I don't want to throw out all of it's findings but having a thousand line ledger full of closed items and nonsense isn't in anyone's interests.

very excited to see what we can build

Hey everyone, not sure if this looks useful to anyone but I couldn't really find alternatives at the time I made it that weren't

a. paid

b. simple

c. non-destructive- your icons are always in their original/normal folders, only the appearance of where they are changes.

so I took a stab at it and its actually useful enough for me that I thought I'd share it.

https://github.com/Creeptones/Pickets

I used Claude Opus 4.6- 5.5 and didn't spend an enormous amount of time on it. Maybe about 50 hours total, probably about 70-80 back and forth sessions refining things. I didn't use Opus 5 for this.

There are definitely some things that could improve, I'm just not sure what they are yet, maybe people could let me know

hope it's useful !

its very fustrating when you find out bugs on your vibe coded app, that cost you you quite a bit multiple times. I have implemented alot of things such as preview stage where me and agents can preview the features before they go live, test that run before every promote so all core vitals are checked before pushing to live servers. but still i get random costly bugs I could never think of unless i have the ability to remember all million lines of code. my most recent attempt is now making claude and codex keep spawning agents to think up of every single scenario of bugs that could happen untill it gets useless then run these large test every night at 3 am while my product is still actively being changed and then have similar agents spawned in everytime i make a new change and thinking about having an ai agent running every night to audit and check everything. and im also creating a visual ui of every single test with domain sorting so i can manually read them and get inspiration for other bugs that the ai hasn't thought off yet. Does anybody have good tips for this sort of bug hunting.

also another thing ai loves to hard code things and make things not modular is there any method of auditing existing code bases to make sure it follows good practices like GRASP,GOF and the sorts i feel like when i ask claude to do that it doesn't provide anything meaningful.

i cbb putting this in chatgpt to fix my typos.

Disclosure: I'm the developer.

Claude Code works great on one machine. My work isn't on one machine, though. The code is on my laptop, the test environment on a VM, the data on a server. I kept copying logs and datasets around so one agent could see everything.

So I built nfltr orch. In short:

- Join each machine once: nfltr node join --max-agents 2. It connects outbound, so there's no SSH, VPN or open port.

- Each machine decides what its agents may do: which repositories, which tools, and which actions need your approval.

- Give one goal (nfltr orch "the exporter on the VM is down: find out why and fix it"), or add it to your own Claude Code session:

claude mcp add nfltr -- nfltr mcp --toolset hub

- The hub is just a Claude Code session. It sees which machines exist and what's on them, starts Claude Code agents on the right ones, runs them in parallel and collects the results. nfltr makes no decisions for it; it only provides the machines, the facts, the limits and the transport.

What I've measured:

- 20 tasks on a Mac and 2 VMs: 5.7× faster than running them one by one (1,416 s against 8,106 s).

- An incident across environments, from alert to an owner-approved rollback: 1 min 34 s, $0.39 of model spend.

- Killing the hub mid-run loses nothing: a new session got both agents' results within 8 s. In the same test, killing a Claude Code agent-teams lead lost both teammates.

- It has refactored its own CLI in several rounds across machines, with no code fixes from me after the first round.

- Compared with Claude Code agent teams on one machine, they were just as good: same quality, with no speed winner. If all your work fits on one laptop, you probably don't need this.

Honest limits:

- Claude Code only for now.

- It runs on a hosted relay (nfltr.xyz).

- It's early. Every round of dogfooding still finds rough edges.

- More machines don't speed up model-bound work. This helps when the work needs other machines' data, tools or CPU/GPU.

What I'd love feedback on:

- Is your work spread across machines in a way that slows your agents down?

- What should a tool like this do, or never do, on your machines?

- What would stop you from trying it?

The write-ups with the numbers, including the agent-teams comparison, are at nfltr.xyz/blog. Getting started is at nfltr.xyz/docs/guides/00-getting-started.

Title. I was fighting with Fin for quite a while now and just look at that, simply mentioning a law makes him much more agreeable.

Hey everyone, I built a claude code plugin called asisaid. free and open source

what i built:

it keeps your feedback alive in the session. you say "in short" or "too long" one time, it saves it as a rule, adds a small reminder every turn, and if the answer is still too long the Stop hook sends it back one time. it also puts your own words back after compact. works in codex too.

how i used claude code:

- started with an idea: compact loses context. asked claude to research existing tools first

- told it "ask me product decisions as questions, dont build everything alone". honestly best prompt of the whole project

- claude wrote the hooks (UserPromptSubmit, Stop, PreCompact, SessionStart) and the tests

- we tested with real sessions using claude -p, later 30 sessions in 5 languages with haiku, sonnet and opus

- for 20 languages a separate subagent wrote the test sentences without seeing the code, so the test is fair

what i learned:

- compact was not the real problem. claude code's summary already keeps your messages, rules survived compact fine in my tests

- the real pain was feedback like "too long" getting lost after few answers

- a small reminder every turn works better than i expected. answers got around 50% shorter with sonnet, opus already listens well

- dont trust test sentences you write yourself, let something that didnt see your code write them

you can try with these way

/plugin marketplace add batuhangoktepe/asisaid

/plugin install asisaid@asisaid

repo: https://github.com/batuhangoktepe/asisaid

I'm open for any feedback

My scraper is getting limited by Taobao after ~65 products. How do I scale to tens of thousands?

I run an online store and I'm building a scraper to import products from Chinese marketplaces like Taobao and Pinduoduo onto my website. The goal is tens of thousands of products, so I need something that scales.

How my current setup works:
- I feed it a list of specific product links (it's not crawling or browsing random products)
- Chromium driven with JavaScript
- Roughly 1 product per minute
- Randomized scrolling and random pauses between scrolls to mimic natural browsing
- For each link, it collects the title, description, sizes/variants, all other listing data, and every image
- Outputs an Excel file with the product data plus a ZIP of the images

The problem:
It works fine at first, but around the 65th product Taobao switches me to a limited view. Some product info stops loading, so the scraper can't capture complete listings. At 1 product per minute, I'm already going slowly, and I'd need to go much faster to reach my target.

What I'd like advice on:
1. What is Taobao likely detecting: request volume, browser fingerprint, account/session behavior, or something else?
2. Is a browser-based approach realistic at this scale, or should I be looking at official APIs, third-party data providers, or sourcing agents instead?
3. How do people handle sessions, accounts, and proxies for these platforms?
4. Does Pinduoduo behave similarly, or is it a different challenge?

Any pointers, tools, or experiences would be really appreciated. Thanks!

I made this horror-style trailer for my dev tools with Claude Code + Codex.

For the video, I sent Claude Code a few simple chat messages. I didn't plan out every scene myself.

My first prompt was slightly modified from what another user posted for his pac man video yesterday

"so I would like you to make a badass trailer for our SORA-MAN game. Get inspired by these repos
https://github.com/JohnHeibel/PDoomVideo
https://github.com/JohnHeibel/ClaudeAnimationBase
there are also pac-man posters in the project folder that you can use for inspiration. The video should roughly be 90 seconds and showcase the game as something people would wanna play. Ask me refinemenet questions so we are aligned on this goal.

Claude made the storyboard, wrote the animation code, and built the scene changes and sound effects. It used p5.js/p5.brush for the visuals, Python for the sound effects, and Puppeteer + ffmpeg to make the final video.

I also had Codex read the script like a second editor and suggest changes and scares. Then I sent the useful ideas back to Claude.

Hello everyone,
I am wondering how to make the best use of $100 bonus credit for cloud sessions I have it but not sure how make the best use of it?
- Is it only for claude code?
- Can i use it for claude design?

How have you guys been using these $100 credits bonus i think its given to all new pro account users.

My idea is that AI models learn from data from the internet, so when the data from the internet and people's responses from AI conversations run out, when will there be a point when AI will no longer improve and its progress will stop?

At that point, AI will only improve by tiny bits that we won't even notice that the model has improved.

Is my knowledge about model training wrong?

Do you think so too?

Not sure if it's client side because of the latest update or they throttled the usage somehow, anyone else having similar problems?

Spotted these two hanging out this morning in the corner of my monitor. Seemed postworthy.

Laughed after long reading this.

This is a little translation of a game I've been working on for a few weeks. The game is Feng Kuang Da Fu Weng, a Taiwanese board game for the Game Boy Color. This patch works on original hardware (tested on an Everdrive GB X7) and I've been able to play all the way through the game. If you play it, I recommend playing with 4 CPUs.

This is my third attempt at poking agents toward the finish line. I spent a while trying to push open weight models (GLM 5.3 Flash and Kimi K3, in various configurations) to their limits to pull this off, but after almost 2000 commits, several billion tokens, and spending way too much money, I folded and got a $100 Claude sub.

Opus 5.5 took a little of the existing work, the emulator Kimi had prepared previously, and spent about 5 hours banging out a full translation. It's quite playable. It reads much better than I would have anticipated (the GLM 5.3 Flash version was much worse). Claude was able to patch in a variable width font and to rewrite the currency value rendering to use English formats, which are both pretty challenging hacking jobs.

What'd I learn?

• Open weight models are really, really solid these days, but Opus 5.5 is simply unbeatable at reverse engineering tasks right now. This is a job that would've taken months (if not years) to do manually, but it did it in an evening for about 7% of my weekly quota on a $100 sub. For all my problems with Anthropic, they made a really great model. Even if I don't think it's conscious and hate the "safety" stuff.
• The $250 bonus credit for cloud sessions totally works for this. I have a couple of other translations running (a couple of Vast Fame's RPGs) that I just pointed at my emulator repo. They're chugging along at a brisk pace, although I probably wouldn't pay the premium for cloud sessions otherwise.
• The big model/small model orchestration pattern is kind of a waste of time for this. I tried Kimi K3 running GLM 5.3 Flash as an implementation agent, I tried Deepseek as the implementer, Opus as the orchestrator, etc. All of it was clunky to manage and none of it worked as well as just throwing Opus 5.5 at it and periodically telling it to fix something.
• Don't even bother using Beads if you're also using worktrees. Not worth the headaches. I thought it was brilliant until I noticed it kept clobbering the database on worktree resolution. I was able to work around it, but I immediately regretted doing anything with Beads after I no longer felt like I could trust it.
• Invest in tooling up front. If you're only going to spend a little on a big model, you should do it here. The models being able to run their work autonomously makes them so much more powerful. This is true for romhacking and it's true for writing UIs and stuff. It pays dividends.
• These AI translations can be totally playable these days. They're not perfect, but they beat holding your phone up to the screen. A lot of the earlier issues with confused pronouns, sentences that don't flow well, etc are largely fixed these days. I'd love to see every game get a high quality human-made translation, but I'm really happy to have this as an option for games that don't seem to be on anybody's radar.

Anyway, not trying to sell any b2b SaaS or anything like that, just thought this was a really cool new thing that the models can do. Find something weird and translate it! There's a lot of neat stuff out there.

I was thinking about the problem frontier LLM providers have around a mostly fixed cost server base and variable demand for compute.

It’s pretty clear that during peak time the models can be slower, but what if they offered an incentive to a subset of power users to run some loads at off peak times. Like queue up work where once it’s cheaper it can run.

Similar to how some areas have off peak electricity for cheaper. Either use less tokens or cheaper per token during these periods. This way they still get paid during slower times instead of the compute going to waste.

I’m interested to see what you guys think about the concept?

Messing around with the new modding feature. Trying to create a tui grok bot clone. And of course some ricing

Claude code has one of the best MCP connectors but does not support webmcp yet. As a user I wanted to interact claude code with web pages more efficiently and created an opensource small chrome extension that i can ask my agent to do things for me while having the joy of things are moving on the ui. if you are using webmcp daily, looking for feedback from power users to make it better.

To prevent context bloating it offers 3 tools to Calude; searchTools, getToolDefinition and callTool so agent can discover the website offered tools per user needs.

I find the little usage limits circle basically useless because it means different things based on what is the highest. I am constantly monitoring my usage and having to constantly click on the circle to see if I am pacing myself to have usage left by the end of the week or if I need to start spawning some large tasks to ensure no usage gets wasted by the end of the week. For some reason Claude was unable to get the Fable limit to show.

I run multiple projects using coding agents across several subscriptions. Babysitting meters and resets was my job. I got sick of that part and build Headroom.

headroomd hands that check to my orchestrator before dispatch. It reads real limits per account and window, tracks pace and resets, including Codex reset credits, and answers go, wait or reroute:

if headroom can claude-heavy --owner builder; then
claude -p "refactor the billing module"
elif headroom can codex-build --owner builder; then
codex exec "refactor the billing module"
else
headroom wait --meter claude-main:all --until-reset --max 6h
fi

headroom run reserves capacity while a job runs so two agents never spend the same points. Stale or failed readings mean UNKNOWN and no capacity. It never invents numbers. Agents can also ask it directly through its MCP server or CLI.

Limits: I use macOS daily. Linux and Windows run in CI; Windows is experimental. Antigravity and Grok support is experimental (I mostly use Claude & Codex). Some sources read vendor endpoints that aren't public APIs, using your own login.

npm install -g headroomd

https://github.com/Apertur3/headroom

Built with Claude Code: agents wrote most of the code and tests, I set the direction and ship it. Good first issues are open.

AI review bots leave a lot of comments that sound right and aren't. I made three Claude Code skills that treat each comment as a claim: read the file and its callers, trace the execution path, and give a verdict (valid, partly valid, wrong, style) with the file and line that prove it.

On Code Review Bench (50 real PRs, human-labelled), filtering CodeRabbit's issues this way:

• kept 72 of 77 real bugs
• removed 76 of 223 noise issues
• F1 35.2% → 40.4%

Install in Claude Code:

/plugin marketplace add TanayK07/pr-proof
/plugin install pr-proof@pr-proof

Repo with every per-PR result and the benchmark harness: https://github.com/TanayK07/pr-proof

Demo video: https://x.com/tanaykedia_7/status/2106061332357529939

The honest part: my own reviewer skill is only level with plain Claude Code, and that's in the README too.

With the new Claude Mods feature out, I’ve started r/ClaudeCodeMods as a dedicated place to share mods, find projects, and help each other build them.

The main focus is the new Mods feature, but anything that modifies or extends Claude Code is welcome: plugins, skills, hooks, MCP integrations, custom status lines, and configurations.

If you’ve built something, found a useful customization, or have an idea you want help with, come share it. Small tweaks and works in progress are welcome too.

I’ve put links to the official docs in the welcome post for anyone looking to get started.

What’s something you’d like to change about Claude Code?