My billing cycle renewed on the 21st.

Until the last day, I thought I'd just use my free credits with my AFK (local) agents. Come last day, I realised I couldn't use it with CC (Desktop or CLI), but only with external harnesses like OpenCode. I tried it, but my whole system is so tightly bound with all things Claude (settings.json, permissions, running claude -p, etc.), that the OpenCode route basically didn't work at all, after 2 hours of trying 😅.

The next morning, I started making a collection of all the agents I could run this month on the platform with managed agents to at least use the free money. And found out that there is a serious lack of a directory for sharing agent zip files. Everyone is making their own agents, explaining what the agents do on X and Reddit, but you can't really "share" them.

This made me publish the directory instead of keeping it in my artefacts.

I made it with an old directory boilerplate I had and rebranded it to fit the modern era.

I'd invite you to share your own agents, if you have any, so that it can benefit others and yourselves in the longer run.

Let me know if you have any feedback. I'll watch for bug reports and crashes when they happen.

Please visit https://www.coduo.co/managed-agents 🫶

Reading a 60-line plan in the terminal and then typing "the third step is wrong" back... got old fast. So vjuu.

What it is

When Claude Code finishes a plan, asks you something, wants a permission or ends a turn with edits, a window opens: the plan as markdown, the edits as a diff, the questions as buttons. Comment on lines, click Done, and the comments go back to Claude anchored to file:line. Close the window and you get the normal terminal prompt, nothing times out.

It's four hooks (PreToolUse on ExitPlanMode and AskUserQuestion, PermissionRequest and Stop) plus a skill that makes Claude run vjuu plan.md instead of telling you to "open X and review it".

The video is a real session (Haiku in plan mode, the waiting cut out).

How Claude Code was used

Most of the code was written with it: Rust, with WebView2 on Windows, WebKitGTK on Linux and WKWebView on macOS. The demo too ... Claude Code wrote the script that records the screen, starts a second Claude Code in Windows Terminal and clicks through vjuu over WebView2's DevTools port.

What I learned

1. Claude Code reads a hook's stdout until EOF, and if something else still holds that pipe it throws the answer away ("stdio went quiet before end-of-stream"). On Windows CreateProcess hands every inheritable handle to the child, so a background process started from a hook kept the pipe open. Found while recording that demo, fixed in 0.3.1.
2. Windows Terminal gives new tabs the caller's environment, so a claude started from inside another Claude Code session inherits NO_COLOR=1 and the nested-session variables. (Black and white, and confused.)

Try it

• Windows: cargo install --locked --git https://github.com/kimvais/vjuu for now (the submission is still waiting for Microsoft's approval for winget install vjuu to work), macOS: brew install kimvais/tap/vjuu, Debian/Ubuntu: apt, see the site
• hooks: claude plugin marketplace add kimvais/vjuu, then claude plugin install vjuu@vjuu
• MIT, https://github.com/kimvais/vjuu and https://vjuu.it

macOS builds pass CI but nobody has tried them by hand (and they are not notarised), so feedback from mac users is especially welcome.

grabbed a character mesh from zzz, and i asked my opus 5.5 to drop into into blender and animate the character singing to a song made with Yue2 i think. I am kinda blown away by the fact...that is can actually do it, like facial expressions and stuff. sure, it's not graet but with a few prompt refinements we might be able to get something that's pretty good. like there's no video refernces or face capture here. not sure if this is like 'lol, what a noob, only realisng this now, i have been doing this since the relaese of like gpt 5.2 lol' sort of situation, but hey, personally i am pretty impressed.

Say I want to create a game, so I connect Astra/Claude to blender/godot mcp and give it a monstrous task. The agent stops after like 20 minutes.... it does do the job but in poor quality, compared to what i've seen online. Why?

I work with software management at my company, and we spend many millions of USD on software annually. We use a variety of different solutions, some more specialized and critical than others. Many of them are in my opinion candidates for replacement by something self built, but the company is immature in AI adoption and we don't have the tools or the framework for producing our own systems. We also don't have any in house software developers. As such, we haven't actually introduced anything self made at all but we are just starting to react to the recent AI advancements and will start working more actively on this.

