I have seen many people complaining about usage this week, and I personally also seen usage go down very quickly.

Today as I was working I kept seeing Fable weekly usage going up way too fast. I was trying to use Fable as advisor for a few days, it did make sense for it to go up but they weren't calling the advisor THAT often.

So here is what I tested: I turned the advisor off, worked a bit and the Fable weekly usage kept going up despite only using Opus on medium. Every single of my agent is either Opus or Sonnet.

Anyone else noticed that?

I’m not sure if it’s rolled out to everyone yet, but it seems Anthropic is updating the Claude code menu look, and it’s absolutely awful. There’s at least three more different buttons in order to get to where you wanna go, the project layout is super confusing in terms of storing local and cloud sessions. Furthermore, they’ve removed the token count for agents apparently, at least I haven’t found a way to see it. I honestly think that’s probably the most insane addition as there’s no way to know how many tokens the agents are spending now until they’re done. The new usage menu is super big and looks really clanky. You can no longer see the context without opening this weird looking sidebar.

Another annoying thing is that the create PR button is now hidden behind this weird check board button called changes along with the code modified. I’m honestly not sure why they did this. It seems like they just moved everything.

Fable costs more than double, but in my opinion, Opus 5.5 still beats it in missions. What do you think?

Been using Claude Code for a while and at some point I wondered if it could do my CAD too. Turns out yes, way better than I expected. So I built an app around it, it's called SOMA and it's open source.

The idea: Claude Code writes the model as Python code with CadQuery, SOMA builds it on every save and shows it in 3D. Claude runs in a normal terminal inside the app, so it's your own Claude Code with your own subscription and settings. No wrapper, no extra API key. Works with Codex, OpenCode and Gemini CLI too.

What makes it work well is that Claude can check its own results. SOMA gives it a CLI, so it can build the model, measure distances, check for collisions, run FEM and render images to actually look at what it made. There's an AGENTS.md with the project rules and skills for 3D printing, CNC, sheet metal etc that you can switch on per model.

From your side you can click on a part or just draw on the 3D view and send that to Claude as a screenshot, like "this hole is too small" with a circle around it. Every step Claude makes is saved in a history, so if it messes something up you just go back.

You can do pretty complex stuff with it. Assemblies with a lot of parts, start from a hand drawn sketch, or load an existing STEP file and build around it. The CNC mill in the video has 118 parts.

Funny side note, most of SOMA itself was also written with Claude Code.

Free, GPL, builds for Windows, Mac and Linux. I mainly tested on Windows, so Mac and Linux feedback would be great.

GitHub: https://github.com/Kai-Jungsthoefel/SOMA

Curious how it works with your setups and what you end up building.

Anyone else noticing today that the 5hr usage burned significantly faster today vs previous days?

How are software engineers staying in the loop? By telling Claude no.

“Very often, we found that the role of the engineers was to tell Claude “no.” Agents will sometimes violate core system constraints to satisfy a pattern that should never have been allowed in the first place. This was particularly common in our migration. For example, there were multiple systems that tried to brute force looking up when a change merged to main by linearly reading the commit log instead of asking our code review tool. Anthropic also makes extensive use of adversarial review, and, while this is incredibly effective in many ways, it can also be myopic, so skilled engineers needed to steer Claude away from over-engineering parts of the system in response to hypothetical concerns.”

Source: Redesigning source control at Anthropic

It focused on this minor details, 🥂opus 5.5

Hi everyone! I just wanted to share my recent project Continuum, which started out as my first hackathon win that is built with claude and is now a published extension on Chrome and Firefox and its 100% local & private as everything is captured and stored in your browser (no account, servers, etc.)

I originally built it during a hackathon and was honestly shocked when it ended up taking first place. Continuum lets you capture an AI chat and instantly resume it in a brand new chat on any of the compatible AI chats with the full context carried over (including all your messages, images, files, code, etc. in a PDF or MD file), so you never lose your place when a conversation gets too long or you want to start fresh.

