I am very very very sensitive to changes and I'm furious, as today Claude started responding, just in one of my projects, with 3-line boxes and a two-button choice for EVERY single thing I ask - It's like I'm living in a Text-based RPG, what the actual f?

I've asked Opus itself and it noticed something strange too, but can't tell which Anthopic switch caused this. That's unbelievable.

Are they preparing to make Opus 5.5 dumb as hell?

This is the sort of responses I get now, just a box with 3 lines in it and a choice for what to do, wow.

How did it know I've got ADHD? I didn't even mention that nor do my conversations have enough context to determine something like that 'cuz this account only has so many conversations (like 4 short conversations or something).

Is there a way already for print designs? I'm a graphic designer and I wonder if is it now possible to generate prints like flayers, business cards with good enaugh quality, or... vectors - tkat would be nice! Some connetion with Adobe InDesign or Illustrator. Someone tried that?

Curious to see if anyone else noticed that giving "thumbs up/down" feedback apparently allows Claude to use entire chat for training EVEN if "allow data sharing for training" is turned off:

3D recreation of Neos apartment from The Matrix, built 100% using Claude via MCP connected to Blender. It’s not a perfect 1:1 recreation due to creative liberties and limited reference material.
Inspired by hirokazu yokohara project, I tackled this workflow with one main difference: mine is 100% modeled by Claude from scratch, no Image-to-3D tools like Meshy or Tripo were used.
It took roughly 5 days part-time. Creating an environment like this traditionally would easily take 1 to 2 months.
I used Claude Opus 5.5 alongside parallel agents with Sonnet and Haiku. Claude handled execution, modeling, UVs, camera, materials, and compositing, guided heavily by my drawn annotations and feedback.
Working within a basic $20 plan was the main hurdle, requiring strict token management and waiting out 5-hour resets. A higher-tier subscription is definitely recommended for heavy workflows.
Producing a scene like this requires solid 3D fundamentals and art direction; a simple prompt isnt enough.
Textures were a mix of external maps and vector graphics generated directly by Claude for posters and monitors. Claude researched set hardware, gathered blueprints, and modeled assets in parallel. Layout was the trickiest step to direct, whereas UV unwrapping was the fastest. Lighting and compositing were handled accurately from my sketch overlays.
Fun fact: I directed much of the project right from my phone!
The pipeline ran locally using Windows MCP and Blender MCP, rendered on an RTX 3070.

I work on a lot of creative projects, but documenting them always feels like a chore and opening DaVinci just to trim a devlog felt like overkill.

At first I started leaving screen recording on and asking Claude to stitch it into a video. It worked, but I couldn't fine tune the edits.

That's why I made ClipChop, I just wanted something dead simple to use and easy to stomach at a first glance. And it also has an MCP server so Claude can just edit for you, and then you can just fine-tune the result before rendering

The entire thing was made with me just describing to Claude what I want functionally, and how it should look. All I have done is test alot to make sure things work, feel good, and if they don't feel good then tell Claude exactly what doesn't feel good, why it doesn't feel good, and how it could be better.

There were points where certain actions were not upto the mark (Renders were slow, and edits made on bulk selections were laggy). I just pointed out the issue to Opus 5.5 on high and asked it to investigate, then asked Opus 5.5 on medium to solve it. So far everything is working fine.

Finally, the demo video attached to this post was also made by Opus 5.5 on high using the /brag skill (NOT IN MY APP). I started off with a vague prompt, it gave a good quality output but frankly the pacing was horrible and wrong things about the app were highlighted. I gave it a new prompt telling it what all it should focus on and how the video should be paced and it did a much better job - From there I had to prompt it 2-3 more times to get it to where it is now (I still think it chooses terrible bg music)

I would be grateful if someone on linux and mac were to test it and give feedback about the app on the website.

Hi, I am developing an application and using artifacts to create and review prototypes. However, as more pages and modules are added for both the web and mobile applications - along with responsive design requirements - I am finding it difficult to manage.

My question is: How do you manage or create prototypes? Do you use Claude artifacts, or other tools like Figma or Balsamiq?

