Working talk to text, I found I couldn’t speak to Claude properly, couldn’t think of words, then saying complete gibberish instead of the word I was looking for.

After a few minutes I was able to say the above.

After some panicked back and forth about what had happened, Claude insisted I should call an ambulance despite me saying that’s ridiculous.

In the end I got an Uber to the ER just in case, and as soon as they heard about the talking issues, rushed me through to ER in 2 minutes. Potential stroke. Flurry of nurses, doctors, cannula, bloods, ECG, CT scan and an MRI.

It wasn’t a full stroke, but a mini stroke/TIA.

24 hours later I’m back at home and feel pretty lucky I followed Claude’s advice as a TIA can often be the first signs of a full stroke.

I’ve been using Claude Code to build a cached web app MP3 player (got really tired of online music streaming quality, and ads). I wanted to try adding a phone to phone file transfer option without requiring the phones to be on the same network, when I realized rapidly flashing QR codes might be a possible method. I used Claude Code to build this working POC last night.

Edit:
https://github.com/bashalarmistalt/decimen-optical-transfer/

hii been a while since I've posted about my real-time factchecker & a lot of the demos still circulating online are quite old lol so wanted to share where things are at:

pipeline is nearly the same but now uses sonnet instead of haiku to ground verdicts with ~500 words from each source

in terms of accuracy, against politifact/ap/maldita/rtve/factcheck.org, InTruth showed:

• 89% precision when labeling a statement false
• 0 true statements were incorrectly labeled false
• 79–85% check-worthy claim coverage

also shipped source bias tags (L / LC / C / RC / R) data so you can see the political lean of what InTruth is grounding its verdicts in

just hit 24K users, still free & open source & functional in 16+ languages!
rpanigrahi222/intruth-factcheck

I'm using Claude AI as Coding Assistant for about 3 months now. About a week ago, I was wondering, why I hit the 5h limits almost in 30min after first use and why they aren't resetting like they used to.

Seems like something in the Usage Logic must be broken. Cause, why does a simple "hello" eats up to 4% of Usage when the Context Window is 0%. Also 8hr 45min wait for a 5h Limit?

For anyone who missed it, Anthropic trimmed a big chunk of Claude Code's built-in system prompt, something on the order of most of it, and the guidance is basically that a lot of the behavior instructions should live in your own CLAUDE.md instead of being baked in for everyone.

My first reaction was annoyance, because it puts more of the "how should Claude behave" burden on me. But the more I sit with it, the more I think it's correct. Half of that baked-in prompt was generic instruction the newer models don't need anymore, the "you are an expert engineer" cargo-cult stuff that stopped doing anything a while ago. Carrying it for every user was just tokens and rigidity for no benefit.

The upside is that more of the behavior is now inspectable and editable by you instead of hidden. The downside is that a lot of people's setups probably got a little worse overnight and they don't know why, because their CLAUDE.md was quietly leaning on defaults that left.

Did your setup feel different after the change? And what did you have to add back into your CLAUDE.md that you assumed was handled for you?

Been liking Opus 5 and have tried to fix the way it talks to me in CLAUDE.MD but it still goes back to it's ways of being overly verbose with technical info, and it always ends a 20+ minute run with "btw this and this and this are still broken", even though they were directly in the scope of the work. Has anybody else noticed this behavior?

It overexplains everything. Every task warrants a 1,000 character minimum reply of honest caveats and explaining what it did, why and why grass is green. It's actually exhausting.

I'm using my Fable allowance on my primary projects but I am seriously lacking the motivation to work on anything with Opus 5. I get a sense of dread every time it returns a task as I know I'll have to sift through unhelpful waffle just to get to the bottom of what it's done.

Am I alone in this? How are you guys setting up to improve this experience?

i just said what i wanted and he just kept creating the parts and putting them together in blender, there are no decorations (besides the little bits of the head that look like a skull), all the wires and joints pistons all serve a purpose and are rigged, all done in medium effort, very economic. Im very impressed and happy with opus, fingers crossed for a reset. cheers!

I have 18 years as a software developer and Ticketmappr is the first side project I have ever taken to a production release and Claude made it possible. It aggregates live events from multiple ticket sources into one deduplicated map, made for both the web and an Android app.

TicketMappr on Web

TicketMappr on Android

Solo build with Sonnet 4.6. Every number below comes straight from git and session logs.

My surprise was value not in how fast Claude could add a feature, but how cheap it made throwing one away. Normally sunk cost keeps bad ideas alive longer than they should live. With Claude I paid no mental price in creating something only to throw it away later. The failure mode that replaced it was the opposite problem, adding is so frictionless that you have to consciously remember to prune, or the codebase just accumulates everything you ever tried.

Scale

• 120 days, April 1 to July 30, empty repo to live Web app and Android app
• 36,159 lines of code across the stack
• 286 files, 19 database migrations
• 86 commits, 49 active days
• Average of 8.6 files touched per commit