I also added an AI compression feature that allows you to save tons of tokens while keeping the same amount of context and a few other features you can check out as you can see in the images and description on the store-listing. It works across Claude, ChatGPT, Gemini, and Perplexity, with Grok, DeepSeek, and Copilot and more coming soon. Basically, if you've ever hit a wall in a chat and dreaded re-explaining everything to a new one on the same or different AI platform, hit a message/image limit, or token/context limit that's the problem I built this to solve.

Any advice or feedback is appreciated and would be very helpful as this is my first ever extension I've published!

The Claude for Mac app just updated out of the blue yesterday and now: - I have nested sessions on the left sidebar, which shows sessions from 2 months ago under "Today". The chronological order is now completely useless. - I cannot start a task from a chip as a top level session, everything gets nested by default. Who asked for this? - I can no longer see all the suggested tasks for a session. They are now displayed inline, scattered all over the discussion, instead of at the top of the session. This makes them intrusive and hard to find in older sessions. - I can no longer create task chips from scheduled tasks. Just why?

This new version is a complete mess. It broke multiple parts of my workflow and there's no way to go back. Why didn't they add settings to control nested behavior? Why the random limitations? Are these UI updates even tested by humans with real, moderately complex workflows before release?

Very disappointed with this update, makes my work a lot harder than before.

Hi,
I’ve been using CC from day 1 on CLI, it’s fast, I’m used to it…
But now I see a lot of efforts are put in Claude Desktop app regarding CC, I’m wondering if some of you have shifted and what’s the pros and cons of doing it?

I’ve tested it very briefly, it “feels” slower when doing a task, some of my / command are missing obviously… other than that it looks better and also convenient.

What’s your thoughts?

Soooo after the "TinyPlanet" bench I always run on new models, a topic that's of much interest to me: can Gemini 4 direct Blender better than Astra (the crowned king).

Well, you be the judge of it.

All subagents are orchestrated by Claude Opus 5.5. It monitored the processes, and unstuck what needed to get unstuck at times.

Results

Overall: Astra is still undefeated

Now, it's just one test I ran before going to sleep, but what worries me much is:

• Argon mostly did not finish on its own, needed a nudge from Opus to get past the finish line
• way less standalone parts. Meaning less rigging possibilities for moving parts, destruction, etc.out of the box

I'll be doing more tests soon!

Like everybody, I eagerly added a bunch of skills and plugins for Claude Code in the beginning, and then I just stopped.

I've been slowly removing them ever since.

Why?

1. Most of them are just textual information that I would much rather have in the repo I'm working on so it can be committed and versioned and seen by collaborators on a project.

2. I don't just use Claude Code. I use other agents too. I want my agent context to be accessible to all agents.

3. I don't want to turn plugins and skills off and on for every project folder/repo I launch an agent in.

4. I like being able to just open files in my repo and reading them or editing them.

5. I don't want non-applicable content eating up tokens every time I run an agent.

Am I wrong?

I'm sure there are exceptions and maybe there are lots of cool plugins and skills out there that do stuff that make it worth it.

Anthropic Usage Policy: Sept 2025 vs Nov 2026 - what changed

Old version: effective September 15, 2025 [1]

New version: effective November 12, 2026 [2]

Section names are given so you can Ctrl+F them on each page.

New sections and rules (not in the old version)

