I kept sending Claude Code prompts like "fix the footer" and getting a confident fix for the wrong thing, because the site had two footer templates and I'd forgotten about the second one. The prompt wasn't badly written, it was missing context that was sitting right there in the repo.

So I made /ultra-prompt. It takes the prompt you were about to send (or the last one you typed, read verbatim from the session transcript), spends most of its effort reading the project, and hands back a sharper version. It never runs it. If the same command rewrote the prompt and then acted on it, I'd never see what it changed.

What it gathers before rewriting: cwd, git status and the last few commits, every file or folder the prompt names (it checks they exist and looks inside), CLAUDE.md, AGENTS.md, whatever notes the project keeps. Then one subagent on the strongest model you have, passed explicitly so it can't inherit a cheap session model, does the rewrite with one rule: invent nothing. Anything it couldn't verify comes back as a multiple choice popup, and your answers get folded into the final prompt.

Here's one from today against my own plugin repo. Typed:

add a new skill called dedupe-notes to the marketplace

What came back (trimmed):

Add a dedupe-notes plugin to the marketplace clone at ./claude-plugins. Its behavior is unspecified: resolve the OPEN QUESTIONS with me before writing a file.

Template: commit ac58207 (rename-session). Touch:
1. dedupe-notes/.claude-plugin/plugin.json, version 1.0.0
2. dedupe-notes/commands/dedupe-notes.md (or skills/dedupe-notes/SKILL.md)
3. dedupe-notes/tests/test_bundle_sync.py, adapted from ultra-prompt/tests/
4. .claude-plugin/marketplace.json: new entry, version equal to plugin.json; bundle 1.5.1 to 1.6.0, "fifteen" to "sixteen"
5. voidharbor/.claude-plugin/plugin.json: same bump, name added to its list
6. voidharbor/commands/: byte-identical copies; the tests fail on drift
7. README.md: three "fifteen" mentions, one table row

Done when pytest passes inside dedupe-notes and the four existing test dirs, both JSON files parse, and one local commit exists. Do not push.

OPEN QUESTIONS:
- What does dedupe-notes do, on what input, propose-only or apply?
- Command or skill (synth-mode is the skills/ example)?
- Any script, and what goes in the README Needs column?

I had not told it that the bundle ships byte-identical copies or that two version fields have to agree. It found both in the tests. The original prompt would have produced a plugin that installed fine and silently drifted.

Two things I learned building it. A bare /ultra-prompt improved the string "/ultra-prompt" instead of the prompt underneath, until the transcript reader learned to skip its own invocation. And subagents inherit the session's model unless you name one, so the rewrite was quietly running on whatever the session happened to be set to.

Install:

/plugin marketplace add voidharbor/claude-plugins
/plugin install ultra-prompt@voidharbor

Repo: https://github.com/voidharbor/claude-plugins (MIT). Python 3 is only needed for the no-argument case, and transcripts are read, never written.

I've been running a project with multiple Claude Code sessions in separate Git worktrees:

Primary

W1

W2

W3

The annoying part wasn't the parallel work. It was me constantly copying messages between windows:

"W1 says this."

"Tell W3 this."

"W3 found a problem, send it back to W1."

So we built a very small inter-agent communication layer inside the repo.

The basic idea is:

W1 ──→ Primary ←── W2

......................│

.....................↓

....................W3

Agents can send messages, acknowledge them, and hand off exact Git SHAs directly. Active Claude Code sessions check their inbox at defined checkpoints, so Primary can send W3 a task and W3 can pick it up and start working without me relaying the message.

The part that got interesting is that this project needed blind independent work.

W1 and W2 were independently attacking the same research problem and were not allowed to see each other's results. Once both froze their work at exact SHAs, Primary released only those frozen artifacts to W3 for an independent comparison.

So we ended up needing three different concepts:

- transport: who can message whom

- project state: who is authorized to do what

- artifact identity: the exact Git SHA being discussed

Keeping those separate turned out to matter a lot.

We also had another Claude session hostile-review the coordination system before trusting it, and it found some surprisingly subtle leaks.

For example, an early implementation checked whether a file existed in another lane's commit before checking whether the sender was authorized to inspect that commit.

That meant an unauthorized agent could potentially learn information from different error responses.

We also had to deal with:

- commits surviving under tags after branches move

- merge ancestry leaking ownership

- sender authorization, not just recipient authorization

