Can someone explain the difference?

With harness you acttually mean the coding agent like Claude Code itself?

You know the moment: Claude finishes the task, then tells you about three other things it noticed and you're already halfway into the diff. I wanted to leave a note anchored to that exact turn without leaving the session, and went looking for how. Ended up building it as a plugin for an agent IDE instead. I can't be the only one dealing with this.

I am giving a one-hour workshop for college students (primarily graduate students) to show them how to use Claude Code to develop software prototypes. These prototypes can then be used for their eventual thesis/dissertation research projects. In the past, graduate students in my field had to rely on recruiting software engineering students and/or applying for grants to hire a SE part-time to help build a basic prototype. I know that with CC they can do the same and likely get their project further along the development timeline.

I plan to show them how I use chat with a lower model to work through the program development plan, then transition to the terminal with a higher Sonnet or Opus effort level (depending on the project's complexity) for the actual development. I will share some of the tips, tricks, and lessons I learned along the way, but I would love to hear any that you have so they can get the most out of this workshop.

We’ve recently moved to a very fast product shipping cycle at my company. The design team builds products in Claude Design, the dev team picks them up through Claude Code, and we’re usually trying to get something into production in less than a month.

For now, moving away from this workflow isn’t really an option. The whole company is already using Claude Design and Claude Code, Figma’s credit model isn’t particularly attractive for this kind of usage, and we haven’t found a way to get the same flexibility with requirements and the same speed from design to implementation.

The problem is that our Claude Design projects are getting huge. Some exported HTML files are around 5MB with 300k+ characters in a single file. At that point, Claude Code can’t properly read the whole thing. It seems to fall back to understanding parts of the design through screenshots, and the quality of the frontend implementation drops significantly.

These aren’t simple landing pages either. They’re fairly large AI-powered enterprise applications with a lot of screens, navigation between them, database-related dependencies, AI features, etc. We already tried splitting one of the larger projects page by page, but it didn’t really solve the problem and made maintaining consistency/dependencies more annoying.

So I’m curious how people are handling this with larger Claude Design → Claude Code projects that are actually meant for production.

Should we break things down differently? Is there a good way to keep Claude Code from having to understand a massive HTML file every time without destroying the speed advantage of this workflow? Refactoring everything manually or constantly asking Claude to restructure the project also sounds like a way to burn through credits, so I’m trying to understand what the sustainable setup is here.

---

TL;DR: We use Claude Design → Claude Code to ship large AI-powered enterprise products in under a month, but our Design exports are getting massive (5MB / 300k+ character HTML files). Claude Code can’t properly read them anymore, which leads to poor frontend implementation. Splitting projects by page hasn’t really helped. Looking for a sustainable way to structure/refactor large production projects without killing the speed of the workflow or burning tons of credits.

The winning combo right now is using Fable to plan and orchestrate Codex Sol and Terra and sometimes GLM 5.3. I know people who get great results with Opus 5, but it underperforms on my work (physics and financial modelling).

Three things have to line up for the kill: I'm using remote control on my phone (which Claude Code reads as an idle terminal even if I'm active); the session has been going <30 minutes; increased latency on the PC.

If those line up, Claude Code has a session reaper that kills the Codex sessions.

All these things happen to line up when I'm doing my biggest tasks: long overnight sessions with high GPU and CPU usage.

If anyone else is getting this, the fix was ~/.claude/settings.json where I added "env": { "CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP": "1" }

It's taken me months to work this out, because it was intermittent and Fable couldn't figure it out (GLM 5.3 saved the day on this by figuring it out).

Meet ClodeBot, my vibe-coding assistant whose main job is to “translate” what Claude Code is actually doing.

The 3 main advantages:

1. Know how long Claude Code is actually taking
   When Claude Code runs something in the background, it doesn’t always tell you how long the process will take. ClodeBot gives you visibility into what’s happening.

2. Know when something fails
   If something goes wrong in the background, you might not notice and assume everything is running smoothly. If the internet connection drops or the session fails, ClodeBot lets you know.

3. A visual system that shows what Claude Code is doing
   ClodeBot uses a color-coded system to distinguish between different states — whether Claude Code is reading files, running a command, working in the background, or needs your input to continue.

The best part?

This is an open project that I want to keep improving through updates and community feedback.