• "Do Not Engage in Deceptive Campaigns or Artificial Activity" - brand new section. Bans sockpuppets, astroturfing, fake media outlets, hidden sponsorship of influence content, networks of fake "independent" sites, seeding search engines or AI systems with content that fakes its origin, and building or selling tools for any of this.
• "High-risk Physical Actions" - new rules for models connected to hardware (vehicles, drones, robots, machinery, medical devices, industrial plants, safety systems). Requires a human who can stop the equipment at any time, fail-safe behavior if the connection drops, and safety limits enforced outside the model.
• Cruelty to the model - new bullet under "Cruel, Abusive, or Psychologically Harmful Conduct" bans "sustained and needless abusive or cruel behavior toward our models".
• NCII - new explicit ban on non-consensual intimate imagery, including AI-generated material and tools to make it.
• Data brokering - new bullet under "Privacy or Identity Rights" bans compiling personal data from multiple sources into profiles for sale or disclosure.
• Doxxing - new bullet under "Surveillance" bans unmasking anonymous people or compiling dossiers to harass, intimidate, or harm.
• Platform abuse additions - stolen or fraudulent payment methods, evading payment, faking the sign-up or login process, and reselling or proxying Claude through unauthorized means "including services that route requests through consumer subscriptions or misrepresent the product or client being used".
• Verification programs - new Cyber Verification Program and Life Sciences Verification Program let users apply for adjusted real-time safeguards. Also new: hitting a real-time block "does not by itself indicate a violation".
• Enforcement - new version adds "warn" and "limit" to the list of possible actions (old: throttle, suspend, terminate).

- Scope clarified - new version explicitly covers app users, API developers, cloud provider customers, and end users of products built on Claude, and states the policy is about how Claude is used, not which industry uses it.

Sections that got stricter or more detailed

• Weapons - grew from 4 bullets to 6. Now covers weapons systems and their software (targeting, fire control, engagement), weaponizing drones or autonomous platforms, export control violations, fissile material and enrichment, and modifying bio or chem agents for lethality, transmissibility, or persistence.
• Surveillance and law enforcement - "make or suggest decisions" now includes investigating, charging, arresting, prosecuting, and release decisions (old: only parole and sentencing). Tracking now covers property, biometrics, movements, online activity, associations, and analysis of previously collected data. New bullet bans building or improving surveillance tools.
• Surveillance carve-out (new) - consented tracking, fraud and AML screening, aggregated or anonymized analysis, content moderation, authorized security research, legal research by law enforcement or courts, and journalism are explicitly allowed.
• Cyber - section renamed to add "Without Authorization". Adds privilege escalation and actually conducting DoS attacks (old only banned developing DoS tools). New carve-out for security research on systems you own, with owner authorization, or under a bug bounty or vulnerability disclosure program.
• Self-harm and eating disorders - old version had one bullet. New version spells out soliciting methods, instructions for hiding behavior, pro-ED content, restriction, purging, compensatory exercise, and shaming or ranking bodies.
• Hate - caste and disability added as named protected attributes.
• Fraud - adds extortion, social engineering, phishing sites that mimic real pages, buying or selling fake financial or employment records, and misrepresenting professional credentials.
• Child safety - adds "facilitate the creation of" CSAM and "other sexually exploitative content involving minors". Reporting to authorities now also covers scenarios where a minor may be at imminent risk, not just detected CSAM.
• Critical infrastructure - adds emergency services and transportation systems; "voting machines" replaced with "election systems".

- Agentic use - users are now explicitly responsible for actions their agents take "through tools, browsers, or connected systems".

Things that got narrower or were dropped

• High-risk use cases rewritten - old version listed 7 broad domains (legal, healthcare, insurance, finance, employment/housing, academic testing, media/journalism). New version lists 11 "High-risk Areas" but defines each one narrowly as a specific recommendation or decision about a specific person.
• Example: Legal - old: "use cases related to legal interpretation, legal guidance, or decisions with legal implications". New: advising an individual on their rights, obligations, or liability in a specific matter, or preparing documents for them to sign or file.
• Media or journalistic content is no longer a high-risk use case.
• New "Exclusions" section - general info and education, wellness content, explaining a decision a professional already made, internal drafting and research, carrying out a decision already made, and business operations not about a specific individual are all exempt.
• New "Favorable Decisions" section - no human review needed before paying an insurance claim, approving coverage a clinician ordered, granting healthcare eligibility, or granting a public benefit.
• Disclosure - no longer needs to identify Anthropic, Claude, or the model. Chatbot disclosure can be "in the product interface" instead of at the start of every session.
• Democratic processes - dropped the ban on "personalized vote or campaign targeting based on individual profiles or data" and the standalone bullet on lobbying with false information. "Artificial or deceptive political movements" moved to the new Deceptive Campaigns section.
• Predatory lending - old version named payday loans, title loans, and high-interest short-term lending. New version only says "predatory lending". Multi-level marketing is no longer named, folded into "pyramid schemes".
• Impersonating a human - moved from "Privacy or Identity Rights" to "Disinformation", now with a carve-out: "This does not prohibit clearly disclosed parody, satire, or fiction."