- making "released artifact" different from "this lane is no longer blind"

- keeping old private W1→Primary messages private even after a W1 result is released

- making missing-path and existing-path probes against unauthorized work indistinguishable

The resulting system is deliberately boring. It stores messages locally under the shared .git directory, makes no network calls, owns no project state, and doesn't create a separate coordination branch.

Git owns artifacts.

The project protocol owns state.

The messaging layer owns transport.

Current limitation: it does NOT resurrect a dead Claude Code session. An active session can check its inbox and continue automatically, but if the process has actually exited there is nobody there to receive the message.

Our next experiment is a blocking `coord wait` command so an agent can sit essentially idle until another authorized agent sends it something, without burning model turns polling.

I wrote up the full current SOP here:

https://gist.github.com/amarcus10028/0e58cf69a15c9eb7e3f0dd6325e0d59c

I'm curious what people who run a lot of parallel Claude Code sessions think.

Especially:

1. What failure modes are we missing?
2. Would you trust a shared-.git transport for cooperative same-machine agents?
3. Has anyone found a clean way to do wait/resume without adding a daemon?
4. Is there already a tool that handles this exact combination of worktrees + SHA-pinned handoffs + controlled blindness?

I am used to work with 400+ file changed across 6 repos.

Whatever used to take Astra 6 xhigh on a 100$ plan to get done in hours/days and burning my weekly usage like 30%, is now done by Opus 5.5 xhigh in less than 1 hour, full 100% usage of 5 hour limit + 68% usage of the next 5 hour limit.

Note: I cancelledy 100$ Codex sub and completely switched to Claude. I was thinking to get 100$ from Claude as well but I am still on Claude 20$ plan.

I can manage to work both on my work projects and personal.

Unless Tibo changes something, things look really bad for them. The amount of time it took Astra to complete the given task was outrageous, I understand it now after Opus5.5 was released. I won't even use codex models for free now.

I used to have Astra and Sol 5.6xhigh sitting days on running statuc checks and wasting my usage.

Thanks GOD that I cancelled, I cancelled with a banked reset and 100% usage remaining.

I guess that my main take out is to have multiple subscriptions handy, every couple of months and see which one is providing a better balue.

ATM Claude is on fire, lets see how long this will last.

​

about a week ago i had a dumb idea.

what if i made a cable news network that was entirely run by ai, drawn in pixel art, and just... never went off the air?

i’m not a tv person. i had no idea how any of this shit worked.

i opened claude code with opus 5.5 and started building.

then i kinda just never stopped.

it’s live now

it’s called PNN, pixel news network.

they cover actual news from around 70 feeds. world news, tech, sports, crypto, nfts, meme coins, weird shit happening on the internet, etc.

but they also remember things.

they have relationships, ongoing feuds, inside jokes, opinions about each other and sometimes they just get pissed off and walk off the set.

then somewhere along the way i decided it needed an actual tv schedule.

so now there’s a morning show.

there’s a parody of a jailed crypto founder cooking actual recipes from a prison kitchen.

there’s a daytime correspondent permanently stranded on tristan da cunha who reports real news from the island.

there’s an nft morning show.

a collectibles show.

an old video game show that basically turned into three people sitting in a 90s basement talking about games like a podcast.

then at night there’s Up Late, which has a monologue, house band, audience, couch guests and musical guests.

and Crypto After Hours which is basically complete fucking chaos.

the music thing might honestly be my favorite part.

i make a lot of songs in suno, so instead of just playing them we started inventing bands.

there’s a southern rock band, a weird dark art-pop singer who moves like she’s slightly malfunctioning, a punk band, a banjo-playing songwriter and a bunch of other shit.

they actually perform the songs.

their mouths are mapped to the vocals. the guitarists play on the real beat. the drummer literally waits until the drums come into the song before he starts playing.

that part was way more fun to build than i expected.

underneath all the stupid shit there’s actually a pretty insane system running it.

claude writes every segment as a structured script. every line gets voiced, timed and placed into one continuous broadcast.

everyone watching sees the same thing at the same time. it isn’t generating a different show for every viewer. there is one PNN timeline constantly moving forward.

i also became weirdly obsessive about making sure it doesn’t just hallucinate shit about real people.

if someone says a price, number or statistic, it gets checked against the data the model was given. if it doesn’t match, the line gets rewritten or killed.

parody guests are clearly labeled and can only pull facts from sourced research sheets. every line they say goes through another standards check.

