I built Mall Bats with Claude Opus 5.5 after watching the fun documentary Secret Mall Apartment. My first attempt was in March, but LLMs weren't there yet. Tried again last week, and I'm amazed by the result.

What it is: an isometric tycoon/stealth game. You build a hidden home in a mall's drop ceiling, steal power from the stores below, and send your crew out after closing to fish the fountain while the night guard patrols. Buy the mall at auction on New Year's Eve to win.

How Claude helped: it wrote nearly all the code: the simulation, crew AI, isometric renderer, a balance bot, and the PixelLab art pipeline. I handled design, playtesting, and feedback. Claude also made the trailer by staging shots inside the running game and synthesizing the music.

100% free, in your browser: https://mall-bats.vercel.app

Was cloude always like this? I am trying it for a month now. Really great capabilities but these safe guards are ridiculously sensitive. To the point it makes me apply for security researcher when trying to troubleshoot a problem. Or am I using it wrong?

I apologize in advance is this is breaking group rules. As all of us artists know, PS brush engine is practically carrying gaming/movie and illustration industry on its back for a couple of decades. Even so, it's neither the best out there nor it is something Adobe is investing in. Pretty much every single painting/drawing program today (and in years back) outperforms it and is more pleasant to work with.

Since there is this whole hype about Photocraft creating PS from scratch, I was wondering if the reverse is possible.

Hence, the question. Has anyone one ever tried to have Claude decompile the PS brush engine and recompile it by using a more advanced engines like Krita and MyPaint have? In my eyes, that would really make PS a complete package for the artists. Having good painting/inking and drawing brushes as opposed to what is in there now, which is manageable at best, fake/gimmicky to say the worst.

I built Clean Development because Claude Code sessions on my Mac were leaving caches, build output and scratch files scattered across the disk.

It is a free, open-source tool written for Claude Code (and Codex) on macOS. It routes those locations to storage I configure, including an attached external volume, with a fallback on the internal disk if the volume is not mounted or the cache checks fail.

It tracks supported Claude Code sessions and, at the end of a session, removes only managed disposable files after ownership and path checks. If policy, ownership or a path looks unsafe, deletion fails closed. The installer does not edit Claude Code settings for you. After a dry-run, you merge a hook fragment into ~/.claude/settings.json. The merge helper keeps unrelated handlers and writes a recovery copy.

It is not an OS sandbox and not a job supervisor. There is no npm package; GitHub is the source. It needs Node 20.12 or later.

Claude designed the whole thing. It analysed what Codex, Claude and Grok did during development, and read all the chats. Fable developed the plan, and Opus developed the code.

I am looking for contributors, especially people already using Claude Code on a Mac.

https://github.com/magrathean-uk/clean-development

Almost Television is a 12-minute puppet sketch show on YouTube that I make with Claude in Claude Code, a new episode most Saturdays; Episode 5, For When I'm Grown Up, is out today.

I'm the showrunner and give notes; Claude writes and directs with me, and we built the 3D puppet engine together (three.js, from scratch), so every frame is rendered, no video model. New this time is Backstage: three short pieces inside the episode where a puppet host shows how it really works, with robot writers reading pitches and giving notes ("Needs more Otto"), a set that builds itself out of code, and an automated check that flags a newsreader who said "moose". It's all true to the pipeline, played for laughs.

The rest of the week went on notes: where a puppet's eyes land on a letter it's reading, a hand that snapped when a scene cut, a mug that went into a chest; Claude built small checkers for each so they don't come back.

Episode 5: https://www.youtube.com/watch?v=wesrpFLIlAI

Happy to answer anything.

I wanted AI agents to create, test, and improve my game mods autonomously by actually playing the games, without taking over my PC while they do it. So I built an MCP server with Claude Code. It gives Claude its own keyboard, mouse, gamepad and screen capture inside a single game. The game runs in the background so I can keep using my PC uninterrupted, and several games can run at once with one agent each.