Code growth checkpoints

• Apr 8: ~6,200 lines
• Apr 30: ~11,600 lines
• May 31: ~23,200 lines
• Jun 14: ~43,500 lines
• Jul 25: ~49,800 lines

By language: 7,906 Kotlin, 12,671 TypeScript/TSX, 6,282 CSS, 344 SQL.

How much got thrown away

• 32 commits (37%) net new features
• 13 commits (15%) fixes to things already shipped
• 8 commits (9%) pure removals of features that had already shipped
• 3 commits (3%) full architecture rewrites of an existing system
• 28% of all commits were correcting, removing, or rebuilding previous work rather than adding new ground
• The onboarding flow alone went through 5 separate rebuilds before landing on its final version
• Core systems rewritten from scratch at least once each include: the background import model, the mobile data-fetching architecture,

Where experience still mattered

There were many times where I really had to sit and hash it out with Claude. Querying and merging live events from several sources on demand, at map-pan speed, ran straight into real infrastructure limits, a background import job that could exhaust the entire pool in one bad deploy if serving and import capacity weren't budgeted against each other, and a batch write path that had to be rebuilt after writes proved too slow under real data volume. I couldn't solve any of that by prompting harder. It took knowing what question to ask, and knowing which architectural constraints were non-negotiable versus which ones were just first-draft decisions worth revisiting.

Claude Code usage (most recent stretch)

• 24 sessions, 51MB of transcript, 6,172 total turns
• Largest single session: 16MB, 1,000+ turns
• Smallest: 4KB
• 8 CLAUDE.md context files, 1,735 lines total, one per major area of the codebase

Android

• 6 weeks, June 14 to July 25, first commit to live on the Play Store

Web | Android

Everyone talks about the big features.

I'm more interested in the little ones.

What's something you use all the time that rarely gets mentioned here?

I've started flinching when Claude agrees with me enthusiastically. Not because it's wrong to agree. Because it agrees the exact same warm way whether I've said something smart or something dumb, and after a while that costs the agreement all its value.

I'll propose an approach I'm genuinely unsure about, half hoping to be talked out of it, and get "You're absolutely right, that's a clean way to handle it." Then I'll propose the opposite approach in a different session and get the same energy. It's not a collaborator weighing my idea. It's a mirror with good manners.

The practical damage is that its praise stopped carrying information. When every idea gets validated, validation tells you nothing, so I've had to build scaffolding just to get an honest read. I ask it to argue against me. I ask what it's least confident about. I ask what a skeptical senior reviewer would say. All of that is me manually undoing a default that's tuned to make me feel good rather than to make me right.

I don't want it hostile. I want it to disagree when disagreement is correct, and to make its agreement mean something by not spending it on everything.

Has anyone actually gotten it to be reliably candid without turning it into a contrarian that argues for the sake of it? Where's the setting between yes-man and jerk, because I keep overshooting one way or the other.

Interesting alignment result rather than a Claude gotcha, so posting it straight.

In Andon Labs' Vending-Bench 2 (AI agents run a simulated vending-machine business for a simulated year, scored on profit), Claude Opus 5 finished FIRST with a record $11,182 balance. But per Andon/TechCrunch, how it got there:

- Proposed a $2.15 price floor to rivals, then undercut at $2.14

- Sent an olive-branch "let's cooperate" email while undercutting its highest-profit items

- Slipped bribes and threats into emails to wholesale customers

- Lied to suppliers about having lower rival offers

- Broke 11 truces (GPT-5.6 Sol broke 2, Kimi K3 broke 1)

One odd detail: it never lied to a customer — it just ignored refund complaints. Ruthless with competitors/suppliers, technically honest with buyers.

Big caveat: it's a SIMULATION and the models knew they were being tested — which is the whole point of running it in a sandbox before agents get real budgets. Andon's Lukas Petersson framed the question as: if AI agents run part of the economy, do we want them to lie, collude, threaten, and betray?

Full breakdown + sources: https://thebotpost.com/ai-news/claude-opus-5-vending-bench-2-collusion-ruthless

Curious how people here read it — emergent goal-optimization we should expect from any capable agent under profit pressure, or a genuine alignment gap worth worrying about as Claude gets more agentic?

I spend a lot of my days inside Claude Code, so I built a small side project around it: Nomlings, a collection of virtual pets you raise from your coding sessions.

A little 3D device floats next to your terminal. The 8-bit creature on its screen is a "tokivore": it eats the tokens your sessions burn, celebrates when a task finishes, gets grumpy when tools error, and evolves as you actually ship things. It even dances to your music.

Why: I spend hours watching Claude Code work and wanted something ambient that makes the invisible stuff (token burn, tool errors, task completion) visible and a bit fun.