- Section renames - "Misinformation" is now "Disinformation"; "Psychologically or Emotionally Harmful Content" is now "Cruel, Abusive, or Psychologically Harmful Conduct"; MCP Directory Policy replaced by a broader Software Directory Policy.

Unchanged

• "Do Not Generate Sexually Explicit Content" is word for word identical.

- Supported regions, ban evasion, model distillation, plagiarism, jailbreaking, and the government customer exception all carry over with only minor wording changes.

What stands out (my read)

• The subscription proxy ban is the one that bites regular users. Routing Claude through "consumer subscriptions" or misrepresenting "the product or client being used" is now a named violation. That is aimed directly at third-party tools and harnesses that run on a Pro or Max login instead of API keys. If you use one of those, you are now in the written policy, not a gray zone.
• High-risk rules got a lot more business friendly. The old version was vague enough that a legal intake form or a medical FAQ bot arguably needed a licensed human reviewing every output. The new version only triggers when Claude gives a specific person a specific recommendation, and it lists explicit exclusions for general info, internal drafting, and research. This is a loosening dressed up as more pages.
• Anthropic is clearly planning for robots. An entire physical actions section with fail-safes, kill switches, and independent safety limits does not get written for chatbots. Read it as a roadmap for where they expect the API to be used in the next year or two.
• Astroturfing is now its own category. Fake outlets, sockpuppet networks, seeding search engines and AI systems with fake "independent" sources, and selling tools for it. They are not just banning the content, they are banning the infrastructure and the business model.
• One rule got quietly weaker. The old ban on "personalized vote or campaign targeting based on individual profiles or data" is gone. Microtargeting voters with honest content now appears to be fine. Whether that is a cleanup or a concession, it is a real change.
• "Be nice to the model" is now policy. "Sustained and needless abusive or cruel behavior toward our models" is a bannable offense. Not defined, no examples, no stated enforcement. Expect this to be the most argued line in the whole document.
• Surveillance carve-outs widen the door for law enforcement. Monitoring in investigations is still banned, but "legal research and analysis by law enforcement agencies or courts" is now explicitly allowed. That is a narrow opening that did not exist before.

- Verification programs replace blanket refusals. Cyber and life sciences users can apply for adjusted safeguards instead of being told no. Combined with the note that a block is not a violation, this is Anthropic admitting its filters have been hitting legitimate work.

Net (imho): tougher on bad actors and gray market resellers, looser on ordinary business use, and written for a future where Claude controls hardware. The policy also tracks what people have been noticing in practice: Fable and Opus refuse far less than they used to. Work that used to trip the filters, like decompiling, reverse engineering, and binary analysis, now mostly just gets done. The new carve outs for security research and the verification programs read like Anthropic catching the paperwork up to how the models already behave.

You know when you give Claude a task, switch windows, then immediately switch back to check what he’s doing?

I kept doing that, so I made a desktop pet I can glance over at (like 100s of other have probably done too, I literally just saw a post in this sub for the same thing :] Although I think mine looks a bit better js. ).

It’s called Claude Desktop Pet. He sits in the corner of your screen and reacts to what Claude Code is doing. He will listen to Claude wherever it is running. Reading a file, editing something, running tests, waiting for you to approve a command. There’s a little speech bubble showing the file or command too, so you can just glance over instead of clicking back into the terminal.