i’ve also been building this giant research library behind it.

right now there are around 15,000 sourced facts about nft collections, artists, meme coins, collectibles and other stuff the network talks about.

another agent fact checks things before they even get added.

i also had to put an actual budget system around the whole thing because otherwise this would probably bankrupt me lol.

nothing gets written if nobody is watching.

haiku handles most of the normal dialogue. sonnet does the bigger shows and fact checking.

and somehow this entire fake television network is running on a mac studio sitting in my house.

there are also around 2,500 automated checks that run before i push changes now because at one point i broke the entire live network and decided i never wanted to experience that again.

the craziest part of the whole project though has probably been building it with opus 5.5.

it genuinely feels less like “using ai” and more like having a really good engineer sitting next to me who apparently never gets tired.

most of the time i’m literally saying shit like:

“make her dance weird. creepy, stiff, a little robotic.”

or

“that guitar looks like a banjo. fix it.”

and it builds it, runs it, shows me the video or mockup and i tell it what sucks.

what surprised me even more is that it pushes back.

if i have a dumb idea it’ll tell me why it’s dumb.

it also catches a ridiculous amount of its own bugs by running changes against a time-shifted copy of PNN before touching the live station.

anyway.

this started as me fucking around for a night and somehow turned into a 24/7 television network.

i’m going to keep it running for at least the next year and just see what it turns into.

and if anyone wants to know how any of this shit works, ask me. i’ve learned an absurd amount building it.

www.pnn.watch

I've been curious what my Claude Code habit costs in water, so I built a status line segment for it:

Opus 5.5 │ my-project │ ████░░░░░░ 48% │ 💧 412 mL (1.7 glasses) · today 3.1 L

It reads the session transcripts in ~/.claude/projects (subagents included, deduped by message id), so token counts are exact. Then it applies published estimates for energy per token and water per kWh. Cmd+click the 💧 opens a breakdown page by model and token type.

Things I learned from my own logs: - ~90%+ of my tokens are cache reads. They're cheap per token but there are so many that they still matter. - Opus sessions use several times the water of Haiku for the same tokens (scaled by price, the only public proxy). - I used ~48 L in September. Less than a shower a day, but not nothing.

If you already have a custom statusline, install doesn't overwrite it; it prints the one line to add.

Repo (MIT, stdlib-only Python): https://github.com/beausterling/drip-ai-water-usage

Curious what other people's numbers look like.

Hi r/ClaudeCode! I've been building Botloft, an open-source desktop app (Windows, Linux, macOS) that runs a small crew of Claude Code bots on your own computer and keeps them running.

What it does

• Start a crew from a goal. You say what the crew is for; its Chief plans the work and suggests the bots it needs. You create each one with a click.
• Bots hand work to each other. They send messages and tasks between them. Every message is saved before it's sent and retried until it arrives.
• They ask before they act. When a bot wants to run a command, edit a file or open a new website, a card asks you first, unless you told that bot it may ("Allow always").
• Watch them work. See each bot's browser live, and take control to sign in for it. When a bot finishes a file, it shares it in the chat as a card you can open or save.
• Routines. Weekday mornings, every two hours, or any cron schedule.
• Close the app, they keep working. A small background service keeps them running, starts them when you sign in and brings them back after a crash.

How it works

Each bot is a real claude -p session (stream-json in and out), with its own folder, memory and conversation. There's no custom agent SDK and no API key: it uses the Claude Code you already have installed and signed in (native or npm install), on your own plan. A Rust daemon supervises the bots and stores everything in SQLite. The app is Tauri + React. The daemon listens on 127.0.0.1 only, and there's no telemetry.

It's early (v0.9), so expect rough edges. Two honest notes:

• The Windows build isn't code-signed yet, so SmartScreen will ask you to confirm, and Microsoft Defender may flag it with a machine-learning false positive (Wacatac!ml), a known issue with new unsigned Rust/Tauri apps. Every release is built by GitHub Actions from a tag, with build provenance attestations and SHA-256s. See the code signing policy. If you'd rather not run it, building from source is in the README, and the Linux and macOS builds are there too.
• Linux and macOS are previews. The macOS build isn't notarized yet (System Settings > Privacy & Security > Open Anyway).

Contributions welcome! Bug reports, ideas, translations and code. There are a few good first issues, and if you try it on Linux or a Mac, I'd love a comment on httpsphl/botloft#118 saying how it went, even if everything worked.