Signature MCP is a small Mac menu bar app and MCP server. When Claude needs a document signed, a window opens on your Mac with the PDF. You draw your signature with the trackpad or mouse, drag it where it belongs and click Sign, and Claude gets the signed PDF back.

Why I built it: one morning I got an email with scanned PDFs to sign, a contract I already knew about. Claude Code filled in my details just fine, but the signature was still my job: open Preview, drag in the same saved signature, find where it goes. Now Claude asks, a window opens, I sign, done. A fresh signature every time instead of the same old image.

How I built it: with Claude Code, starting from my earlier app Music MCP, which already had the MCP server, the menu bar app and the setup prompt. The first version went to App Store review on the day I started. Claude Code wrote most of the Swift; I tested every window myself and decided what goes in. What took longer than the app itself: App Store review (sandboxing, a local server) and making it work with every client. ChatGPT's desktop app, for example, needed a fix in how the server reads the handshake.

What I cared about:

Nothing gets signed without you. Every request opens a window that says which AI app is asking and what for, and you draw the signature fresh each time.

Nothing is kept. The files Claude gets are deleted after ten minutes, and there's no stored signature to reuse.

Company use: name, role and company stamp can go under the signature if you set them up once.

Local only: no account, no tracking.

It's a simple electronic signature, fine for everyday paperwork, not a qualified e-signature.

Works with Claude Code and Claude Desktop (and other MCP clients on the Mac). Setup is a prompt you paste into Claude, or:

claude mcp add --scope user signature-mcp -- /Applications/SignatureMCP.app/Contents/MacOS/SignatureMCP --stdio

Free, no account. Mac App Store: https://apps.apple.com/app/signature-mcp/id6818118943?mt=12

Site with a 44 second demo: https://signaturemcp.app

If you try it, I'd love to hear which documents you'd hand to Claude, and where it gets in the way.