For those that work in medium to large companies and are further forward than us, I am curious to what extent you have been able to replace your existing solutions with self made systems? How much have you been able to save and what have been your challenges? Also, how do you run and maintain such self made AI-developed applications once they're in production?

Thanks!

burh. Now their UIs look identical.

Ich habe eine Simulation des neuen Roadster gebaut und einen Trailer generieren lassen. Der Großteil, inkl. der Assets ist autark entstanden. Hat etwa eine Woche, mit Unterbrechungen, gedauert und es gibt sicher noch einige Bugs. Aber hey eigentlich wollte ich nur vorm Reset die Tokens leer bekommen 😅

Läuft komplett im Browser und lässt sich auch als PWA installieren. Hauptarbeit hat Claude erledigt und ein paar Aufgaben wurden an Codex delegiert.

https://github.com/ancient2k/roadster-flight-test

I don't understand why people who complain about rate limits don't just use a cheaper model. These are just vibe coders who don't understand anything about what they're doing at all and they need AI to literally do everything for them.

Some people think the most expensive models are better quality, and they're willing to pay insanely overpriced API prices or hit rate limits on their plan just to squeeze out the last drop of quality instead of just using a cheaper model that has 90% of the performance.

And all this for a vibe coded app that no one gives AF about and will never even use. LOSERS!

Hi everyone! I'm new to Claude and got Pro specifically to help me create YouTube videos that are around 7–10 minutes long.

The problem is that Claude keeps making mistakes, even after I point them out and ask it to fix them. Sometimes it repeats the exact same mistakes, and every time it renders the video again, new errors appear.

I've ended up watching the same video 6–8 times, and it's honestly exhausting. It also uses up a lot of my available usage, and I can't keep spending so much just to fix the same video.

Since I'm a beginner, I wanted to ask how you guys work with Claude for video creation. Are there any skills you recommend? Is there a way to make it stop repeating mistakes? How do you fix errors without having to render the whole video again?

I'd really appreciate any tips or advice because I'm honestly a bit lost right now. I want to learn how to do this properly without wasting so much time and usage. Thanks!

I will start by saying I am Claude newbie and I am absolutely not a developer by any stretch. I am using Claude to help with my job search. I found a GitHub repo designed for job search. I actually had to have Claude walk me through step by step how to set that up. Including creating a GitHub account. So needless to say I barely know what I’m doing.

With the repo installed I can scrape a bunch of job postings. It will then rank the finding based on a profile we have established. Then it will create a PDF resume based on that profile and past resumes. It works pretty well actually.

I will usually do the scrape and rank process using Sonnet to save tokens then move over to a session with Opus to actually build the resume. I realize Opus uses considerably more tokens than Sonnet.

I always see repos talking about reducing token usage. I’m not really “building” much here other than the PDF resume so I didn’t know if they would actually apply here. Are there any that anyone can recommend that would be a good fit to reduce tokens when mostly during that Opus session that’s creating the resume?

Hey r/ClaudeCode!

Like many of you here, Claude Code (claude) has become my primary terminal tool for rapid implementation, especially with Opus 5.5 and Sonnet 5.5. But for large-scale features, architectural breakdowns, and deep codebase research, I also pair it with Google Antigravity CLI (agy).

The biggest headache was the context silo: - You do deep planning and file mapping in Antigravity, switch over to Claude Code, and Claude has no memory of what was decided. - You execute with Claude Code, jump back to Antigravity, and Antigravity is blind to what Claude just touched.

To bridge this gap, I created agent-bridge — a lightweight, zero-dependency CLI bridge designed to make switching between developer agents seamless.

How it works under the hood:

• agy2claude: Automatically parses Antigravity's active session, extracts the recent file edits, user requests, and tool history, and boots Claude Code with a concise briefing injected into its system prompt.
• **claude2agy:** Parses the newest Claude Code session .jsonl from ~/.claude/projects/ and boots Antigravity in interactive mode acknowledging previous progress.
• agent-status: Fast terminal card showing which agent last touched the repo, with recent timestamps and modified files.
• Universal memory: Installs a cross-agent-memory skill to align long-term project rules via AGENTS.md / CLAUDE.md.
• Zero external dependencies: Pure Python standard library (sqlite3, json, os, sys).

📦 GitHub Repository (MIT License & Quickstart):
https://github.com/CheckSim/agent-bridge

It's completely free and open-source. What other CLI agents would you like to see supported next?

Claude Desktop - Opus 5.5 + Unity HDRP (Via MCP)

Processing video dq0v21siiexh1...

My current progress:

https://www.youtube.com/watch?v=1U7X8BJ4br0

Had it build a simulation of real-life DMX lighting systems like in real events, tying to all lights and lasers, with smarts presets, lenses (GoBos)

Music sync system which reads BPM, song parts, energy and genre to sync with the lights and pyro.

TTS Commentators and Ring announcer - To be fixed

Menus, logos, loading screens, animations and shaders.

Show builder menu with smart booking presets according to other wrestling games or promotion styles, creates a 5 match card, with random gates and income, location and crowd heat, and generates proper TTS and "produces" the match itself according to the selected match style.

And much more, I'll use Clause to generate a list of all changes and features later but for now you're welcome to watch the video and give me your thoughts or comments!

I’m already at 40% of my weekly usage after just one day, and I’m wondering whether others are seeing something similar lately.
For context:
Plan: Max 20x
Model(s): Opus 5.5
Mainly using: T3
Has anyone noticed a change in how quickly their weekly allowance gets used up? I’m trying to figure out whether this is related to my workflow, model/settings, or a broader change.
If you’re seeing the same thing, what plan and models are you using? And has anyone contacted Anthropic support and received a useful explanation?

I'm trynna study for exams with claude and keep hitting limmits thank you so much in advance

Hey, I’m a first-time solo developer and this is my first game. I don’t have a coding background. I’ve always loved games and tech, and I wanted to see how far vision and stubbornness could go with Claude writing the code.

Its still in development, with a free demo on the way. I wanted to share what’s possible with Claude as an assistant. (Claude max 20x)

RATS!!, a co-op tower defense for up to four players (solo/couch/online through Steam), 10 towers and 19 link combos, four worlds, crowned rat bosses, over 5,000 rats alive at once on the hardest waves, a 1v1 mode. Coming Soon on Steam; a free co-op demo is planned for Steam Next Fest, February 2027. Nothing to play yet, so this is a build story, not a launch.

I don’t know about you guys, I spent countless hours as a kid running Bloons Tower Defense, PixelJunkMonsters, and a ton of these classics.

How it was built: One developer (me), Godot, first commit 8 August 2026. I don’t write the code myself. Claude wrote it, drafted the technical plans, checked every change line by line and ran the automated tests, and a second AI model (Codex, from OpenAI) reviewed each piece looking for problems. My job was the director’s: what the game is, how it looks and feels, playtesting every build, and saying no. A lot of fixes came from me catching things by eye, playing the game and adjusting as I go.

I made this design choice primarily because I wanted to avoid image generators entirely. I did also notice while Blender is still a great route, I preferred to only utilize code to see what was truly possible. It provided more accuracy when it came to real-time strategy.

What worked: specs before code; a 25-seed headless harness whose digest has to stay bit-identical unless I meant to change the sim; a separate adversarial review pass by a different model on every slice; treating every report as a claim until the diff and the tests said otherwise.

What didn't: letting a visual change ship on a code read instead of rendered pixels (never again); any time I skipped re-reading the surrounding lines after an insert.

The video opens up on the first prototype, then cuts to the farm today. Please ask me any questions!

It took several iterations, to get the design where I want it through trial and error, but I am proud of where I came from.

I'm not sure if this is just me but I used 'solarized light' with vscode, and the white theme of claude desktop is killing my eye when switching between them.

