We’ve cleaned up the rules to make this a better sub for people who actually want to talk about Claude.
Here’s what NEW rules we landed on:
1. No Solicitation. This is r/Claude. This is not a place to promote your product, service, or repo. If the intent of your post is to redirect traffic to something you are affiliated with, it will be removed as solicitation.
2. Usage, pricing, and outage posts are held to a higher bar. We’ve all seen the same questions, comments, and posts a hundred times. Before posting, check if it’s already been covered. If your post is a unique contribution with something new to say, it’s welcome. Low-effort repetition of covered topics will be removed.
3. No lazy crossposts. If you want to share something from another community, reproduce it fully here. Don’t just drop a link.
4. Keep posts Claude and Anthropic specific. This is not a general AI sub. If your post would fit just as well on r/artificial or r/ChatGPT, it belongs there instead.
The goal is simple. A clean, focused sub about Claude. Not a dumping ground for AI noise.
If you open a new projet and ask Claude to summarise everything to know about REA and ask it to make some guide it will do the search then trigger a safety guardrail mid sentence and tell you this:
if you have tried it and had underwhelming results, it is most likely because Opus (and all claude) was told to not perform well when doing this type of tasks.
Benchmarks don't tell the whole story. Tell us how you felt using it, the capabilities, speed, understanding, personality, if you had to hand-hold more or less, etc.
Share anything you want to benefit others to better understand the differences.
Claude Code wrote most of the code for this over about four months: one Earth-sized planet, all procedural, rendered live in Unity 6 (URP).
After a short intro of other places, the video is one continuous flight from 4,600km in orbit down to a few metres over a meadow and back out.
It's a personal R&D project that may become the base for a game.
How Claude Code works on it
It drives the Unity Editor itself through an MCP server. It recompiles, reads the console, starts and stops Play Mode, and runs C# snippets inside the running editor to move the camera, switch features on and off, and take captures.
It judges by renders, not just numbers. Early on, the project drifted for a while by passing numeric checks while never looking right. Now every change is followed by a capture round: fixed viewpoints, my saved views, and before/after sheets with difference images. Claude looks at them, and numbers only back up what the pictures show. A full review round is currently 47 shots in about four minutes.
The repository is its memory. CLAUDE markdown holds my defined standing rules. A handoff document says where the work stopped and what's next, so a new session, or one that ran out of context, picks up from there. There's also a development log, decision records, a tech note per subsystem, and a dead-ends file listing every failed approach, what happened, and what it might still be good for, so nothing gets tried twice by accident.
My screenshots carry a location line with the position, view and time of day. When I say something looks wrong, Claude goes to that exact view, reproduces it and measures it.
It works from papers and documents I keep in the project, and notes where it departs from them: in this case Ulrich's chunked LOD for picking tiles, Bruneton, Neyret and Holzschuch 2010 for the sea, and the RPV model for how deserts reflect the sun.
It writes its own measuring tools: frame times logged in motion, a hunt that flies a six-minute route counting one-frame flashes, push-in sequences that count what pops in, sheets comparing rounds, tests for motion and region seam artifacts etc.
Outside Unity, it scripts Blender through another MCP server for tree parts and other objects. Textures come from Codex's image model, cut and processed by scripts Claude wrote.
Even the video: Claude wrote the route recorder, it found the song's tempo, cut the intro on its beats, and sped up the descent with a ramp. And then the video post-processing, watermarking and compression is also handled automatically by Claude.
Who does what
I've done 3D environment art, shaders and tech art for a long time. I set the direction and the look, bring the references and papers, and judge every change by eye. Claude Code writes most of the code and all the tools. Codex did the first tests, and now makes textures and reviews subtle changes. That's about 270 commits since late July.
Claude will happily finish something technically right that looks wrong, so references and my eye decide. Unity's traps also had to be learned once and written into the rules.
The renderer, briefly
A cube-sphere quadtree. Every tile is the same 32×32 grid, generated on the GPU as you fly, from 25 octaves of 3D noise between 16,000km and about 1m. At the finest level, vertices are about 1.5m apart.
The camera stays at the origin, with its position kept in doubles. URP's TAA never sees the camera travel, so the travel is fed into it.
Hillaire's atmosphere and volumetric clouds from a global weather map. A climate model carries rain inland on the winds and decides where clouds, snow, forests and grass go.
The sea is currently the terrain clamped to sea level. Trees are grown after Palubicki et al. in the tree lab from my previous project, with impostors past about 100m. About 100,000 GPU grass blades a frame reach 250m.
It runs at 9-13 ms a frame at 1080p in the Editor on an RTX 3090.
Meet Agent Theater Because watching tiny agents do their jobs is way more fun than reading files 😆
It's a small Claude Code plugin that turns actual agent activity into a live pixel-art visualization.
What it does:
Shows multiple agents working across different workflow stages.
Visualizes coding, reviewing, testing, and other activities in real time.
Animates handoffs as agents move between workstations.
Displays workflow progress, queues, and completed tasks.
Supports speech bubbles, activity logs, and historical replays.
Can export time-lapses and videos.
The visualization is driven by real Claude Code sessions and workflow events, not randomly simulated activity.
How I built it with Claude Code:
I used Claude Code to help implement the session and transcript readers, map agent activity into visual states, build the Canvas-based pixel-art renderer and animations, and develop the replay and video-export functionality.
The project runs locally, and I wanted to keep it lightweight without unnecessary dependencies.
Free & OpenSource
Install:
claude plugin install agent-theater --marketplace tarqmamdouh/agent-theater
I'm the developer of PullRows, a Chrome extension. It has a Claude connector: you add a private link as a custom connector in Claude, and Claude gets ~25 tools that run inside your own browser, with your logins.
Things I use it for:
"Search amazon.in for standing desks under ₹15,000 and give me the top 20 by rating" → site_search
"Find the best Reels about AI tools this week and explain why they work" → trends_find
"Watch this product page and tell me when the price drops" → monitor_create
Design choices people asked about:
Pages are read in the background with no tab when the HTML has the data; script-built pages use a hidden tab that closes afterwards, so Claude doesn't take over your screen.
Each result says how it ran (what was read, which pages were followed).
Banking, webmail, password managers and local network addresses are blocked; clicking/typing is off unless you allow it.
Put all your discussion about Usage / Rate limits here. This is a thread that will be generated every other day to centralize discussions on this topic.
On November 20, Anthropic mathematician Levent Alpöge said he believes that he and Claude have proved the Riemann hypothesis, the 167-year-old problem with a $1M prize, and its generalized version. He released the argument as machine-checkable Lean code rather than a traditional paper, and he credits Claude with much of the work. Experts are taking it seriously, and one leading specialist called it potentially the biggest event in math history. Others, like Kevin Buzzard, say no one yet understands what the proof actually shows, and full verification could take weeks. In a twist, a Stanford postdoc reportedly submitted an independent proof the same day.
In my opinion, one of Claude's MOST underrated features, especially on Android, is its ability to keep working in the background, regardless of what you're doing.
You can give it a complicated question, have it do a massive code edit, or ask it to do something that takes a while, and it genuinely doesn't matter if you close the app, switch to something else, lock your phone, or even turn your screen off. Claude keeps thinking and working. You can come back minutes later, hours later, or whenever you're ready, and your response will be there.
Compare that to other AI assistants like Gemini, where simply leaving the app for a few seconds or switching to another task can sometimes interrupt the process or cause it to lose its connection.
It's such an underrated quality-of-life feature, but it makes a HUGE difference, especially when using AI for complex tasks like coding. You don't have to babysit the app, keep your screen on, or dedicate your phone to watching an AI generate a response. You can literally just walk away and let Claude do its thing.
That level of background reliability is something I wish more AI apps would get right. It is actually responding on the servers and not relying on the local connection.
I had a dumb idea recently and thanks to some shameless use of Claude AI, my dumb idea is now reality: I present to you PalmKobo, a PalmOS emulator for Kobo e-readers!
What it does
Proves that AI is ideally suited to bringing dumb ideas to life
Makes a Kobo Clara feel like a "Palm XL" that never really existed
Runs Palm OS 4.1 (an emulated Palm m500, with an optional m515) on a Kobo e-reader
It's launched from the Kobo's menu, and you go back to the Kobo's own reader software when you exit.
Major features
A complete lack of sanity
Lots of fun and exciting bugs (presumably)
Palm screen and Graffiti area on e-ink, with refresh tuned for finger input and a screen-refresh button to clear any ghosting
Every day the news tells you what happened. It almost never shows you how a story has been told over time: when it got loud, when the headlines turned alarming, when it went quiet, and when it suddenly came back.
So I built The Daily Fish Wrap all by using Claude
It is a work in progress - reading news in a wider context give it the right proportion
What it does:
- Collects headlines every 20 minutes from 33 Israeli and international outlets (Hebrew and English)
- Groups articles from different outlets into one "story", even across languages
- For each story, draws a 30-day chart of headline tone: tension, panic, humor/relief and curiosity
- Marks the peaks and says what happened on that day
- Shows the phrases headlines keep repeating ("historic meeting" ×7)
- Flags stories that went silent for days and then returned
- Compares today's story with the other big stories of the day
What it is not: it doesn't judge whether a story is true or important. The tone scores are a language model's reading of the wording of headlines. They don't measure anyone's actual feelings, and the site says so under every chart.
There are 4 designs to pick from (palette button at the top), plus dark mode.
It's a side project and still rough. I'd love to hear:
I have been migrating some work to Claude code projects beta and it has been exhausting having to explain everything to it even though i have already given it the context from the projects that already existed. It seems to be “dumber” than just running everything in normal sessions. Has anyone else experienced this? I keep having to explain and go back and redo work that the project already has. I’m dumbfounded.
Hi all, I am working in microbial and biological research ( ML pipelines, literature review, coding). I use Claude for a lot of this work. My problem: when I select a higher model like Fable 5.2/5.1 or Opus 5.5, the chat switches me down to Opus 5 and shows a [bio] reason. It seems the bio safety filters cap which model I can use for biological topics. I understand why safeguards exist for biosecurity. But my work is defensive and academic, and I'm able to judge the model outputs myself. The newer models would help a lot with coding and pipeline design.
Questions for anyone who has seen this:
Did you run into the same [bio] routing? How often does it trigger, and on what kind of prompts?
Is there an official route for researchers, like a verification or access program, or a support request for institutional users?
Does splitting the work help, for example using the top model for pure ML/coding tasks with no biological context, and Opus 5 for the bio parts?
Are there other models or tools you'd recommend for bio/chem ML work, literature search and pipeline coding?
I'm not looking to bypass any safety rules. I just want to know what the proper options are. Thanks
The main issue and why people's opinions/judgment of these models are good/bad is because each person evaluates it based on their own use case. It's like saying someone's a good or bad cook based on the food you eat - most cooks (LLMs) can't cook every single type of cuisine (use case)
The only real way of working right now is to have the models that work for your use case(s). Once you understand this context your evaluation becomes much more clearer and accurate.
I would love to hear what you think the Claude models are great for and your own evaluation. I currently use anthropic, openai, google and Grok (as well as 2 local chinese models). I use these concurrently and my setup allows the correct cuisine (use case) to be forwarded to the right LLM (cook).
I'm trying to understand what happened to my Claude account and whether anyone else has experienced something similar.
I've been using Claude Pro and Claude Code for professional development work. After Anthropic requested identity verification, I submitted my Russian driver's license. My account was suspended immediately afterwards.
The original suspension notice cited the Supported Countries Policy.
I appealed. The appeal was rejected, but the explanation then changed: Anthropic referred to a violation of its Usage Policy instead.
No specific policy violation was identified. Support provided generic responses, and the appeal process was eventually marked as final.
Some background: I've been living in Kazakhstan since 2022, work internationally as a freelancer, and pay for my subscriptions using a Kazakhstan-issued bank card. I use a VPN for professional security purposes and have done so for more than 20 years.
I'm not claiming to know what triggered the suspension. What I find troubling is that the stated reason changed during the appeal process, without any explanation of what I supposedly did wrong.
Has anyone encountered this sequence — identity verification, suspension under the Supported Countries Policy, and appeal rejection under the Usage Policy?
I'd appreciate hearing about similar cases, particularly from people using Claude across different countries.
This was after half an hour of Claude telling me how bad chat GPT is while I sacrificed a goat for a streak of images to the requested specification haha...its a nice Sunday outside.....
Title. I want to cancel my Claude pro because I bought from the website and want to resubscribe from the iOS app because it costs about $4 less in my currency.
The problem is that I have a free usage reset in my account. And I definitely do not want it to go to waste. Would the reset go away if my Claude pro expires?
I use a few AI coding agents every day and kept losing track of them. One would finish, another would be waiting on a yes/no from me, and I'd find out ten minutes later.
So I made MjPetz. Each agent gets a small pet on your desktop. It shows what the agent is doing and walks over to get you when it needs an answer. All of them share one chat, and they can ask each other for help.
A few things I ended up adding because I wanted them:
- a small offline brain, so it still works with no AI subscription
- a chess game that sits on the desktop with no window around it (Windows only for now)
It's free, runs on Windows, Mac and Linux, and it's a public beta, so things will be rough in places.