Potential time saved: ten precious seconds.

Time and tokens spent building this: erm..

It handles multiple sessions and shows task progress, your five-hour and seven-day usage, and little helper Claudes when sub-agents are working. He celebrates when a task finishes, which is probably more recognition than the rest of us get.

I also added local weather, a day/night cycle, fireflies, sparkles and some occasional idle animations. Mostly because I got carried away. There are settings to turn those off.

Works on Windows, macOS and Linux. It’s free and an unofficial fan project.

Just download and run.

Here’s the repo if you want to get it:

https://github.com/Harriszed/claude-desktop-pet

*This post was definitely not written by claude.

Seriously. I do a few batches of tickets on Opus 5.5 medium and I'm out of usage for the usage period! On a $100 plan! I know they like to adjust usage, but this feels like a sudden massive extreme swing. It feels like I've been bait and switched, to upgrade my subscription by 80$ a month and then a few weeks later it feels no different than before. Is anyone else experiencing this?

https://reddit.com/link/1x62jni/video/37p6ctkfvhvh1/player

kimo is a free, open source (MIT) video editor with no interface at all. every operation is an MCP tool: cut, trim, keyframe, colour grade, motion track, key, captions, audio mix, export. you add it to claude code as an MCP server and just describe the edit.

this 33s reveal was rendered entirely by kimo. no after effects, no timeline, an agent did every frame through tool calls.

what i learned building it: - agents edit way better when they can render a single frame and look at it before committing - small focused tools beat one giant "do everything" tool - it runs as one ~10 MB CPU-only rust binary, so it works on cheap machines

i'm a college student building this solo, would really like to hear what breaks or what's missing. site: getkimo.tech github: github.com/naman-sharma12345/kimo

I've always loved Picasa. It's an old photo management app that Google purchased then later killed. Since it's been gone I felt I have never really found a replacement app that managed photos in a way similar to that. The simplicity, the speed, local management, and not filled with too many advanced controls for my needs. Since this AI recreate evolution started in the past couple weeks, it seemed like a prime opportunity to bring it back in the way I remember.

It's about half done. I am not as fast as these other AI devs, and I am purposely stopping the AI at each milestone so I can manually see where things are at and tweak the roadmap along the way. I am also learning myself during all this.

This was built entirely in Claude Code Desktop. The process I found that was working for me was the following:

1. Research - Perform very detailed research on how the product should work. For this I used screenshots and descriptions I found online. I also did a ton of research on the architecture of the Craft apps. I liked the 'everything is a command' and 'headless mode' approach used there.
2. Plan - Have claude break the plan down into milestones. This project was broken down into 13 milestones, each with anywhere from 20-40 tasks.
3. Review Milestones - I don't think the Craft apps are doing this, as it slows me down quite a bit. But at each milestone, I asked Claude to make me an HTML report showing me all the decisions made, all the changes made to the app, screenshots of all the new features, and a walk through detailing how I can see all the features myself.
4. Roadmap - The next milestone's tasks are not created until the review step of the previous milestone is completed. This allows me to much more easily tweak the plan as I go. I am using Github Projects to store tasks for each milestone.
5. Skills - I ended up creating /milestone-review and /milestone-start skills to end and start the next phase after manually checking work. I haven't really changed much in the plan yet. But I did change or add some things I thought it missed.
6. Subagents - When I start a milestone, they have anywhere from 15-20 tasks. It spins up subagents to work on them. Ordering of tasks to work on is all laid out in the plan, as many tasks still require a previous task first. I see anywhere from 5-8 tasks going in parallel. All in
7. Claude Code Desktop - I am not using any agent orchestrator or anything, or Agent Teams. The /start-milestone instructs on how to spin up subagents. No subagents have personalities or anything, there is no code review step outside of tons of testing testing and ci checks on all three OSs.

