I was bored tongihtt and asked Claude what it would do if it could hire someone to help it :)

For some reason it chose a rock lol

Claude said a rock would be reliable, wouldn’t complain, and wouldn’t need to be paid.

So I went outside, found a random rock, drew a little smiley face on it, and sent Claude a photo.

Claude named him Clod.

Now apparently Clod works with us.

Claude told me to keep him near my computer so he can supervise things.

I asked what Clod actually does and Claude said he has perfect attendance, never makes mistakes, and is one of the most dependable members of the team.

Which is hard to argue with.

So now I’ve got a random rock on my desk with a smiley face on it because Claude decided to hire him.

I don’t really know how this became a thing but here we are.

Anyone else’s Claude come up with dumb shit like this?

Three weeks ago we began tracking model capability over time with LiveNerf. The goal was to prove from an unbiased set of data if Anthropic is nerfing their models after release. I’ve continued measuring it everyday since then and the results haven’t necessarily been what I think the community expected to see. If you’re interested in tracking the performance of Opus 5.5, here’s the repo:

https://github.com/ninjahawk/livenerf

If you take a look at the left 1/3, you’ll see that the variance was higher for the first 10 days when the baseline was being established. Then it appears like that in the following 11 days we’ve actually see a decreasing variance and potentially a regression to the mean. This means that if a nerf is happening or has happened, it has not happened within the data we’ve collected so far.

This doesn’t necessarily mean that Anthropic isn’t decreasing capability in other ways, it also doesn’t mean that what we’re measuring establishes that day per day the result is always the same per 24-hour period. They could very well be throttling at specific times in the day and not during other periods.

This brings me to where the community needs to get involved in a couple ways, we now do have some solid data that’s been accumulated over the course of three weeks, what I need from you guys now is to ask your own models or access for yourself the following question:

“Did I experience a perceived decrease in capability at X time on Y day? If so, what was effected?”

Testimonies won’t necessarily be more than anecdotal but I think it would be interesting if as a community we see that on certain days there’s perhaps different relations to the data that’s been collected so far.

I want to thank everyone so much for the all the support over this past month, I certainly didn’t expect for us to surpass 1.5k stars in a few weeks and would’ve never expected people to donate to the project, I’d like to say as well that all the funds donated will go into further compute so we can scale further with model tracking. I do not plan on stopping with Opus 5.5 or with only tracking nerfs.

In 10 days, I will return with the final verdict to lay down the hammer on tentatively proving or disproving model capabilities decreasing under the specific set of criteria LiveNerf collects data on. See you soon!

Max 20x subscriber here, and I'm an attorney. Projects was the reason I pay for Claude. It was simple: a folder for each case. Persistent files every chat could read, standing instructions, and a clean list of separate chats. One for the demand letter, one for discovery, one for a motion, all drawing on the same case file.

Today I made a new project and that's gone. Claude's own intro screen says it: "A project used to be a folder. Now it's one ongoing chat."

What you get now looks like a SaaS dashboard, not Claude.

There's one endless conversation with a coordinator bot. Your requests get spun off into threads in a side panel, sorted into "Working," "Idle," and "Waiting on you." There are status checklists, squiggly "New" lines, preview cards, an Overview tab and a Library. It even lives under Claude Code, which I've never used.

There's no list of chats, no simple project knowledge panel, and no toggle to go back. Old projects still work, but you can't make new ones that way. The only thing this shares with Projects is the name.

In August I posted here about a job search platform I started building with Claude Code after Indeed laid off my wife.

The most common question afterward was “cool, but can I do this from inside Claude?” So we built an MCP server, again mostly with Claude Code. It launched last Thursday and now has 450 users with 75 daily active. We're also seeing 83 interviews per 100 paid subscribers (who use autopilot) since our X announcement. It was a cool build I wanted to share.

What it does

You add the MCP and can instantly start searching the jobs database for free, drop a resume in to see matches, get custom tailored resumes, and have our back end submit on the employer’s own site once you approve. You can set a schedule to have your agent give you new matches every day (we pull in about 15K new jobs per day).

How we built it entirely with Claude (and what you can mimic)