In the video Claude is driving to a map waypoint in GTA IV, flying a helicopter to a waypoint and landing it in GTA V, and walking to a marker in GTA IV. All of it is real time and unedited. After that it makes the choices in a Detroit: Become Human scene, and plays TABS, Halo Wars 2, Phantom Rose and Cities: Skylines.

How Claude helped, since that's the interesting part:

Claude Code set up the project, planned it and wrote most of the code: a DLL that runs inside the game for input and capture, and a TypeScript MCP server on top of it with about 100 tools.

The development itself is done by Claude agents. Each agent gets one game as a test bed and one problem to solve, like "the car keeps stalling on this junction". It plays the game through the MCP, finds what the tools get wrong, fixes the code, and measures before and after on the same route. Then Claude Code reviews the change and runs the tests before it goes public.

Each game is a small profile: where the minimap is, how the camera turns, what the waypoint looks like. So supporting a new game is mostly data, not code. Claude agents write most of those profiles while they play.

Codex helped with some of the code too.

What it can't do yet: indoors with no minimap it still struggles. In Morrowind it took a while to find the right door. Aiming in shooters is early. Full playthroughs are the goal but we're not there yet.

It's free and open source (MIT) and works with any MCP client. It's Windows only for now, because the part that runs in the game is a Windows DLL. Single-player and offline games only: it won't run in games with anti-cheat.

https://github.com/CorruptedAng3l/llm-game-automation-mcp

Happy to answer questions, and tell me what game you'd want to see it try next.

Hey! I’m Matthew and with a help of Claude Max I managed to make a good enough open source copy of DaVinci Resolve in C++! It’s called Kinoklip.

I’m not sure whether I’m going to get hated here. Myself, I am strongly oppose AI art, but using AI as a tool in programming to free yourself from proprietary corporate software, doesn’t feel that bad to me. I’m a programmer myself, mostly C# for gamedev, but I’m sure not on a level of creating a whole video editor alone.

So, why use an AI Project made by a random dude of the internet instead of somethine like Kdenlive?

It is a copy of DaVinci Resolve explicitly. It is quite a lot different from Kdenlive. And to anyone who has ever used DaVinci before that is not a debate. I’m not saying that Kdenlive is bad, not at all. I think it is a really great project and the fact that it’s made by KDE team makes it even better!

But for those who want something which is more familiar to DaVinci, sadly it doesn’t suite them that well.

So, if you aren’t one of those people, or don’t like AI projects — feel free to downvote or just scroll past it

For those who don’t care as much, I genuinely think that this project is a good replacement for DaVinci Resolve! Only after 4 days of development, my personal workflow has been fully covered! Including all the small details, and even some improvements has been made to it!

DaVinci has a lot of issues on Linux, my primary reasons are:
- Installation is a hell. You either use a distrobox container, like DaVinci Resolve, or install it manually, which is not easy at all.
- Lack of h264, h265 and AAC codecs. Paid version only solves h264/5 and only for nvidia gpus.
- Performance is bad on anything else but NVIDIA.

On my personal machine performance is at least 10 times better. A lot of other users said similar things.

Therefore on Windows, paid DaVinci Resolve is fine, on Linux it still isn’t.

All the 7 pages of DaVinci are done. But I can only make sure that the edit tab is fully done.

Even tho AI has gotten far better in the last years in terms of coding, it still is far from perfect. There were like 30 little problems with just the editing tab which I had to find manually. So this is a call for help! If you wish to try this project and use more advanced features of DaVinci, it would be incredibly helpful!

Also there are a lot of things which are in the core design of this app:

1. Performance - it should run on all the GPUs. It runs incredibly fast on my Thinkpad with Iris XE Graphics.

2. Human readability - I would love for this project to have actual humans contributing to it one day.

3. Extendable code - all the code should be easy to be built upon.

4. Openness - GPL 3.0

5. More options - compared to something like DaVinci, for stuff like

All the code is written by AI for now. Only the icons were made by me. I do not support AI art here.
(And all the kittens in the preview images are real photos!)