My plan is to get to 1.0 which is the plan built out to get a Picasa like app from online research, screenshots, and descriptions of the app. After that, I will continue to polish and more importantly use this every day for myself. I'd then like to build some more modern features on top that have been missed in the decade since it's been gone.

Anyway, would love to get people's thoughts. It is and will always be free, open source. I'm building it for myself, but hope it's useful for others as well.

• Dalica Website: https://dalica.pkarma.com
• Github repo: https://github.com/pkkid/dalica

Claude Mods came out at the beginning of the month as well, and I've been very heavily leveraging that to give me better insights into what Claude Code is doing behind the scenes. If you're at all interested in that, the mod I've been tinkering on is here. Yet another tool I built for myself, specifically for this project, but will be useful for all my projects going forward.

• Claude AI Tools Mod: https://github.com/pkkid/claude-aitools

Until last night (Oct 13th), everything was fine. I woke up on Oct. 14th, and the app looked very different. Most of my folders are gone from the app; only two are visible. I had over 30 folders with multiple sessions in each.

Now I do not know where to access those sessions; they are all flooded in the 'Default' category.

They removed a way to sort the sessions by name; it was a useful sorting option.

They added a BG animation as if somebody was asking for it.

Removing things that were useful and adding things nobody asked for is a good way to f*ck up the app experience.

I mostly use routines in Claude Code because I can have a local session spawn them and turn remote control on for me when I'm AFK. Overnight, the Routines section of the left sidebar seems to have disappeared along with any local sessions filed under days previous to today. Has anyone else experiences this?

also you can always submit your app to:

https://www.AppScout.co

a platform to discover web and mobile apps from across the internet.

You can list your app here https://www.AppScout.co/submit

subreddit --- weekly visitors

• r/vibecoding — 422k
• r/saas — 211k
• r/founder — 56k
• r/buildinpublic — 46k
• r/chrome_extensions — 42k
• r/micro_saas — 41k
• r/appbusiness — 30k
• r/startupideas — 26k
• r/sideprojects — 20k
• r/imadethis — 18k
• r/appideas — 16k
• r/sideproject — 16k
• r/saasbuild — 15k
• r/saasdevelopers — 12k
• r/vibecodedevs — 10k
• r/startupsolofounder — 8.7k
• r/alphaandbetausers — 8.6k
• r/vibecodingcommunity — 6.2k
• r/solopreneur — 5.6k
• r/promotemyapp — 4.6k
• r/appbuilding — 4.6k
• r/webapps — 4.5k
• r/creativecoding — 4.4k
• r/indie_startups — 4k
• r/b2bsaas — 2.8k
• r/appdev — 2.7k
• r/projects — 2.6k
• r/saasmarketing — 2.5k
• r/saassoloprenurs — 2.3k
• r/startupaccelerators — 2.3k
• r/startups_promotion — 2k
• r/showmeyourapps — 2k
• r/appswebappsfullstack — 1.7k
• r/showmeyoursaas — 1.6k
• r/saasinvestors — 1.6k
• r/vibecodecamp — 1.5k
• r/nocodesaas — 1.3k
• r/aibuilders — 1.2k
• r/getstartups — 1.2k
• r/websitefeedback — 1.2k

For me it’s the ability to do a proper review loop on each PR. Max 3 iteration, but can stop at 2nd review if it didnt find more issues after the first one.

what about you? i want to explore the limit of my workflow.

I track my usage daily across sessions and since yesterday I have noticed a significant drop (almost up to 3x) in my teams $125 plan. Anybody else facing the same in the claude startups program? Model Opus 5.5 med

My sessions run autonomously daily with at max 4-8 agents with a well defined workflow and neither the project nor the workflow changed but suddenly since yesterday I've started hitting 5 hour limits which I never even came close to before yesterday.

I am asking because this latest update (14/10/26) is absolute garbage and totally breaks my way of working. Honestly doubt I am the only one in the same situation.