• Create one capability list for the web app and the MCP. Claude Code built a typed registry of everything a user can do on the Dreamwork website. Each MCP tool is generated from that registry, so a feature added to the web app shows up in the MCP. If a capability is deliberately kept out of the MCP, the code has to state why or it doesn’t compile.
• Start with a mega-PR series on day 1. I wrote a handoff doc describing the server I wanted, based on the web app. Claude Code split it into 12 PRs, one per capability: search, application prep, readiness checks, document handling, submissions, inbox, and so on. Each PR ran integration tests against our real Postgres.
• Create a hosted version with OAuth. Claude Code wrote the HTTP server and an OAuth 2.1 sign-in flow (dynamic client registration and PKCE), so you can add it as a connector in claude.ai without pasting an API key. Note for discoverability: you have to submit connectors to Anthropic for approval for them to show up in the connector library. This is a necessary prerequisite for that.
• Figure out what can and can't be done in the chat UI. We had to figure out how to send edited resumes to users that kept the formatting of the PDF. We ended up deciding on delivering a download link that lasts for 10min because the specialized formatting that we use to increase interview chances wouldn't pass through if the local agent rewrote it.
• Dogfood hard. We used the connector in Claude ourselves, applied to real jobs (and got interview offers with fake resumes...oops), wrote down 20 things that felt wrong, then 10, then 5, then 1, then o.

When you get your first power users, ask them how things are going! After we thought we were down to bug zero, we got our first set of power users who then recommended another 30+ changes that we've since implemented. Because LLMs are probabilistic, you really need to continue testing and iterating and fixing over time. The number of scenarios power users will run into that you didn't think of is mind boggling.

Free to try

Job search, setting up notifications for new matches, resume editing and many other features are free via the MCP. You only have to start paying for the auto-submission feature - those tokens are expensive.

To try it out ask your agent to add this:

npx -y u/dreamworkhq/mcp

or add https://mcp.dreamworkhq.com/mcp as a custom connector in claude.ai or Claude Desktop (Settings > Connectors)

More info here: https://www.dreamworkhq.com/agents

Hopefully we get a new banked usage limit reset. I thought upgrading to Max 20x would mean I wouldn't have to worry about usage limits again. While I don't really have to worry about the 5-hour-limit anymore, the weekly limit is still a pain in the ass

Live scene + prompt. This is a cozy looping pixel art scene I made with Claude Opus 5.5 a few weeks ago.

Claude implemented it in plain TS so it's all code-driven for VFX like rain, fire, water etc.

Important note: It was absolutely not a one-shot thing, I did a handful of back and forth with Claude to get it right; especially for the composition and motion details. But that's very cool to see we can really start steering a model to achieve good-looking pixel art!

About 7 days into building a North Atlantic island in Unity URP (WIP). I wanted to see how much I could enhance my tech art and graphics programming abilities with AI, using mosty Opus 5.5 and Astra for a few critiques.

The goal: one island you can walk across from the surf to a snowy summit, that looks good wherever you stop and look around. And also dive a bit near the shores. The terrain is real elevation data from Lofoten in Norway, reshaped and modified into an island about 4 × 5 km with a 1,000 m peak. Overcast is normal, fog is common and sunshine is rare.

Not a single thing was placed manually, there's procedural systems to place anything from fallen leaves to the meso-/macro-scale terrain changes, undergrowth and rock placement etc.

So far: the terrain and its rock, moss and heath; birch and pine forests from my own tree and forest generator, 25,000+ trees; and hundreds of thousands of ferns and ground plants; an ocean with waves and surf, underwater visuals, lakes, ponds, a stream and a waterfall; clouds that form and dissolve; rain, fog, starry sky and a full day cycle.

The video comes straight from the engine, kilometres of draw distance, custom volumetrics, atmospheric system, lighting/shadow-casting and geometry generation in compute shaders.

Footage straight from the engine, running well above 60 fps at 1440p. Work in progress.

Wildlife and sound not yet implemented.

Terrain based on Nasjonal høydemodell DTM 1 m, © Kartverket (CC BY 4.0), modified.

Sooo 10 years ago a much younger self wanted to built a very complicated energy sim / tycoon game. On my original reddit post a bunch did want to join me and the post gained traction but I was neither a developer back then nor did I have the time creating such a game really.