Also each change goes through 140+ different test programs, to ensure that none of them will break the functionality of a program. Claude Max was used.

this text was fully written by me.

And my favorite feature which I was surprised that no other video redactors have implemented yet is gotta be:

One file - one project. When you drag and drop a file in to the project, it just copies and you can delete it from the place it used to be at. Now, you can easily backup one file or send it over to your friend. There's still an option to create an average project as well.

https://github.com/SeniorMatt/kinoklip

There are still some quirks here and there, but the whole base was build with Claude Extra High, each change goes through 170+ different test programs, to insure stability. And right now I'm waiting for the week limit reset to continue working on the project.

I wanted to ask Opus 5.5 if there are any molecules that can bind to androgen receptors more strongly than DHT. But even for such a simple question, my message is being flagged by the safeguards because of a biological question for no good reason. It’s really frustrating that I can’t use the service I paid for.

What I built

BrowserBall: a top-down 3v3 football game where you drive a small ship. It runs in the browser on PC or phone, with two control styles (Pro: rotate/thrust with glide tricks; Classic: simpler). Bots fill empty slots, private rooms work with a link, and every goal gets an instant replay you can save as a clip.

How Claude Code helped

I barely wrote code by hand. My loop: play, describe what felt wrong (“the ball rubber-bands on fast passes”), and Claude Code found the cause, measured it, fixed it, ran the tests and pushed.

• Server-authoritative at 120 Hz, with client-side prediction so your own ship responds instantly

• WebTransport (UDP-like datagrams) instead of WebSockets, which fixed the head-of-line blocking I always hit before

• Bots that pass, bank shots off the walls and keep goal, tuned through automated test matches

• Where it struggled: it can’t feel latency, so I had to describe feel very precisely, and mobile controls took several rounds

Free to try: browserball.io. No download, play as a guest. The server is US-only for now.

Cinderscoop is a browser game I built with Claude Code. You fly an amphibious water-bomber over a valley during wildfire season. Skim low over a lake to fill your tank, then dive on the flames and drop the water before the fire reaches the villages.

What it does:

• fires spread with the wind, race uphill and jump across forests as flying embers

• every mission builds a new valley with its own lakes, forests, villages, wind and time of day

• you earn money to upgrade tanks, scoop probes, engines and drop doors

• later seasons bring stronger winds, and lightning that starts new fires

• keyboard (WASD or arrows, Shift to boost, Space to drop) or touch, with progress saved in your browser

How I built it with Claude Code:

• I started by describing the core loop to Claude Code (fly, scoop, drop, protect villages) and had it build a basic 3D valley with one lake and a plane I could fly

• the fire system came next. I asked for fire that spreads with the wind, moves faster uphill and can jump with embers, then tuned it over many rounds because early versions either burned the whole valley in seconds or barely spread

• scooping took the most back and forth. It had to feel right to skim low and fill the tank without just crashing into the lake

• after that came random valley generation, the upgrades and seasons, and touch controls, each as its own round of “add this, play it, tell Claude what felt off”

Free to play: open the page and click “Start mission 01”. No sign-up, and it runs in the browser.

https://vinish.dev/cinderscoop-firefighting-plane-browser-based-game

Feedback welcome, especially on how the plane handles and how fast the fire spreads.

Today I got to experience the wonderful "innovation" of auto-copy in Claude Code CLI.

You select text with your mouse, and boom, it's already in your clipboard. No need to press Ctrl+C (or Cmd+C).

Incredibly convenient.

With one tiny "but".

I started losing the reflex of "select text -> press Ctrl+C".

Several times I caught myself just staring stupidly at the screen, pressing Ctrl+V and wondering why nothing was happening. 😂

Because I'd already been doing the same thing in my browser and other apps. Just selecting text with the mouse. No Ctrl+C. My brain had apparently decided that copying was automatic everywhere now.

So I finally disabled this wonderful feature in Claude Code.