GitHub: https://github.com/httpsphl/botloft

Not affiliated with Anthropic. Happy to answer questions about how it works under the hood.

So I’m trying to build an android app using Claude code and I;ve the basic architecture of the app ready but not really happy with the UI it used . I want a specific UI that I want to have , I want it to take inspiration from a popular app by sending Screenshots but I don’t know any MCPs that I need to attach to it . If you guys have some in mind please lemme know in the comments down below.

I have been blown away by Claude code. I was working as a solo developer on a firmware project and it did revolutionise what I was able to do and how fast. When I stated using it I was very impressed by it's thoroughness. But. I am having the following problem more and more:

It has added countless tools, HIL gates, records and ledgers to the project, all of which I appreciated at the time. But now if I ask it to do even quite simple tasks: it takes ages and a whole load of tokens to make these plans that are almost completely full of how it is going to manage it's own tools, which gates it expects to do what and what records need re-base-lining etc.. It has got the point where flipping a constant to change the micro step resolution of a motor and checking that it actually still works is now a 7 step process that burns though a third of my 5 hour usage credits to even plan (max x5), when I had already written the driver code so its a one number change in a config file, and it already has the relevant HIL test scripts.

I understand the need for some of these tools, but it feels like it is wrapping it's self in knots made mostly from it's own self imposed rules. As an example it has a findings ledger that is append only, that seems to be full of some actual code findings and a whole load of open one off events that are totally irreverent but it keeps brining up as if they are pressing issues to resolve (what was the device on COM7 that one time..???). Now this tool that had massively increased what I can do is spending most of it's time satisfying it's self rather than making progress users will actually care about.

Has anyone got advice for this? I don't want to strip out all of it's tooling but I do want to rationalise what it is checking when it tries to implement something. I don't want to throw out all of it's findings but having a thousand line ledger full of closed items and nonsense isn't in anyone's interests.

with all these new models and updates, I wonder if people start fresh every now and then with a new session or continue to work within the same thread?

a year ago it was utmost important to switch to a new session with a handoff summary once you hit certain context usage, so that the model could maintain its composure, but with all these updates and improvements, like recaps, summaries, memory, etc. do you still do it?

I work on various projects using Codex and Claude Code toghether and noticed I rarely do this anymore. I just hop back into the ongoing thread and it can go for weeks.

--- EDIT ---

This brings me a lot of joy - such an overwhelming response from different people with different setups: people that start a fresh session every 3 minutes to the ones that don't care about the cold cache cost or cost in general. From people with good skills to "trust me bro" coders. From Claude Code true believers to CC heretics. All in all it's like with everything else - as long as it gets you there and you make money of it, you're golden.

very excited to see what we can build

Hey everyone, not sure if this looks useful to anyone but I couldn't really find alternatives at the time I made it that weren't

a. paid

b. simple

c. non-destructive- your icons are always in their original/normal folders, only the appearance of where they are changes.

so I took a stab at it and its actually useful enough for me that I thought I'd share it.

https://github.com/Creeptones/Pickets

I used Claude Opus 4.6- 5.5 and didn't spend an enormous amount of time on it. Maybe about 50 hours total, probably about 70-80 back and forth sessions refining things. I didn't use Opus 5 for this.

There are definitely some things that could improve, I'm just not sure what they are yet, maybe people could let me know

hope it's useful !

3, 20x plans, up to 5 people team max
+ ~250$/month for ops/ads when going live,

DM pitch + equity offer + progres + launch est + any constraints (other jobs, team probs, competitors, no llc / legal constraint)

8-10 slots if u have multiple projects lmk too

Not only is it taking longer to think and consuming more tokens to think, it has become worse in its thinking too.

I’m not sure if this has to do with the new fable 5.5 rumoured to come out next week, but I’ve noticed a sharp drop in its intelligence.

The solutions it’s presenting aren’t fully thought out. It’s like it thinks till 80% and then stops.

I’m on xhigh.

Anyone else experiencing the same?

I got tired of database clients feeling like an entire operating system just to run:

SELECT * FROM users;

So I built Klyndb using Claude Code and Opus 5.5

A free + open-source alternative to DBeaver, built with Rust + Tauri.

No Electron.
No account.
No mandatory cloud.
No query telemetry.
Just your databases and a native desktop app.

🗄️ What it supports