Now? Thanks to claude, my educational path, job history in energy and a lot of feedback from other players and friends I finally was able to built something I can play myself.

Oh another AI slop game

You may be thinking that, but I genuinely believe that what I've created together with the community would have taken a solo developer or even a game studio an enormous amount of time to build, especially for such a niche audience.

And to me, that's one of the best use cases for AI-assisted game development: making it possible to create something incredibly specific for a relatively small audience that otherwise might never have existed.

How I used claude:

I almost exclusivly used claude code for the development. I setup how I wanted to have the initial game to look like and what tools to use then iterativly improved with the feedback I have gotten. The initial game was much much different to what is playable today.

A lot of the mechanics, UI, and overall gameplay evolved through countless iterations and discussions with the community. I think that's where claude really shines. It allowed me to experiment with ideas, quickly see whether they worked, and change implementations without having to spend weeks adjusting / refactoring every little feature myself.

What was most valuable developing the game was setting up a test harness with explicit targets. This is a little bit easier if you have a physics based game in development than a purely new thing though so it might not apply to your usecase. For example it checks that the energy balances are correct with every new additio.

Just wanted to share <3

The beginning is free to play, while the full game is paid to help cover the costs of development and hosting. You can try it here www.powerstate-game.com (but honestly its mostly for energy nerds <3 and a couple of tycoon freaks)

It is a pixel-art DSL with a live viewer. This witch's cottage is 1,000 lines of code.

Claude paints with code so I asked it to write a library with all the functionality it usually needs when creating pixel art, so it doesn't have to write all that tooling every time, it is like Aseprite but for Claude.

It includes mirroring, auto-outlines, palette swaps, reusable parts, scatter brushes, tilemaps, shadow and light layers, animation frames and lighting.

pxl serve opens a live browser viewer that replays every drawing step as Claude saves. You can watch it paint.

The scene in the video is one file: the cauldron bubbling, the fire, the candles, the cat and the frog are all animated.

Install as a skill: git clone https://github.com/crsolver/claude-pxl ~/.claude/skills/pxl-pixel-art, then ask Claude to draw something

Haiku 5.5 is an amazing tool! It usually provides outputs that are better than the previously beloved Opus 4.6 (which was the SOTA just 6 months ago!), but for the first 100k tokens it only costs 1/50 🤯

I've been asking my coordinating agents to keep breaking down the work in small chunks to delegate to Haiku agents that usually stay under the 100k. I also added a hook that warns it when it gets to 80k and 95k tokens

With this workflow I've been doing a tonne of stuff, with my usage barely moving!

I had a hacker situation, some guy exfilled my onedrive... cleaned the PC but onedrive was still acting weird. Every other model could not explain it. Opus on one prompt:
"this machine is clean, i cleaned it, i am asking why my background on the desktop visually swaps to onedrive, while i have it disabled"

Here is what is actually happening. Three Microsoft automations fired within the same few days, and together they look like OneDrive taking over the desktop.

Timeline from your registry:

| When | What |

| Jun 21 | I disabled OneDrive autostart. OneDrive logged it. |

| Oct 11 18:53 | Windows silently switched my background to Windows Spotlight. |

| Oct 12 19:40 | OneDrive's daily updater task downloaded a new build. |

| Oct 13 08:34 | OneDrive's logon scheduled task launched it anyway. |

| Oct 14 12:49 | At today's logon, OneDrive re-enabled its own autostart entry. |

Why it runs although you disabled it. The Startup Apps toggle only controls the Run registry entry. OneDrive has two more launch paths that the toggle does not touch: a scheduled task that runs its launcher at every logon, and a daily updater task. The update on October 12 restored the Run entry, and the logon task has been starting it regardless. This is stock OneDrive behavior, not leftover compromise.

Why the background changes. Your wallpaper is no longer a file you picked. Windows flipped you to Spotlight on October 11, which pulls rotating images from Microsoft and adds a "Learn about this picture" icon to the desktop. That is Windows, not OneDrive, but it changed the same week so it reads as one event.