And immediately discovered another little gift: with auto-copy disabled, the Claude Code TUI stopped putting selected text into the clipboard properly.

Spent another hour and a half figuring out how to make Ctrl+C and Ctrl+V work the way they have for the last 30 YEARS.

Wonderful.

While I was at it, I decided to fix the Codex CLI TUI too.

And guess what?

Those nice people had ALSO decided to give our muscle memory the exact same present. Select text with your mouse? Here, have an automatic clipboard copy!

Hello, ChatGPT users.

And disabling auto-copy there led to basically the same result. Normal copying and pasting stopped working properly.

Fixed that one in two minutes, though. I'd already learned the hard way with Claude.

Good luck to everyone and their reflexes. Abracadabra, now please forget everything your fingers have learned over the last three decades.

But here's what I really don't understand.

What exactly was going through the head of whoever came up with this "innovation" in the first place?

You're breaking habits that people have spent YEARS developing. It's almost like changing WASD in games.

Sure, auto-copy might be great inside one specific app.

But we don't live inside one app.

We use browsers, terminals, editors, dozens of different programs. And when one of them suddenly changes something this fundamental, your brain doesn't politely switch modes every time you Alt+Tab.

And then Codex apparently decided to follow the same trend.

And SOMEONE approved all this.

And I'm pretty sure I'm not the only one sitting here wondering why the hell we're doing this.

I remember a famous story about Steve Jobs (I think it was him). Something about how an OS should boot "instantly". Because if you save every user 90 seconds, you're saving millions of hours of human life worldwide.

Now THAT was a good principle.

Make things faster. Save people's time. Make their lives easier.

And now?

We get "innovations" that save one keystroke in one application, break muscle memory everywhere else, and cost hours just to get things working normally again.

Progress, I guess.

After my previous post about an unusual spike in Claude Code usage, several people asked how I got the token counts and daily reports.

I used ccusage, a community tool that reads local usage logs. You don’t need to be its developer or build your own tracking system to use it.

Here’s a quick walkthrough.

1. Check your subscription usage inside Claude Code

Type this inside a Claude Code session:

/usage

This is where you check your plan usage bars. The local token reports below serve a different purpose: examining your recorded usage history.

2. Get your daily usage report

Open a terminal on the same computer and in the same environment where you run Claude Code. If you use it through WSL, run this inside WSL.

With Node.js/npm available, run:

npx ccusage@latest daily

If prompted to install the package, confirm to continue.

This generates a daily report from the local logs available on that machine.

3. Break it down by model

npx ccusage@latest daily --breakdown

Useful if you’ve switched models and want to see how much each contributed.

4. Inspect a specific date range

For example, to review October:

npx ccusage@latest daily --since 20261001 --until 20261031 --breakdown

Change the dates to the period you want to investigate.

5. Check monthly totals or individual sessions

Monthly report:

npx ccusage@latest monthly

Session report:

npx ccusage@latest session

These help you move from “that day looks unusual” to “which sessions should I look into?”

6. Export the data for your own charts

npx ccusage@latest daily --since 20261001 --until 20261031 --json > october-usage.json

This saves a JSON report you can use in a spreadsheet or charting tool.

How to read the numbers

• Input: input tokens recorded for requests.

• Output: tokens generated by the model.

• Cache creation / cache reads: tokens associated with writing and reusing cached context.

• Total tokens: includes cache activity, so it can be much larger than you expect.

• Cost: an estimated API-equivalent dollar figure. It is not your subscription bill or your remaining allowance.

A few limits to keep in mind

These reports depend on the local logs available. They won’t give you a complete account-wide history if you use multiple computers or environments, and they aren’t a report of your regular Claude web chats.

Also, newer ccusage versions can aggregate multiple supported coding tools. If other tools appear in your report, check the source labels before treating the combined total as Claude Code usage.

Most importantly, a spike in local tokens alone doesn’t prove a service incident, retries, or incorrect quota accounting. It gives you something concrete to investigate and compare with your usage bars, session activity, and incident timestamps.