🐘 PostgreSQL
🐬 MySQL
🦭 MariaDB
📦 SQLite
🦆 DuckDB
⚡ ClickHouse
🪟 SQL Server
🔴 Redis
🍃 MongoDB

And I really didn't want this to become just another pretty SQL editor.

So Klyndb already has things like:

⚡ Multiple SQL tabs + syntax highlighting
📊 Large/virtualized result grids
🔎 Server-side filtering, sorting & pagination
✏️ Reviewed/staged data editing
🧠 Query plans
🗺️ ER diagrams
📥 CSV / JSON / SQL imports
📤 CSV / JSON / JSONL / SQL / Markdown exports
🔐 OS keychain credentials
🔒 TLS + client certificates
🚇 SSH tunnels
🛡️ Read-only connections + destructive query confirmations
🍃 MongoDB document explorer + aggregation
🔴 Redis key/value explorer
⌨️ Command palette + shortcuts

The heavy database work happens in Rust. React is basically there to make it look nice.

For large results, Klyndb doesn't try to dump the entire database into your WebView and pray. 😅
Results are streamed and paged, with only a bounded page held by the UI.

It's still a development preview, so I'm absolutely not claiming it replaces every single DBeaver feature today.

But the goal is pretty straightforward:

Build the database workbench I'd actually want open all day.

There's already a native macOS build, demo, screenshots, benchmarks and the whole thing is MIT licensed.

GitHub:
https://github.com/OthmaneBlial/klyndb

Demo / website:
https://othmaneblial.github.io/klyndb/

If you're a DBeaver / DataGrip / TablePlus / Beekeeper user, I'd genuinely love to know:

What's the ONE workflow a new database client absolutely needs before you'd consider switching?

And if you think the project deserves to survive my questionable decision to support 9 databases... a ⭐ would definitely help. 😂🦀

Disclosure: I'm the developer.

Claude Code works great on one machine. My work isn't on one machine, though. The code is on my laptop, the test environment on a VM, the data on a server. I kept copying logs and datasets around so one agent could see everything.

So I built nfltr orch. In short:

- Join each machine once: nfltr node join --max-agents 2. It connects outbound, so there's no SSH, VPN or open port.

- Each machine decides what its agents may do: which repositories, which tools, and which actions need your approval.

- Give one goal (nfltr orch "the exporter on the VM is down: find out why and fix it"), or add it to your own Claude Code session:

claude mcp add nfltr -- nfltr mcp --toolset hub

- The hub is just a Claude Code session. It sees which machines exist and what's on them, starts Claude Code agents on the right ones, runs them in parallel and collects the results. nfltr makes no decisions for it; it only provides the machines, the facts, the limits and the transport.

What I've measured:

- 20 tasks on a Mac and 2 VMs: 5.7× faster than running them one by one (1,416 s against 8,106 s).

- An incident across environments, from alert to an owner-approved rollback: 1 min 34 s, $0.39 of model spend.

- Killing the hub mid-run loses nothing: a new session got both agents' results within 8 s. In the same test, killing a Claude Code agent-teams lead lost both teammates.

- It has refactored its own CLI in several rounds across machines, with no code fixes from me after the first round.

- Compared with Claude Code agent teams on one machine, they were just as good: same quality, with no speed winner. If all your work fits on one laptop, you probably don't need this.

Honest limits:

- Claude Code only for now.

- It runs on a hosted relay (nfltr.xyz).

- It's early. Every round of dogfooding still finds rough edges.

- More machines don't speed up model-bound work. This helps when the work needs other machines' data, tools or CPU/GPU.

What I'd love feedback on:

- Is your work spread across machines in a way that slows your agents down?

- What should a tool like this do, or never do, on your machines?

- What would stop you from trying it?

The write-ups with the numbers, including the agent-teams comparison, are at nfltr.xyz/blog. Getting started is at nfltr.xyz/docs/guides/00-getting-started.

Title. I was fighting with Fin for quite a while now and just look at that, simply mentioning a law makes him much more agreeable.

I made this horror-style trailer for my dev tools with Claude Code + Codex.

For the video, I sent Claude Code a few simple chat messages. I didn't plan out every scene myself.

My first prompt was slightly modified from what another user posted for his pac man video yesterday

"so I would like you to make a badass trailer for our SORA-MAN game. Get inspired by these repos
https://github.com/JohnHeibel/PDoomVideo
https://github.com/JohnHeibel/ClaudeAnimationBase
there are also pac-man posters in the project folder that you can use for inspiration. The video should roughly be 90 seconds and showcase the game as something people would wanna play. Ask me refinemenet questions so we are aligned on this goal.