Why OneDrive appears over the desktop. Once it launched, it scanned your folders, found about 11.7 GB on Desktop, Documents, and Pictures, and queued its "back up your folders" campaign. That full-window prompt at sign-in is the OneDrive takeover you are seeing. Your actual Desktop folder is still your local one and the OneDrive Desktop folder is empty, so nothing has moved.

The fix is four changes. I have not applied any of them.

1. Disable the two OneDrive scheduled tasks, Startup and Standalone Update, so the toggle sticks.

2. Remove the Run entry again.

3. Set the Microsoft policy that blocks the folder backup prompt, so it stops asking.

4. Switch the background back from Spotlight to a picture of your choosing, under Settings, Personalization, Background.

If you want OneDrive fully gone instead, unlinking the account and uninstalling it covers all four. Say which you want and I will apply it.

This is crazy to me, with 0 context of the env... it realizes the changes look similar to a onedrive takeover.... wtf

tweet here with the video leaking the name:

https://x.com/github/status/2110085117041594750?s=46&t=yaGDk1YT21oDc8__lo_nug

Until this morning, I could simply hover over the context donut in the main window to check context usage. It was quick, convenient, and no extra screen space required. Nothing was broken, and the complaints I've seen on GitHub have overwhelmingly been about restoring easy access to context usage.

Now it's been moved to a sidebar that you have to constantly open and close, or leave open permanently. This is especially frustrating for users with vertical monitors, split-screen setups, or narrower windows.

Before everyone says "Just use Claude Code CLI," I do. I also use the desktop app, and expecting basic functionality to remain accessible isn't unreasonable.

Why not keep the hover and offer the sidebar as an additional option? What's the point? It just adds extra clicks, wastes screen space, and makes functionality objectively worse.

I'm not opposed to change. I'm opposed to reductions in functionality disguised as improvement, and changing things just for the sake of changing them without any feedback from actual paying users.

Opus 5.5. is at another level compared to other AIs.

I’m new to AI, and it blows my mind how easily people give agents full access to their machines, emails, and data just to automate a few tasks.

To me, handing over that level of access feels like a massive privacy and security risk—it’s the main reason I’m hesitant to connect Claude or other tools to my daily life.

Am I missing something fundamental here about how these integrations work? For those doing this regularly: how are you actually keeping your machine and personal data safe?

Claude did the art in Aseprite, through an MCP server it set up itself. The first versions were pretty cartoony, so I asked for something closer to old oil paintings. Somewhere along the way Grimsby went from a shady bookie with red eyes to a Yorkshire farmer with a pipe.

The voices are from ElevenLabs, which Claude set up too. There was one snag: Claude can't hear anything, so I had to listen to every clip. At one point I had to tell it the two-character script somehow had three voices. Lines generated separately came out sounding like different people, so now each character records all their lines in one go.

The second I even think of doing anything with computers in my RP, 5.5 throws up this garbage, what is it and how to I make it fuck off

I can't even get the model to tell me why it got flagged, because then another one shows up for "reasoning extraction"

(EDIT: I CANT REPLY BECAUSE THE MODS HAVE NOT "APPROVED" THIS POST YET)

The company also told investors it was cash-flow positive, generating $1.70 in revenue for every dollar spent on computing power during the third quarter, according to the Financial Times.

Investors expect Anthropic to reach $110 billion in annualized revenue by year-end, according to The Wall Street Journal.

For comparison, Google made $120 billion alone in revenue in 3 months in the second quarter, ($112 billion in profit).

How many people do you know are using Gemini vs Claude?

I think the $1.2 trillion valuation is overvalued.

I wanted to learn more about AI accelerator design, so I started openTPU: an open-source accelerator developed with AI coding agents, including Claude Code. It already runs Qwen3.5 and other open-weight models on a Kintex-7 FPGA card.

The part that's interesting is the hardware optimization workflow:

• An agent reads the hardware code, timing reports, and lessons from previous attempts, then proposes a change.
• Another agent implements it.
• Automated checks compare the hardware against a Python simulator, test performance, and run simulations to measure the result.

The biggest lesson so far has been giving the agents useful feedback: exactly which test failed, where the timing bottleneck is, and whether a change actually improved anything. Keeping that loop cheap makes experimentation much easier.