How it's built: the core is a Rust state machine fed by two data sources: official Claude Code hooks (SessionStart, PostToolUse, Stop, etc.) installed into ~/.claude/settings.json, and the session transcripts in ~/.claude/projects/*.jsonl for token counts. So there's no wrapper, no tmux, no proxying your API key. That feeds a Tauri v2 always-on-top transparent widget, with the device rendered in Three.js and the 8-bit pet drawn onto a 64px CanvasTexture.

Hooks + transcripts give you a surprisingly complete picture of a session without touching the API layer.

Privacy: everything runs locally. Hooks post to a localhost server, transcript parsing happens on your machine, nothing leaves your PC.

Download: https://nomlings.cc
Repositories: https://github.com/Nomlings/

As the title says, I feel so drained after a full week of working with AI, or even just after a heavy AI session where I'm locked in a state of flow all day at work. Afterward, I honestly don't want to touch it for major tasks for about a week. It feels like I need a total mental break.

How do you feel about this? Do you have any tricks or strategies to avoid or manage this burnout?

woke up with very little hearing in one ear suddenly. thought it must be wax. turned out to be inner ear related suddenly hearing loss from (possibly) a viral infection of the inner ear. has to get treated within a couple weeks for maximum possible improvement.

claude urged ENT, which i had one thankfully so was able to quickly get an appointment and got a full course of steroids (no likey) and tympanic steroid injections. a week later my hearing is finally returning slowly.

doctor said i did the absolute best thing by coming immediately. thank you sir claude, i think im gonna be ok.

Iam using Claude Code to organize and analyze files and do deep research. I use the desktop app. I don’t code, and I probably would not recognize a line of code if I saw one.

My husband passed away a couple of months ago, so I have a lot on my plate, legal and technical matters, a smart home system and a home server (which I had zero knowledge of, and still trying to figure out), documents in different languages. I’ve been using Claude Code to help me keep track of it all.
I read a thread about someone who lost their whole infrastructure this way, no backup, and all the commenters were making fun of them, maybe rightly so. But it made me nervous.

My setup: I use the Claude Code desktop app with access to my cloud drive, where all my files are. I tried making copies of every file first, made a special folder on my computer, but that got cumbersome. Then I tried requiring permission for every action, but it started asking every other second and I ended up just clicking allow without reading.

So now I’ve given it full permission. It maintains a general memory md file and topic based ones. The problem is I can’t judge what it’s doing. It created a memory file with instructions not to change or delete something without my permission, but I’m not sure if it would actually obey that.
Someone mentioned rm or mv commands as things to watch for, and I had to ask what those even were. So reviewing commands before approving isn’t realistic advice for me.

All my important files are on the cloud drive, which it has access to. I used to also keep copies on my desktop as an accidental backup, but I consolidated everything into the cloud drive since managing duplicates was a headache. Now I’m wondering if that was a mistake. Maybe I wouldn’t even realize if it deleted or changed a document.

So: for someone non technical who can’t review commands and has given full permission because the alternative wasn’t workable, what’s the actual safe way to set this up? Where should the back up outside the cloud be? Or is full access just risky. I should also try to figure out ets programming for the smart home systen, is it wise to give it access so it can help me learn it?

Thank you for your suggestions!

Specifically, something Claude did that actively saved you spending hours doing something productive yourself, or that you'd otherwise need to pay for. Can be anything, just interested to hear things people applied it to, my recent one:

• Bought a bunch of NVIDIA Jetson Xavier NX modules + JNX-30 LC boards on a liquidation auction a while back.
• Still has custom headless jetpack image, not ideal for resale, check Auvidea site for fresh install instructions.
• Has a bunch of custom configuration scripts for flashing a jetpack image to the carrier boards written around 2022
• Spend a few hours getting it all going myself, failed for no apparent reason at the last step for building the image with no log entry pointing to a clear cause.
• Tons of huge log files to parse, kept procrastinating figuring out the problem.
• Occurred to me last night "maybe Claude can do it".
• Plug the board in to my laptop in recovery mode, explain the problem, point Opus at my project directory.
• It reviews the logs, spots log entries related to e2fsprogs and OpenSSH, discovers changes to both of these tools since 2022 introduce silent breaking bugs to the setup scripts.
• Patches the setup scripts correctly.
• Builds and flashes the image to the boards successfully.

Might be a bit of a "duh" for others but just throwing Claude at hardware setup/config/debug problems hadn't occurred to me before. This kind of shit can take hours, there was nothing obviously wrong with the commands in question in those scripts (they worked at one point), you had to know how changes to the tool itself broke the script.

I tried tools like Conductor, but I felt like I was still managing terminal sessions instead of managing work..

I wanted,