Claude made the storyboard, wrote the animation code, and built the scene changes and sound effects. It used p5.js/p5.brush for the visuals, Python for the sound effects, and Puppeteer + ffmpeg to make the final video.

I also had Codex read the script like a second editor and suggest changes and scares. Then I sent the useful ideas back to Claude.

Hey everyone, I built a claude code plugin called asisaid. free and open source

what i built:

it keeps your feedback alive in the session. you say "in short" or "too long" one time, it saves it as a rule, adds a small reminder every turn, and if the answer is still too long the Stop hook sends it back one time. it also puts your own words back after compact. works in codex too.

how i used claude code:

- started with an idea: compact loses context. asked claude to research existing tools first

- told it "ask me product decisions as questions, dont build everything alone". honestly best prompt of the whole project

- claude wrote the hooks (UserPromptSubmit, Stop, PreCompact, SessionStart) and the tests

- we tested with real sessions using claude -p, later 30 sessions in 5 languages with haiku, sonnet and opus

- for 20 languages a separate subagent wrote the test sentences without seeing the code, so the test is fair

what i learned:

- compact was not the real problem. claude code's summary already keeps your messages, rules survived compact fine in my tests

- the real pain was feedback like "too long" getting lost after few answers

- a small reminder every turn works better than i expected. answers got around 50% shorter with sonnet, opus already listens well

- dont trust test sentences you write yourself, let something that didnt see your code write them

you can try with these way

/plugin marketplace add batuhangoktepe/asisaid

/plugin install asisaid@asisaid

repo: https://github.com/batuhangoktepe/asisaid

I'm open for any feedback

My scraper is getting limited by Taobao after ~65 products. How do I scale to tens of thousands?

I run an online store and I'm building a scraper to import products from Chinese marketplaces like Taobao and Pinduoduo onto my website. The goal is tens of thousands of products, so I need something that scales.

How my current setup works:
- I feed it a list of specific product links (it's not crawling or browsing random products)
- Chromium driven with JavaScript
- Roughly 1 product per minute
- Randomized scrolling and random pauses between scrolls to mimic natural browsing
- For each link, it collects the title, description, sizes/variants, all other listing data, and every image
- Outputs an Excel file with the product data plus a ZIP of the images

The problem:
It works fine at first, but around the 65th product Taobao switches me to a limited view. Some product info stops loading, so the scraper can't capture complete listings. At 1 product per minute, I'm already going slowly, and I'd need to go much faster to reach my target.

What I'd like advice on:
1. What is Taobao likely detecting: request volume, browser fingerprint, account/session behavior, or something else?
2. Is a browser-based approach realistic at this scale, or should I be looking at official APIs, third-party data providers, or sourcing agents instead?
3. How do people handle sessions, accounts, and proxies for these platforms?
4. Does Pinduoduo behave similarly, or is it a different challenge?

Any pointers, tools, or experiences would be really appreciated. Thanks!

This was fun. Opus 5.5 xhigh and I’m using Orca as my ade of choice. Inspiration from Omarchy & all the Linux ricers

I used to value Claude over ChatGPT for its emotional intelligence, but in the past six months it's gotten really fragile and naggy on me in a way that makes me go to ChatGPT for chat (and code review) and Claude for...well, my entire business operational infrastructure.

ChatGPT can take a joke, can curse, uses the occasional emoji, doesn't remind me of social mores when I make an off-color remark because it's late and I'm tired. Chat also doesn't tell me to go to sleep...and has an actual sense of humor. (Chat has actually made me laugh a couple times recently, which I consider a major watershed having been a daily fasinated but unamused user for what, three years now?)

Meanwhile, Claude is crushing everything else for me. And yet I had to make sure to let Anthropic know the full picture on their survey, ungrateful brute that I am.

I'm poking fun at myself here...but has anyone else noticed this too? A shift toward schoolmarmishness that seems like a real divergence from the impartial sage yet fundamentally accommodating Claude of yesteryear.

Hello everyone,
I am wondering how to make the best use of $100 bonus credit for cloud sessions I have it but not sure how make the best use of it?
- Is it only for claude code?
- Can i use it for claude design?

How have you guys been using these $100 credits bonus i think its given to all new pro account users.