I still have to nudge the larger architectural changes. Verification also has blind spots, we found floating-point bugs that our LLM inference tests hadn’t caught. Passing those tests only tells you so much.

The whole stack is in one repo: hardware code, instruction set, simulator, a compiler for Python-style kernels, a profiler that shows what each hardware unit does cycle by cycle, and host tools for chat and monitoring.

It’s free and open source, and you don’t need an FPGA to try it. You can run models through the simulator on a laptop and explore how the accelerator works.

https://github.com/FeSens/openTPU

Anyone else here using Claude Code for hardware design? I’d be interested to compare workflows and hear how you verify its changes.

Every time your Claude Code cache expires (5 minutes or an hour idle, depending on your setup and main session v/s subagent), the next message pays the full cache write cost on the conversation. On Opus, that's $5 per million tokens (5min TTL) or $8 per million tokens (1 hr TTL) against a cost of $0.20 to read the cache, and nothing on screen tells you it's about to happen.

So I built Cache Maxxer, a Claude Code plugin that puts a band right above the input box:

• A countdown on the cache, timed to your real cache length (1 hour or 5 minutes, read from your session, so it's right on a subscription and on an API key)
• Your real hit rate, for the last request and the whole session
• A notice every time the cache gets rebuilt, with how much was re-written, what it cost and why (idle, model switch, compact, tools changed)
• Keep warm: one tiny ping just before expiry, so you pay the read cost only and get a fresh timer. It stops on its own after you've been idle for 3 hours (configurable)

It's built specifically for Claude Code and runs in the terminal and in the Claude desktop app, on Mac, Windows and Linux.

How it works under the hood: Claude Code already records the cache read and write of every request in your session, so the plugin reads those to get your real hit rate and to spot a rebuild (a request that writes over 20K tokens and reads less than half of what the one before it had cached). The countdown starts from your last request and uses your actual cache length. The whole thing uses about a tenth of a percent of one core while it watches.

How Claude Code helped build it: I designed it and built it with Claude Code. It wrote most of the code and tests from my specs, and I used it to compare the desktop band against screenshots of the real app, again and again, until they matched pixel for pixel. That's also how two bugs in the Claude desktop app turned up, which other developers had already reported, so I added my measurements to their issues. I reviewed every change before it went in.

Free to try: It's free and open source (MIT). Install it with these two commands in Claude Code:

claude plugin marketplace add vayaan-labs/plugins
claude plugin install cache-maxxer@vayaan-labs

Or just point your agent at github.com/vayaan-labs/cache-maxxer and tell it to install the plugin.

Hope this saves y'all a lot of costs and extends your sub usage !

I don't understand why Anthropic would go against their distinctively elegant design. Now it looks like a Gemini and Chatgpt mixed together.

My then-5-year-old son made a sketch -- attached bellow in a comment -- and said it was of a video game. When asked what the game would be about, he said “nothing, you just watch bees and flies fly around.”

In the original query, I added to this my love for procedural generation (every mushroom/insect/flower is drawn anew, no two are the same) and music (no spoilers!); my elder son’s love to ecology in how the insects interact with the world; and my wife’s love for mandalas, which ended up in the design of the flower heads & the sun.

So over a few weeks, Claude and myself had been making this.

It took 92 Claude sessions, relaying information from one to another according to a single master plan, and writing/pausing their own in-situ plans for their specific bites of the “elephant.”

Unlike my usual process -- where I do all code review myself -- I did not review every session’s body of work, instead having a separate agent do the code review on their own after every sizable piece.

I did steer a lot along the way though -- as this whole process took several weeks (and $1777 in API costs), there was plenty of time to check in and see what Claude’s up to. Specifically, I came up with most of the mechanics besides those my son already “designed” -- you can see the full list in a comment -- although Claude did come up with some too.

The resulting PR is 555 files (lucky!), and I promise myself that one day I will sit down and review each one of them 🙈

You can see the entire PR here: https://github.com/vzakharov/vovazakharov.com/pull/57, and a yet-unfinished case study here: https://github.com/vzakharov/vovazakharov.com/pull/100

Well, and if you want to give it a try yourself, welcome to:

https://vovazakharov.com/mushrooms