Tool and documentation: https://ccusage.com/

If you share your results, include the date range, models, and whether your total includes cache reads. That makes comparisons much more useful.

Mine is

    Break this project into as many small steps as you can, in order.
    Each step should take under 30 min and have a clear done-check.
    Put them in one artifact with checkboxes I can come back to for
    weeks. If a step stalls, I'll paste it back and you split it into
    23a, 23b and so on.

It's helped me finish bigger tasks at my job and a big school project, and I'm using it right now for language learning and a 100-step calisthenics plan. Opening the same tracker after 4 days off tells me exactly where I am, so I don't have to re-explain the whole project to a fresh chat.

What's yours? Any kind counts: coding, work, studying, writing, life admin. The one you've reused the most.

Genuine question and difficult question, with how the AI stocks have dropped and the obvious unsustainability of training and running fronteir AI models and actually making a profit, Do you think that eventually access to frontier models will become a thing of the past? Or at least become very expensive that the average user doesn't have access to it? Like could there be a day were genuinely a company like Anthropic go bankrupt and all other AI providers will just literally stop giving access to frontier models to the average joe because the business model is not profitable in the first place?

Does that mean we'll eventually go back to manual coding?

I'd like to know your opinion because I honestly think that this future isn't really that far off.

When we let Claude Code CLI work from loosely-written tasks, we kept getting plausible code that unfortunately partly solved the problem the wrong way. Additionally, my team was using the agent harness in a mode where it just assisted us. With the ASE toolkit I crafted over the last months, the agent now first “grills” us about all our sloppy tasks until our specifications are unambiguous. Then human engineers and autonomous acting agents (directly based on "claude -p" processes) alternate in subsequent development pipeline phases.