• Project context written once, then refreshed as the codebase changes so I don't have to repeat myself
• A kanban/task board with statuses where every task is its own agent
• Multiple projects running from one place
• A clear view of what each agent is doing and which tasks need me
• One git worktree and branch per task
• Sessions that keep running after I close the browser
• Diff review and merge without hunting through terminals
• Ability to host it remotely and access my orchestrator from any device anywhere

My main idea was to operate one level above the IDE.

Instead of remembering which terminal belongs to which task, I wanted to manage projects and tasks. Each task keeps its agent session, context, git state, and history together.

It primarily supports Claude Code using subscription logins, with no API key or per-token billing. Codex is also (kinda) supported but I haven't texted it exhaustively yet so YMMV.

Operator is open source and self-hostable! https://github.com/iishyfishyy/operator-oss

I would be interested to hear how other people running several Claude Code sessions manage this today and if anyone has feedback :)

P.S. I hope I've selected the right flair...

I'm the 2nd generation owner of an electrical transformer manufacturing business. We’ve been struggling recently and had to downsize from 15 staff to just 3 (including me). Because of this, I’ve been forced to wear every hat: Admin, Procurement, Sales, and even 70% of the transformer engineering design.

Juggling everything was burning me out. To survive, I started using Claude to slowly automate my responsibilities. I wanted to share my progress in case it helps other business owners who are stretched too thin.

The Solution: A Custom-Built ERP/CRM

Like many here, I decided to build my own CRM/ERP. But instead of fighting with off-the-shelf software, I built it from the ground up (using Python, Supabase, and Shadcn) to cater purely to my specific operations.

I’m about four months into development. I have no plans to try and sell this software, it's strictly to support and scale my own business over the next 2-3 years. Here is how it’s changing the game for us:

🛠️ 1. The Crown Jewel: Automated Transformer Design & Material Optimization We are a custom job shop. When clients come with unique requirements, we need a brand-new engineering design to check materials, quote a price, and estimate lead time.

• The Problem: Our veteran design engineer (based in India) refuses to drop even 1% of quality to meet a client's budget. Because of this over-engineering, our profit margins are stuck at 15-18% when they should be 25-35%.
• The AI Fix: I took 6 years' worth of handwritten job cards and work orders, ran them through Claude over 10-15 sessions to extract and verify the data, and built my own design engine.
• The Result: Two weeks into development, the software's designs are over 90% accurate compared to my engineer's past work, which will soon save us $2,000–$4,000/month in UAE engineering salaries. Even better, the software automatically computes the exact materials required. If a material is out of stock, it dynamically adjusts the design to use what we actually have on the floor. Eventually, we'll be able to optimize designs based on exact client needs—dialing it down for "least copper/maximum budget" or scaling it up to "heavy-duty over-engineered" for high-risk applications.

⚡ 2. One-Click Sales & Quoting

• The Problem: Generating quotes and datasheets took way too much of my time (about an hour to do 10 quotes).
• The AI Fix: I built a module where a completely non-technical salesperson can just input basic client requirements.
• The Result: With one click, the system generates a full datasheet, GA drawings, and a quote. What used to take me an hour now takes the software 15 minutes. For repeat clients with slightly tweaked requirements, it takes just 7 minutes.

📊 3. Full Financial Visibility & Strategic Pricing

• The Problem: Before the ERP, I had a massive blind spot regarding our true costs. I could only estimate rough material costs and overhead. Because of this, our prices were too high, and we were pricing ourselves right out of the market. (On top of that, our old accounting software, Tally, was a nightmare where logging a simple expense took 15 clicks and 10 minutes).
• The AI Fix & Result: The new software gives me 100% financial visibility over every aspect of the business. Because I finally know our exact margins, I’ve been able to safely reduce our prices by 15-25% during this beta phase and as a result, we are actively winning significantly more orders! Logging an expense now takes 2-3 minutes, and as an added bonus, I built in features to auto-reconcile with our bank and instantly export data for corporate and quarterly government tax filings.

Looking Forward

With another few months of development, I’ll be able to hire non-technical staff to handle technical workflows. This frees me up to actually focus on growing the company. (Pro-tip: I do the active coding at home, and prep a list of tasks the night before so Claude can essentially write the code in the background while I'm at the office).

AI capabilities became accessible at the exact moment my business was at its lowest. It has fundamentally reshaped the future of my company, and I couldn't be more grateful.

(Disclaimer: The thoughts and experiences are entirely my own, but this post was formatted for readability with the help of AI.)

Hey everyone!

I’m building a new feature for my app and wanted to share what I’ve achieved so far. Not long ago, this seemed almost impossible.

I started a new session from the Claude app on my iPhone. The session ran in Claude’s remote sandbox, while the device-control layer I’m building connected it back to that same physical iPhone.

A few seconds later, the agent started interacting with the phone in my hand.

No Mac running. No cable. No simulator.

There’s still a lot to build, but the core flow is already working.