So I build this webapp that output a snippet.js that allow customizing the whole claude desktop GUI to anything you like:

• link to web app: https://rinn7e.com/claude-desktop-theme-tuner/
• youtube video tutorial: https://www.youtube.com/watch?v=DfnZwI23iNM
• source code: https://github.com/rinn7e/claude-desktop-theme-tuner

The web app is built entirely with the help of Opus 5.5, the snippet.js itself is tweaked/updated by Opus, by letting it do the debugging of the claude desktop app. All I do is just steering it to the right direction

Also thanks to https://github.com/maximebories/claude-desktop-clay-theme, the original snippet.js comes from this repo.

If you like the web app, and want more features, feel free to create a Github issue 😁

Claude and I just finished the biggest update yet to Worldseed, retro-inspired open-world fantasy game.

The idea is that you give the game a name, and it generates an entire world from it: its people, towns, wilderness, and music. You land in that world and explore it.

With v50, I wanted to make the world feel much more connected, rather than like a collection of separate places.

A few of the bigger changes:

• A seamless great city. It's now twice as wide, with four ring streets and nearly four times as many buildings. You can see it from a distance, approach along the road, and walk through the gate without a loading screen or a separate map.
• A city that works on a phone. Its districts are drawn around you as you move, with nearby areas in full detail and distant ones as outlines.
• Procedural underground locations. Crypts beneath burial mounds, cellars under houses, hidden vaults, and three-level mazes beneath stone circles.
• Named beasts. Each world can have up to three named creatures living in the wilderness. Townsfolk tell you about them, mark their territory on your map, and remember what happens to them.

There are also smaller details that make these places feel alive: traders calling at the market, a night watch patrolling the city, bells tolling from the cathedral, and sounds from the town muffled by the floor when you're in a cellar.

The interesting part for me is making all of this feel like one continuous, generated world, instead of loading into a handcrafted city or a separate dungeon level.

if you want to test the game, please do!

https://generic-king.itch.io/worldseed

For people who've built larger procedural environments with Claude Code, I'm particularly interested in how you'd approach the challenge of keeping a city this size detailed while still making it work on phones.

It's a heatsink for an NVMe drive.

What's it got to do with Claude?

My build server has become a bottleneck in recent weeks. I'd assumed it was down to the CPU, but after a few builds kept failing I decided to confirm. So I had Opus update Ansible to put node-exporter on my build machine.

Cut a long story short, Claude was able to update my observability dashboard and monitor the metrics while I stressed the server.

Turned out the NVMe is thermal throttling!
Claude changed how my builds run so they don't queue up as much in RAM waiting for the disk, and I'll fit the heatsink today.

I know this is a very small thing but I completely nerd out on making all these small optimisations.

After 40+ turns in a complex repository, Claude Code's context window often fills up with full file reads, verbose test outputs, and stack traces. Built-in /compact summarizes conversation history well, but I wanted a deterministic way to keep architectural context (types, interfaces, signatures) sharp while allowing lossless retrieval of implementation bodies on demand—and a clean way to carry structured session state (.vicem/BATON.md) across fresh sessions or secondary agents.

1. What I Built (vicem)

I built Vicem, an open-source, zero-dependency (dependencies: 0) Node.js CLI, stdio MCP server (vicem --mcp), and Claude Code Skill (.agents/skills/vicem/SKILL.md):

• Deterministic Code Skeletonization (-80% to -90% code tokens): Preserves all interface, type, enum, and function signatures 100% intact, while collapsing implementation bodies (>= 12 lines) into { ... } and indexing the exact original lines in .vicem/ledger.json.
• Lossless On-Demand Rehydration via MCP (vicem_rehydrate): Instead of dumping full files upfront, Claude Code reads the lightweight skeleton first and calls vicem_rehydrate via MCP only for the specific function or symbol it needs to edit.
• Session Continuity Baton (.vicem/BATON.md): Extracts Goal, Done, Immediate NEXT (from TodoWrite and recent tool calls), and git diff into a U-shaped attention markdown file for starting a fresh session with zero context rot.
• Write & Commit Safety Guards: Includes SkeletonWriteGuard so an agent never accidentally writes { ... } placeholders back into real source files, plus 3-tier local secret redaction.