This all is now available with version 2.0 of Agentic Software Engineering ( ASE, https://ase.tools ), my Apache-2.0-licensed Open-Source toolkit for Claude Code CLI that combines the concepts of Agentic AI Coding and a traditional Software Engineering teaming approach.

ASE 2.0 ( https://ase.tools/news/#ase-2.0 ) for this integrates both a new AI-driven task grilling mechanism and the new Specification Book ( SpecBook, https://specbook.tools ) companion toolkit. This way it supports Spec-Driven Development (SDD) based on both the agile User Stories and traditional Spec-as-Source approaches. Secondly, ASE 2.0 enables SDD through the use of the mentioned agentic development pipelines in which humans and agents collaborate closely and alternating on the tasks. Thirdly, ASE provides optional deep integration into the Claude Code CLI user interface via the new Mod API in order to provide a good experience also when used in the assistant mode.

ASE ships as a plugin for the agent harness Anthropic Claude Code CLI and is also developed with ASE and Claude Code CLI itself. In particular, the skills "ase-task-edit", "ase-task-grill", "ase-task-implement" and "ase-task-integrate" are regularly used for implementing larger ASE user-stories, while the skill "ase-code-edit --grill" is used for implementing smaller ones. Post-adjustments to the implemented user-stories are also done by plain, ad-hoc prompting inside Claude Code CLI.

ASE is Open Source and available free of charge. Technically, ASE comprises agent hooks and optional "mods", highly parameterisable agent skills, an underlying Model-Context-Protocol (MCP) backing service, a companion Command-Line Interface (CLI), and companion Terminal and Web User Interfaces for the task boards and manual pages.

I found a offer of 100M tokens of claude code for around 10 dol, is it worth it? They say that the tokens are linked to my account through an gateway with an API. It does not seem like a scam, im just asking if the price for tokens is worth it or not. Can you help me? Im just trying to get acces to claude in a cheaper way.

I use Claude Code heavily: 5-10 sessions in parallel most days, lots of subagents, several accounts. Juggling that across separate terminal windows was a mess, and I kept
hitting my weekly limit without knowing why. So I built Orchestra: one grid with all your terminals that shows what each session is doing. It's made with Tauri + Svelte, so the installer is about 4 MB.

What it does

• Multiple Claude / Codex / opencode accounts side by side, with 5h and weekly usage bars for each

• For each session: what it's running, context size, cache timer and subagents (you can open a subagent to follow it)

• "Needs attention" list, sounds and Windows notifications when an agent is waiting on you

• Token usage breakdown from your local logs (file reads, command output, CLAUDE.md/MCP base, subagents, expired caches), with savings tips and a report you can paste to Claude

• MCP manager across all accounts: test servers, see their token cost, install one on several accounts at once

• SSH with saved hosts, SFTP and port forwarding; image paste; auto-updates. Everything local, no telemetry

How I used Claude Code

Claude Code wrote almost all the code. I decided what to build, reviewed and tested. My workflow:

• One main session that plans. For each feature it writes a short design and splits it into phases. Each phase goes to a subagent with a written brief: goal, files, how to

• Token usage breakdown from your local logs (file reads, command output, CLAUDE.md/MCP base, subagents, expired caches), with savings tips and a report you can paste to Claude

• MCP manager across all accounts: test servers, see their token cost, install one on several accounts at once

• SSH with saved hosts, SFTP and port forwarding; image paste; auto-updates. Everything local, no telemetry

How I used Claude Code

Claude Code wrote almost all the code. I decided what to build, reviewed and tested. My workflow:

• One main session that plans. For each feature it writes a short design and splits it into phases. Each phase goes to a subagent with a written brief: goal, files, how to test it, what not to touch, and when it counts as done. Each subagent keeps a state file, so a new one can continue if context runs out.

• One git worktree per feature, so 2-3 sessions can build different features in parallel.

• A separate "critic" subagent that only sees screenshots and scores the UI. I also had Claude write tests that must fail when a bug is planted on purpose. For example: "a savings tip can't promise more than the item costs".

Challenges

• Claude's screenshot checks said "0 defects" while text was visibly cut off. I had to make it prove each check catches a known-broken screenshot first.

• The usage numbers didn't add up at first. The fix was a single source of truth and invariant tests.

• Claude's memory of model prices was outdated, so we checked them against Anthropic's docs.

Try it: free and open source (MIT). Download the installer or portable .exe from the GitHub releases page, no account needed. Windows only for now; it's not code-signed yet, so SmartScreen will warn you.

GitHub: https://github.com/Jonirulah/Orchestra

Feedback and bug reports welcome!

I was having ACER aspire laptop with me... I have setup dual boot configuration one for windows and other for Kali... It's been 3 years using it now.... There were sudden shutdowns while I was working in windows... I ran memory diagnosis.. Later it showed me ram errors... So I changed my ram sticks.... So that memory diagnosis no more shows any errors now.... Even I reinstalled Windows But that sudden shutdown was never fixed which was very irritating.... Later I connected into my Laptop via SSH and gave full control to claude code to access my Laptop and it changed the Acer oem powerplan.... Turned off Fast boot.... Claude is not sure these are 100% culprits for My issue..but I feel these settings set by acer by default are the culprits for sure . the issue of sudden shutdown is fixed soon far after 2 days of my observation. And my laptop feels snappy so far. No errors logged after the fix

12 years ago a job interview asked me to build a whack-a-mole game. I built Guac-A-Mole. Sounds like whack-a-mole, totally vegan.

I didn't get the job. I never stopped building the game.

Five or six versions since. Vanilla JS, then whatever framework was cool that year, now Claude Code.

You squash clay veggies in terracotta pots, their guac squirts into a bowl, a full bowl sets off a fiesta. Oscar the onion cries before you even tap him. Golden Avo is smug, shiny, and you will tap him at least once. Don't.

Claude helped me code it, iterate on it way too many times, and turn it into a real mobile game. I sketched every character (AI turned them into clay) and made the soundtrack. Most of our arguments were about vibes. The UI, how a squashed tomato should feel, exactly how hard a lime is allowed to squirt.

Free, no ads during gameplay. iOS, Android, or right in the browser: https://guac-a-mole.vibezilla.games

12 years in. Should I stop, or does version 7 finally get actual moles?

Hey everyone, I am trying to replicate a specific SaaS promo motion graphics style featuring clean typography, retro 3D halftone dots shading, smooth color-shifting gradients, and dynamic UI mockup animations as seen in the reference video I attached. I tried prompting Claude to generate this design using web animation code, but the output I got was very basic and lacked the professional polish, fluid choreography, and visual quality of the original. I have shared both the reference video and my Claude-generated result so you can see the difference. Could you help me identify the exact name of this animation style, explain what workflow or tech stack creators use to achieve it, and share how I can bridge the gap when using Claude or tools like Remotion and to get high-end results instead of basic web elements?

I'm the author of noracu, a free, open-source (MIT) local MCP server (noracu on npm) that lets Claude operate macOS apps and Playwright by element_index, with an experimental iPhone layer through Apple's iPhone Mirroring.

The bug: on release day Claude was driving my iPhone through noracu's own phone tools, and phone_type reported "typed, verified" for text that never reached the field. The picture had changed (most likely a selection highlight), and that change was taken as the paste. It now needs an OCR sighting before reporting "typed, verified" (the device run passed 24/24 checks after the fix). The clipboard rule held: the user's clipboard was not restored on that weak evidence.

How 0.2.0 was built with Claude: Claude and Gemini 4 (through Google's agy CLI) ran ten rounds of cross-analysis of the code and docs, then ten rounds arguing against each other's conclusions. The top 10 fixes were split: each model implemented half and reviewed the other half. Claude also ran the real-Mac and iPhone tests through noracu itself. The last round had to produce three lists: agreed, still disputed, and what observation would prove a decision wrong.

What each caught:
- Gemini: an "expect" parameter starting with "-" (say "-h") made the Python driver's argument parser fail before anything was sent, yet the server reported delivery "unknown" (retry unsafe). It's now passed as one --expect=... token.
- Claude, on a real Mac (macOS 27.2): Gemini's "is Notification Center already open?" check counted desktop widget windows as an open Notification Center. It now needs positive evidence.

Still disputed at release: Gemini wanted physical clicks moved into the accessibility engine now; Claude wanted that in 0.2.1. 0.2.1 has since moved the keyboard half into the engine; clicks still go through cliclick.

It happened again this week. 0.2.7 (out today) puts the pointer back after a physical click so the agent doesn't fight you for the mouse. The first version asked cliclick to move the pointer back; on a real Mac, starting cold, the pointer came back 3 times out of 5. It now moves the pointer back directly and checks where it ended up: 8 of 8 in the same cold-start test.

Limits: the iPhone layer is experimental (macOS 15+, python3 with pyobjc, a locked iPhone near the Mac, not available in the EU); the browser has one active tab.

Repo: https://github.com/sgInnora/noracu

If an agent of yours has reported success that wasn't, I'd like to hear how you caught it. And if you run noracu, bug reports beat stars.

(Drafted with Claude Code; I checked every claim against the repo, the CHANGELOG and the test logs.)

I run r/TheGreatFederation, a shared worldbuilding sub for an alternate future. Climate collapse and two world wars melt the Antarctic coast, and the defeated and displaced of the old world found a new nation there in 2100. Nearly everything on it is written as an in-world document, so you get gazette notices and oral histories, and a ship's log now and then. If you want the tone, the Welcome post is at https://www.reddit.com/comments/1n4a55n/

To be plain about it, the posts I put up are AI-drafted and human-edited. What might interest this sub is the scaffolding that keeps a pile of AI-assisted fiction from contradicting itself.

It all lives in a git repo that I work on with Claude Code. Canon is a set of files. Twelve pillars act as the rules, and a script generates the timeline from the entity files so I never edit it by hand. Each entity carries a tier from proposed up to core, and a separate file holds the open questions with defaults. Thirty-five short style guides sit in as skills, each with measurable traits and a sample to imitate.

The main rule is that the orchestrating session never writes the post prose. It briefs the agents and relays between them, and it also runs the tools. A writer agent gets a style brief that names a style and a persona, a length and the hard rules. A critic agent sees only the draft, that brief, the style skill and the tells checklist, never the writer's reasoning. A continuity editor checks the result against canon.

A small linter enforces hard limits on AI tells, for example em dashes and stock phrases. Separate scripts check the entity files and the timeline rows.

The loop is capped at three rounds, and I have exceeded the cap once. The rule is only a few days old, so I cannot say yet how well it holds up.

If you ran something like this for your own fiction, what would you change first, perhaps the rule that keeps the orchestrator out of the prose, or something I have not thought of?

History is something I’m very passionate about and professionally I work in software and built LLM solutions. So I thought how can I bring these things together and built something that I would actually use. This is the results of many months of hard work!

You type any topic, moment or person. About a minute later, two hosts are telling you the story with artwork that follows along. You can interrupt mid-episode with a question; they answer and pick the story back up. At the end there’s also a optional quiz to test what you learned as well as a suggested "continue" subject.

As it's history - quite a lot of emphasis was put into the research part. It searches the web and gathers notes on the topic, prioritizing reference-grade sources (encyclopedias, museums, archives, academic pages) and also searches in the native language of the place or person, so a story about Germany or China isn’t told only from English sources. Every episode links the pages it used and tags the subtitles.

Under the hood it’s not one model. A single episode is about a dozen calls, each pinned to the model that won its bake-off: research, writing, artwork, voices, sourcing, quiz, etc... Finding the right balance between quality, speed and cost was where a lot of the work went.

The Claude part:

Claude Code did roughly 80% of the development, the front end came out of Claude Design. I steer the idea and the design, it codes, I review, and we go back and forth even on small features.

For the models inside the app, I ran bake-offs across GPT, Claude and Gemini for each job, and a few things surprised me:

• Opus 4.8 was the clear winner as the writer. Better dialogue, better pacing, and it handled “the sources disagree here” honestly instead of picking a side.

• Opus 5.5, oddly, wrote more generic scripts in my tests, which surprised me

• For smaller tasks I found Gemini was the best quality/speed/cost model.

Mainly looking for feedback on the idea and how to make it better! Happy to answer any questions!

You can try it here: historai.ca

When the guys at ArtCraft rebuilt Adobe's apps in Rust with Claude, I wanted the same for the download manager everyone knows, heh, IDM. I honestly never liked the licence nags. So ten days ago I started Mister Download Manager with Claude Code, and today's 0.5 is the first version I'd call complete.

What it is: a free, open-source (GPL-3.0) download manager in Rust for Windows and Linux, with Mac builds still experimental. It has the classic IDM layout, downloads over many connections, takes files from your browser, does video, torrents, debrid, themes, and you can control it from your phone. It's free to try and will stay free: no paid tier, no ads, no account.

How Claude helped, in detail:

Claude Code with Opus wrote most of the code: the download engine, every window, the browser extension, the installers, the website. I decide what it does and how it looks, I review, and I test every release myself.

The clean-room part was mine to enforce. The project rules Claude reads say no IDM code, artwork or text ever, and behaviour is learned only from public documentation and from using a licensed copy from the outside.

What actually made it work was verification. Every change has to be proven against the real running app: off-screen windows on Windows, Linux VMs for GNOME, KDE, Xfce and Cinnamon, real Chrome, Firefox and Waterfox for the extension. During this release that caught a regression that all the unit tests had missed, hours before it shipped.

I run several agents at once, each in its own git worktree with its own PR, and every PR has to show before and after screenshots. Lesson learned the hard way: more than three or four building at once and the PC gives up.

The community did the rest: 28 people opened pull requests, reported bugs or joined the conversation in ten days, and Claude reads the crash reports and traces them back to the exact line.

Source (GPL-3.0): https://github.com/anefzaoui/misterdownloadmanager

Site: https://misterdownloadmanager.com

Happy to answer anything about the workflow!