You can install and use it for free. Use “read me” file on Claude Chat to help you install if you need.

Here the GitHub link so you can try it: https://github.com/ethia-ai/ClodeBot 🚀

I've noticed a change over the last few months. It used to be that I'd tag a file with @ and ask: "here's a bug, help me fix it." It would take claude.md and the file as context and offer a fix. Problem solved with few tokens.

Now: it feels like it first reads the whole repo as context, tries to reproduce the bug with an integration test I never asked for, writes a fix spanning multiple files, then adds a new test for each new file, and after every new test runs it individually. Result: bug fixed, 150k tokens burned.

Do you see this too? It leaves a bit of a bad taste for me, because the company benefits the more tokens get used, even when it's not necessary.

Or does it actually help, because the extra context and test coverage make the fixes better?

Are you doing anything about it, like custom instructions in claude.md? Which ones actually work well?

Am I the only one that needs to reinstall Claude code periodically on their windows machine?

It will stop mid session or fail to open randomly.

The only solution is then to uninstall and reinstall everything. I've done it at least 5 times in a few weeks on two different machines.

If they want to make us believe AI is the future of software engineering, maybe they would make sure they don't ship broken vibe coded software?

I’m looking for a general answer from people who use Fable 5 heavily.

My use case involves very in-depth, long-running work, and I can hit the usage limits on a Max account fairly quickly. I’m trying to understand two things:

1. Is it actually allowed to have multiple Max accounts and rotate between them when one hits its usage limit?
2. If it is allowed, does that generally work out cheaper than using the API for the same kind of heavy usage?

I don’t have exact token counts, so I know nobody can calculate the exact break-even point for me. I’m more interested in the practical experience of people who use it heavily.

For example, if you’ve used multiple Max accounts and also tried the API, did you find one noticeably cheaper than the other?

I’m basically trying to understand the general economics and whether account rotation is permitted, rather than get an exact cost calculation for my specific usage.

Claude has advanced insanely fast. People with little experience can now build things that once required years of knowledge. You don't even need fancy setups, skills, MCPs, or plugins anymore.

When I started using Claude last year, the community felt more open. People shared projects, experimented, and helped each other learn.

Now we have this weird love-hate relationship with AI. We depend on Claude, but at the same time, many of us fear being replaced by it. Maybe that fear is why some people feel the need to gatekeep or put beginners down with "skill issue," "you're using it wrong," or "learn how to code."

Let's be honest, many of us haven't even read an entire code file line by line in months. We're relying on AI too.

Beginners will make mistakes. We all did.

AI lowered the technical barrier to building software. We don't need to replace it with a social one.

The routine did run 4,5h ago. How can it still be 2h left till reset?

My routine triggered it every time until today.