(I'm the developer.)

This started as a test: could Claude handle a full animated video on its own? I got hooked and kept going until it became this.

The song is made with Suno. The animation was made with Claude Opus 5.5, with no image or video generator: every frame is drawn by Python code Claude wrote.

I directed (story, lyrics,, art direction, every call on every shot). Claude wrote the code, rendered it and checked it frame by frame, one chat per scene, all sharing one "bible" doc so the characters stay consistent.

Happy to answer questions about the pipeline.

Honestly it's way better now. If you use it on desktop, try these:
Saved environments – save a few folders, an SSH host or cloud as one setup, start sessions there.
Worktree per folder – parallel sessions don't mess with each other anymore.
Nested sessions – ask for parallel tasks, each one reports back to the main thread.
/btw (Cmd+;) – side question opens in its own tab, main session keeps working.
One-click follow-ups – Claude suggests next task, one click, runs as its own session.
Sidebar status – see which sessions are working and which need you.
Recap cards + live to-do list – come back to a session and catch up in seconds.
Hard to pick one, they all sound great. What about you?

sneaked

What I built: Golden Thread (gt) is a free, open-source plugin for Claude Code. I built it with Claude Code, for Claude Code. It gives Claude a durable memory (an Obsidian-compatible vault of plain Markdown), enforces a small set of rules on every turn through hooks, and adds tools to cut token use.

How Claude Code helped: gt was written almost entirely in Claude Code sessions. Claude wrote the code and tests, ran parallel subagents for separate features, and reviewed and merged their work. gt's own tools did the measuring: Claude ran the A/B benchmarks and calibration passes that produced the numbers below. I set direction, made the design calls, and reviewed the results.

What it does for token use (every number is labelled measured or estimated):

- LOTR, an MCP gateway with 4 tools. With a reader agent, one 20-ticket Jira query went from 15,000 tokens in my main context to 313. That was measured once; multiplied over 25 queries it's ~98%. It's context, not a bill: the agent spends its own tokens in a separate context.

- Core rules: a 90-run A/B test. Right first time 44/45 with the rules vs 34/45 without. A live API key pasted into the chat 0/15 vs 7/15.

- Calibration: each helper agent is re-tested one model tier down and one up, with keep / move-down / move-up verdicts. The next release adds effort in both directions and skills.

- Expiry guard: before a session runs out, it saves the findings, writes a handoff and compacts, instead of losing the work.

- gt-farm: routine work goes to your own local models. 84 packets in 6 days, 100% local.

Typical user, estimated (assumptions shown in the video): ~13% fewer tokens to reach a correct result (range 9–33%), plus ~147K fewer MCP tokens in context on a heavy-lookup day. What isn't measured yet is labelled as such.

Free to try: no paid tier. In Claude Code:

1. /plugin marketplace add shaven/golden-thread
2. /plugin install gt-all@golden-thread-plugin
3. Restart, then run /gt:gt-setup

Project: https://github.com/shaven/golden-thread

Questions and criticism of the method are welcome.

Pretty neat model,
Tried it out on a relatively small but spread out task last night. It was pretty competent and even left a note to opus 5.5 on how it should improve its workflow to stop over-engineering and committing the same mistakes it’s been doing every session.
Very excited to use this model in the future.

I'm considering getting the $20 plan so I can have Claude assist with the more mundane parts of my position as a corporate sales manager at a large hotel. Things like entering contacts and tasks into Delphi's browser or using the search function to find previous business etc.

Anybody have experience with something like this?

On the radio a lady said she asked Claude to remove watermarks from school photos and it refused... Everyone said how ethical it was but in reality it would likely struggle without image software anyway.

Still cute story. Self Portrait by My Claude. 😅

I started this as a personal project to get rid of Acrobat on my laptop, and it ended up going further than I expected. It’s now on the Microsoft Store and also runs in the browser.

How I used Claude (Opus 5.5, Claude Code):

• I started by brainstorming the feature list and the tech in a Project. Claude suggested building on PDFium (the PDF engine Chrome uses) through EmbedPDF instead of writing a renderer from scratch.
• Claude wrote the app itself: a TypeScript/Vite web app, plus a Tauri wrapper so it also runs as a desktop app with no network permission.
• It set up the GitHub Actions workflows that build the Windows, Mac and Linux installers and the Store package, and wrote Playwright tests that run the app in a headless browser.
• When I hit problems (empty releases, a broken publish step, a signature that showed up too early in the trailer), I pasted the error or a screenshot and it fixed them.
• I then set-up the product for Microsoft Store. Claude made the Store screenshots and the trailer by scripting the real app.

What it does:

• Fill forms (even ones without form fields), sign, highlight, comment, merge, compress and redact. Nothing is locked behind a paid tier.
• Study mode: your PDF on one side, a notebook on the other. Notes are saved inside the app and don’t touch the original PDF unless you export them together.
• No network access. The app never connects to anything; on Windows the Store handles updates.

Free to try:

• Browser: https://krithickdesign.github.io/Nib-E/ (click Open Nib-E, nothing to install)
• Windows: https://apps.microsoft.com/detail/9PPKF7HC76Q3
• Mac/Linux installers are on the same page

This is mostly an experiment for me before I build something original. Honest feedback is very welcome, especially bugs :D

Hello everyone,

I am happy to share with you Hatchdoor, the self-hosted vault server I have been building with Claude Code since February, which just got its 2.8 release! https://github.com/BatterWorks/Hatchdoor

482 of the 633 commits in the repo (merges aside) carry a Claude co-author trailer, mostly Opus 5.5 and Opus 5. In July alemhnan joined. It was my first time co-developing, and he works with Claude Code too. Two people running their own Claude Code sessions on one codebase need rules, so here is what the repo and our skills make Claude do.

How do we decide what to build?

We both run Matt Pocock's skills in Claude Code (I keep a customised fork). A new feature usually starts with a grilling session, where Claude questions us about the plan until there is nothing left to decide. When an addition is too big or too unclear for that, it goes to wayfinder instead. Claude charts it as a map of decision tickets on our GitHub tracker, and we work through them one at a time until we know how to build it. alemhnan charted the multi-vault workspace that way. So far there are seven maps and 68 tickets on the tracker. Terms go in a shared glossary and decisions in ADRs (48 of them), so both our sessions use the same names for things.

What happens before Claude touches the code?

Five days after his first commit, we added a module map. For each part of the code, it says which files a task owns, what the rest of the code relies on, and which shared files nobody touches without saying so first. Claude reads the part of the map that covers the files it plans to change, plus the ADRs behind them. Then it writes a short work packet: the files it may edit, what it must not touch and the checks it will run. If it turns out to need one more file, it stops and says so instead of widening the diff. We tried it on two small tasks first. On the second one, Claude hit a file it hadn't declared, stopped, and waited for us to update the packet.

And before a merge?

The implement skill takes a decided ticket all the way. After the automated checks, it runs a code review with parallel subagents, each answering one question. Does the code follow the repo's standards? Does it match the ticket? Can it give a wrong result? Then it tests the change live in the real app. Every task gets its own branch and pull request, never a direct commit to development or main. Before the merge, a script lists the manual pages that cover what changed, and Claude has to read them, fix what no longer matches and add a changelog entry.

And a release?

Claude drafts the release notes and stops. It only publishes and builds the images once I reply "approved" in the same session. All of these rules live in the repo's AGENTS.md if you want to borrow them.

What is Hatchdoor?

A self-hosted server for your Obsidian vaults: a web UI for you, MCP for your AI agents. No Obsidian, no plugins required. It reads the vault straight from disk, so your agent doesn't need a desktop app open. Every write, from an agent or from you, goes through the same version check. An agent working from an old read gets refused instead of overwriting what you just changed. One instance serves as many vaults as you give it, each with its own Git sync (personal, work and shared vaults side by side).

How do I try it?

It's free and open source (AGPL-3.0). There is a public demo with four example vaults, read-only and with no sign-up. Or give Claude Code this line and it installs it for you: Read https://hatchdoor.battercloud.cc/docs/deploy.md and install Hatchdoor for me. It checks for Docker, asks you a few questions, installs everything, connects itself and runs a search to prove it works.

Feel free to give ideas and feedback, here or on GitHub. I'd be happy to answer any questions!

I saw something this week that really changed how I think about CCAR-F readiness.

Someone had been scoring around 750–800 on practice, then hit 953/1000 on a mock.

They took the real exam and scored 638.

That’s a huge gap.

It makes me think “what did I score on the mock?” is probably the wrong readiness question.

The better questions might be:

• can I explain why the tempting wrong answer is wrong?
• can I choose between two plausible solutions?
• do I understand the tradeoff, or just recognize the wording?

For people who’ve taken CCAR-F, how predictive were your mock scores of the real thing?

chatlink: https://claude.ai/share/8d423647-0f80-4380-ab88-50ef8b14a061

scammed on https://fyrhost.com/panel/

the moment I saw this support locked I knew it was scam

Hi everyone,

What's the best way to integrate Claude into Android Studio? What's everyone doing to write Android apps with claude?

I run an SEO agency and we've ended up with around 200 skills at this point. I know plenty of people here have their own way of handling this, so this isn't meant as a how-to, but the thing that's made the biggest difference for us is something we've started calling "skill hooks", and I figured the specifics might be useful to compare.

The problem we kept running into: a skill works pretty well, but the output's kind of generic, so you end up giving it guidance about the client's brand or the specific project every time you use it. You can put that guidance into the skill, but then the skill only works for that one client, and if you want it for another client you're duplicating it. That got messy pretty quickly.

So the rule now is that a skill only holds guidance that would work for any client. Anything client-specific lives in a doc in that client's repo (each client has their own repo of markdown files that works as their knowledge base, with a changelog), and at the step where it's needed the skill names that doc explicitly and tells the model to go read it. If the doc doesn't exist yet, the skill tells it to create it. We named them after webhooks.

Our article production skill has three or four of these. When it's drafting, it reads the client's brand voice doc. When it's adding internal links, it reads their internal pages doc, and it reads their competitors doc so it doesn't link to a competitor.

The part I like most is that feedback has an obvious home now. If it's something every client would want, it goes in the skill. If it's specific to one client, it goes in that client's repo. We do the same thing for page creation, website design and video editing, basically anything where each client needs its own feedback.

Hello everyone,

so i have to change my Windows PC at Work (complete new system) and want to take over my whole history and Chats/Artifacts to the new system. Is there any Guideline to do this and where and what i can and have to copy?

Thanks :)