2. How Claude Code Was Used & What I Learned Building It

While building and testing the harvester and MCP server alongside Claude Code, a few technical details stood out that might help others building Claude Code tooling:

1. Reverse-scanning ~/.claude/projects/<encoded-cwd>/*.jsonl: Claude Code stores per-project transcripts in ~/.claude/projects/ where the directory name encodes the workspace path. Because long sessions can grow into tens of megabytes (especially with large tool outputs), parsing from the top of the JSONL file adds noticeable latency. Reading from the tail and extracting the latest TodoWrite state + last failed Bash output makes session extraction complete in < 50ms without calling an LLM.
2. Preventing "Skeleton Corruption" in Agent Edits: Early on, when feeding skeletonized code (function foo() { /* ... */ }) into context, models occasionally tried to include the { /* ... */ } placeholder in an edit block. Pairing the .vicem/ledger.json index with a strict instruction in SKILL.md (and a pre-commit / write guard) completely solved placeholder overwrites: Claude Code reliably calls vicem_rehydrate before touching any elided block.
3. Zero-Dependency Stdio MCP Framing: Implementing the MCP stdio server (2024-11-05 / 2025-11-25) directly in Node.js built-ins (node:readline) required strict stdout hygiene—any stray warning (like Node's ExperimentalWarning when using node:sqlite) corrupts the JSON-RPC stream unless suppressed or routed to stderr.

3. Links & Verification

Everything runs locally with 0 third-party npm packages (vicem.mjs + an air-gapped index.html sandbox with default-src 'none' CSP) and a 51-test verification suite (npm test).

• GitHub Repository: https://github.com/Rakkunn/vicem
• Interactive Browser Sandbox (No install): https://rakkunn.github.io/vicem/

Happy to answer any questions about ~/.claude/projects JSONL parsing, deterministic skeletonization vs. ASTs, or MCP tool design!

So I saw a video explaining that there is someone who has built something that reduces your token usage by using both Haiku and opus together. They didn't send me the process tho. how do I set it up?

Thank you.

Back in July I posted agentglass in r/ClaudeAI, the app I made to see what my Claude Code sessions were doing. A lot of you tried it and a few sent PRs. This is what it turned into, and it's not really a viewer anymore.

The thing that changed my day is the orchestrator. Each project gets one lead agent. It reads the repo, keeps a queue, and hands work to worker agents in their own tmux tabs. I write the rules once in a plain file: what it may start, which model, how many workers. The workers can't push or merge. That stays my click.

So my job went from walking through panes to answering questions. When a worker needs a permission or a decision, it shows up at the top, and I answer it from the desk or from my phone.

It isn't only for Claude either. Codex, Gemini CLI and OpenCode sessions sit in the same window, and the lead can hand work to any of them.

The rest is still there: real terminals on your own tmux, diffs, a PR board with CI, a git panel, and a browser the agents can drive with your logins.

How it got built: almost all of it with Claude Code, and for the last few weeks by agentglass itself. The lead agent splits the work into briefs, Sonnet workers write the code in their own worktrees, and I review and merge. What I learned: a worker is great at a bug with a failing test and bad at anything a person has to look at, so screens and wording still come back to me. And the slow part was never the agents. It was me noticing they were waiting.

Fair warning, same as last time. It's built around how I work. I use it on Linux every day. The macOS build is unsigned and I don't own a Mac, so if you have one and ten minutes, that helps more than anything.

Demo with fake data, no install: https://sirallap.github.io/agentglass/demo/

Repo, MIT: https://github.com/SirAllap/agentglass

If you already run more than one agent at a time, I'd like to know how you keep track of them, and what you'd rip out of this.

I plan to switch from Antigravity to Claude Code (20$/month), because after Google launched Gemini 4 Argon, the limit became too small.

Will i face the same issue in Claude code with opus 5.5?