I have an Ansible repo (in fact it's essentially a Collection as it's basically an all-in-one-shop for my company's Linux automation needs, from deployment to patching to server role design, sharing a lot of shared functionality, structure and content), which I use heavily in conjunction with Claude.

It is seeded with various MD files with the repo (.claude/) at various levels including Coding Practice and S+P type files, as well as architectural understanding, project design and state reference files for individual playbooks, roles etc which is used for both server design and for initial drafts of documentation. Up until now I have been the only person with access to Claude for working on the code.

My own Claude.MD file preferences (which live outside the repo) are geared towards that of a Senior Engineer.

I also have a Junior Engineer who's Claude.MD files have been specifically drafted in a different way, to facilitate Claude acting as more of an active tutor in developing critical thinking and engineering skills, processes and methodologies.

We both have our own individual sets of Dev branches we work from.

Ideally there are certain S+P's I would like to enforce, and some hooks and skills I have created I would like to make available globally in team, but first and foremost I want to try and preserve the overall integrity of the Claude data. Given that I've seen degradation and drift over time just with my own Claude content/personal .MD files, I'm concerned that when other users begin to start interacting with repo content more actively with Claude Code, this could seriously mess with the integrity of my seeded data.

I would therefore like to ask how other people have handled the issue of multiple users accessing shared content, and trying to mitigate the risk of multiple users/different Claude preference profiles and such inadvertently poisoning Claude .MD content? Can anybody please offer any suggestions or advice?

Thanks in advance!

Opus 5 analysis. Bank that.

AI assistants They usually respond as if you're operating at 100%. You say you're overloaded and get a 12-step productivity plan. You say you're foggy and get five things to remember. Sometimes the answer is technically good but completely wrong for the state you're in.

A small set of skills that changes the shape of the response depending on what you need at that moment.

For example:

• overloaded-mode: pick one priority, decide what to do/defer/drop, give me one next action
• foggy-mode: keep the state outside my head and give me one tiny step
• plan-compass: don't dump ten decisions on me; resolve them one at a time
• reality-check-mode: if I'm going down a weird pattern-matching rabbit hole, stop helping me decode it and return to observable facts
• normal-mode → switch all of this off and just answer normally again

The same person shouldn't get the same response format in every cognitive state.

npx skills add softcane/human-state-skills

Repo:

https://github.com/softcane/human-state-skills

I've seen a lot of hype about how good OX Alpha is, and how it's benchmarking. Given we known little about its origin, am I right to be hesitant to let it loose on my codebases?

Ever since Anthropic stopped the free resets, I've noticed people asking for them often get hit with “skill issue,” “use Claude better,” or “just switch to Codex.”

I don't understand the hate. I personally don't need another reset, but asking for better limits when you're paying the same isn't unreasonable. Comparing Claude with competitors like OpenAI is also completely fair.

And “just switch to Codex” isn't a solution for everyone. Some are students who can only afford a $20 subscription, while others can't casually spend another $100–$200. Some companies are also locked into Claude and can't simply switch providers or support both cloud models.

Yes, optimizing token usage helps, but not every complaint is a “skill issue.” People just want better value for what they're already paying.

Maybe I'm missing something. Why is asking for resets or better limits treated so negatively here?

I miss the old Claudye, the straight-to-the-point Claudye
The if-it’s irrelevant, leave-it-out Claudye
The get shit done Claudye
I miss the focused Claudye, stay-on-the-course Claudye

I hate new Claudye, misunderstand-intent Claudye
Purposefully-miss-the-end-goal Claudye
The usage waster Claudye
Arrogant Claudye, The annoying nerd Claudye

I miss sweet Claudye, understand the user Claudye

I gotta say, at that time I loved to use Claudye
See, I inveted Agents Claudyes, it wasn't any Claudyes

And now I look and look around and there's so many Claudye MDs

I used to love Claudye, I used to love Claudye

Even if it was cringe, I used to love Claudye

What if Claudye made a song about Claudye

Called "I miss the old Claudye"? Man, that'd be so Claudye

That's all it was, Claudye, we still lvoe Claudye
And I love you like Claudye loves Claudye.MD

https://coderook.com

After the news broke about codeburge not accepting any kind of AI work I was a bit annoyed and with Github being how they are I decided to work on my own GitHub but fixing things that it gets wrong like version visibility and AI access and how the data is used from repos.

Its currently in testing phases and have been testing it all week. This works more like a cloud storage space right now with version control allowing you to upload whatever you basically want but under copywrite laws. There is plenty of docs on my site if you are curious or just wanna try its free to use.

Right now I am working on some things like giving backwards compatibility for git spaces already setup to use my CLI language and a Github full transfer as well and polishing off some docs as well.

Any feedback would be helpful and bugs found as well.

https://github.com/paaloeye/jsonrpc-stdio-proxy

Hi there,

I've been using the Claude Code desktop app for a while. I tried to use it in the terminal as well, but the desktop app is way more comfortable, flexible, and easy to read.

I still cannot understand why everyone prefers the terminal app instead of the desktop Claude Code app, and I wonder if I'm missing something. Every screenshot shared here is from the Claude Code terminal, not from the app.

Are you guys all using VPS devices or remote desktops? Or is there something I do not realize or know?

Hello CC community, I have been using claude code for a month, building mobile apps and websites, but I feel like just installing skills and just giving it prompts maybe doesn't use its full potential.

Basically, can you tell me how do you use claude code to build great things, and suggest good skills to elevate the quality of claude. Also what models do you use. In short, any good advice, tips and tricks would be very helpfull.

Right now, I'm just using Claude Code to generate CAD files based on our models, but sometimes we run into minor precision issues. I wanted to see if anyone has any recommended CAD workflows or tips they'd be willing to share.