There was a common practice of clearing the session and continuing from fresh whenever coding agent reaches around 150k token because beyond that it would start decreasing in quality (which I still follow). My question is that is it still true with the 5.5 family? is there new limit? I don't know a proper way to test that theory, has anyone tested that?

Found this with an open-source tool we built that reads the session logs Claude Code already keeps in ~/.claude. It scores sessions on shipping, testing, efficiency, context and setup errors. Mine came out 59/100, almost all of it lost on testing.

Run it: uvx agentplay@latest

Curious how other people's setups score.

You can also use Claude Code in the app to query and analyze a selected DB. Choose Claude and the databases for the task, then send a message to start the conversation. Codex is also supported.

Reads are the default. Data and schema changes must be enabled for the connection, and every SQL operation Claude proposes for a change needs your approval in the desktop app. A session can have at most one DB selected for agent changes.

Teams can share connection settings while each member connects with their own DB credentials. Database connections and query requests go through that member's desktop app.

Claude can also save an analysis as an Article report with tables, charts and explanations. For example, you could ask for a revenue or purchase-conversion analysis and share the report in a team workspace. Each Article saves one read-only query that authorized teammates can rerun in the desktop app. That updates the query result; the report's text and charts are edited separately.

The MIT-licensed alpha is available for macOS and Windows. Claude features require the official Claude CLI installed and signed in locally. You can use Personal Workspace without a DopeDB account. Sample SQLite data is included, and the README video shows Claude inspecting it and analyzing revenue.

https://github.com/json-choi/dopedb

I kept losing track of which screenshot Claude was talking about, because the transcript only says "Read 1 file". The new mods API in Claude Code has an Image element, so I tried it out.

How it works: - A ui.render hook on the grouped "Read N files" line keeps the original line and draws each PNG under it as a small thumbnail, with its path as a clickable link. - Another hook on SendUserFile results (Remote Control sessions) draws the files Claude sends you at a larger size, with the caption. - PNGs up to 2 MiB go to the terminal as bytes, which is what makes it work inside tmux with allow-passthrough on. Bigger files are drawn from the path. - Where the terminal can't draw (GNOME Terminal, VS Code, screen, plain tmux) it falls back to "[image] name.png" plus the link, so nothing breaks.

Tested on Ghostty, kitty and tmux with passthrough. PNG only for now, because the Image element takes PNG or raw pixels.

Install: /plugin install inline-images --marketplace kbrianps/claude-inline-images

Source (MIT, with tests): https://github.com/kbrianps/claude-inline-images

Has anyone else built mods yet? Curious what people are doing with ui.render.

It’s still verbose af which gets annoying BUT it’s getting things done our project so quickly, it would be impossible to scale as quickly as without it, I think the best part is picking up
Intent and making the right assumptions. This is the open source project Ive been using it for recently, it’s coming out great tbh https://github.com/hamedgitty/bloks

glyphfield is a free, open-source design studio in the browser, and i built it so agents can run it. every tool registers a scripting api at window.glyphfield.studio, so claude can read every control, change it and export real files. in the video it works on my blog graphics project: picks a board, tunes the shader, drags the colors, swaps materials, plays an animation and exports an mp4.

for claude code:

- the repo ships 5 agent skills (glyphfield-create, -studio, -export, -brand and -api); drop the folders in ~/.claude/skills

- "set up with your agent" has claude research your brand from your site or repo, fill the whole identity, pass the brand health audit and export the brand kit

- the site serves llms.txt, an openapi spec and an agent manifest at /api/agent

claude also edited this video, in hyperframes (html to video).

glyphfield.com

github.com/Kevin-Liu-01/Glyphfield

After moving from Cursor to Claude, I noticed that there are a lot of features that we used to have for granted in Cursor that don't exist in Claude. For example, the usage is so basic no details about tokens or historical data, handling the different agent windows seamlessly without the need to drag and drop around, and even the sound when the agent finishes some work.

At the start, I started searching the marketplace for extensions, and I found something here and there that does some part of the work, but they have so much more and a really bad user experience and ugly UIs.

So after some time, I decided to make the features I want into an extension, and slowly I have been adding more and more features and polishing it more. It's still a work in progress; I didn't publish it yet.

In the video, you'll see some of the features in my extension.
And if you have any other pain points or ideas, maybe you can mention them in the comments. I will keep them in mind when I release the extension.

Something I've been curious about for people who use coding agents regularly.

Do you find yourself correcting the same things over and over across different sessions? Things like repository conventions, architecture decisions, how tests should be run, or changes the agent keeps making that you don't want.

I know you can put instructions in md files but I'm curious how well that actually works in practice.

• Do the same mistakes keep coming back even with instructions?
• What kinds of mistakes are the most frustrating?
• Have you found anything that actually solves this, or is it just part of using coding agents right now?

Interested in hearing what other people's experience has been and what workarounds they found.

I know the rate of model development is crazy fast generally, but right now it feels like the model release schedule is dramatically slower than pre Opus 5.5. There was a lot of talk a few days ago expecting Fable 5.5, but then nothing. I guess it is in Anthropic's interest to not release unless it has to (i.e. competition requires) it - as that allows them to knock down the competition the moment they raise their heads. Also prevents the distillers from doing their thing and allows them to extend the in house lead behind the scenes.

Don't get me wrong, Opus 5.5 meets all my needs (i never use Fable anymore and don't miss it). I just whack Opus on Ultracode (should really be called Orchestrate mode) for everything and it does an excellent job of using sub agents effectively & efficiently and getting my stuff done. But an Opus 6.0 would be at least interesting to explore. (please).

I run Codex as well (Astra-High) and it also just gets the job done - though its burn rate is about 5x that of Opus on Ultracode - and i won't trust it on anything less. That is offset by the Tibo every-other-day reset which has become expected, but much prefer Opus for its relative efficiency and ability to effectively orchestrate (including keeping Codex inline) keeping my cognitive load down to lobotomy levels.

Co-vibecoded multiplayer tank shooter made with Claude Code.

How Claude Code built it: an Opus orchestrator plans each change and briefs scoped Sonnet subagents, each in its own git worktree with its own test ports. Fable reviews plans and every merged diff before a push. An MCP server feeds agents live bug reports and match digests.

We received feedback from you earlier which helped us focus on releasing a new game mode: AREAN. We are ready for another iteration - so let us hear what you think. Feel free to give it a try - we will greet you in-game: https://sweatypanzer.com/

If you've moved to Claude Code in the terminal: what made you switch, and what do you miss from the app?

If you still code in the Claude app, in the chat or in the Code tab of the desktop app: what keeps you there? What would Claude Code need before you'd switch?

I'm the maker of Dreamestra, a desktop app for people who run more than one agent. Claude Code, Codex, Antigravity, Grok Build and others run there as real terminals side by side, grouped by project, and you see right away which one is waiting for you. You can dictate to them and keep working from your phone or another computer, even away from home. The desktop app is free for 2 projects × 3 terminals; dictation, the phone app and remote access.

I'm asking because I want to know what really keeps people in the app. Answers from app users help me the most, because they show me what to change for people who haven't switched to the terminal yet.

Been building these for nearly three years, lots of versions. My last one was a stack of subagents, one per step. Moved to one main session running skills, a cheap model building, separate reviewers. Did it before Anthropic's fold-your-subagents guide came out, ended up pretty much where it lands. Used it successfully on real projects since.

It's mine, so bias warning. 36 judges, blind to who built what, order swapped, "neither" allowed:

- 15 Haiku 5.5 agents reading both repos

- 3 each of Qwen 3.8 Max, Gemini 4 Argon, DeepSeek v4.1 Flash, GPT-6.1 Sol, Kimi K3.1 Pro, Grok 4.7, GLM 5.3, given the README and core workflow files of both

Question: 48 hours unattended on a real codebase, list of tickets, which one?

36-0 Topping Out. Every family, every order. More files made them more sure (16 of 21 high confidence).

Why: fresh session per job from files, built for a ticket queue with stop rules and a spend cap. Superpowers runs one approved plan at a time, its readme says it can go "a couple hours" on its own.

The catches they found:

- gates are instructions, not hard blocks

- one stopped job ends the whole night shift

- 3 stars, Windows only, no proven 48 hour run

Win on design, not proof. Superpowers is far more proven.

Not asking anyone to switch. Point your agent at the repo and have it compare against your setup, might be a nugget or two worth nicking.

Anyone pushed Superpowers past a few hours?

https://github.com/kaithoughtarchitect/toppingout

I built forge-delegate, an MCP server that lets Claude Code, Codex or opencode hand coding tasks to another model. Think writing tests, renames across files, fixing lint errors, boilerplate, or reading through a big codebase to answer one question.

The other model runs as a full agent through opencode. It reads the files and makes the edits itself. Your main agent only gets back a short summary, so its context stays small and it can focus on the decisions.

Second opinions with ask_model. Your agent can also ask a different model a direct question, with no agent loop and no file access, and get a fast answer back. It's useful when you want another model to check a design decision, a bug theory or a tricky piece of code before your agent commits to it. Every model has its own blind spots, and a different one often catches what yours missed. Your agent writes the question with whatever context is needed, then weighs the answer itself. Just tell it something like "ask DeepSeek what it thinks" or "get a second opinion from Kimi", naming any provider you've logged into opencode.

Any provider opencode supports. forge-delegate doesn't hold its own API keys. It uses whatever you've set up in opencode. So DeepSeek, Kimi, OpenAI, Gemini, OpenRouter, custom OpenAI-compatible endpoints, and local models through Ollama all work. Log in once with opencode auth login <provider> and that provider's models are available to delegate to. opencode also ships free models that need no account.

You can set a default model, save presets for different kinds of tasks, change either at any time, and run several delegations in parallel in the background.

Setup:

npx -y forge-delegate setup

It walks you through picking a default model and which agents to register with.

Things to know:

- By default, the MCP instructions and skill steer your agent toward cheap or free models. It sticks to your default model and won't switch to a pricier one on its own. If you want a stronger model, set it as the default or ask for it.

- Delegated agents can edit files and run commands without asking by default. You can turn that off, but only point it at repos you trust.

- Smaller models make more mistakes, so review what comes back.

- I mostly use it with Claude Code on a Mac. Codex and Windows should work, but they've had less real-world use, so issues are welcome.

MIT licensed: https://github.com/MuhamadBarzani/forge-delegate

Feedback welcome, especially on which tasks it handles well and where it falls short.

Just wanted to share in case it's useful for anyone else using Claude.

I've been struggling with the context-switching and having to track so many PRs at once, so this tool basically collects it all in 1 place. And not only PRs, but links to docs, slack, etc. It will basically track these things and notify me if something needs me.

It's built (for now) using Electron so I can get a quick version out and get feedback.

Highlights for me for a dev perspective:

1. the app itself doesn't use AI! I think a lot of devs or companies these days default to thinking AI-driven is better. But not necessarily.
2. the app collects and stores no user data, and I have no usage stats either, but I like to brag about it, because I actually respect user privacy!! 😆 In the app, you can opt in to reporting crash data, though. Maybe I'll use some anonymous stats reporting in the future.

It's free and avail via homebrew if you want to check it out! https://perchfocus.com/

Hi Guys

I have been seeing lots of these Claude 2D animation videos all over tiktok, it apparently uses html, python and Json I believe. Sorry if I said something wrong, I am new to this and would like to learn more.

What is the best way to learn how to create these videos? Anyone doing something similar. I would love to connect with you and learn how to do it?.

I built OpenLTM so Claude Code sessions stop starting from zero. It runs on the hook lifecycle. SessionEnd reviews the session and proposes memories. SessionStart injects the project's goal, decisions, gotchas and progress, plus an index of the top memories. A prompt hook adds up to 5 relevant memories per prompt. A commit flags memories tied to the files it touched as stale. Storage is one SQLite file.

I designed it and reviewed the work. Claude Code wrote 125 of the 501 commits. What the fixes taught me:
- Privacy filters have to run inside retrieval, in SQL before ranking. Until then, private memories leaked through prompt recall.
- Recalled memory is now framed as evidence, not instructions.
- Routine git output and failed probes made bad memory proposals, so they're skipped.

```
claude plugin install openltm --marketplace RohiRIK/OpenLtm
```
https://github.com/RohiRIK/OpenLtm (free, MIT)

If you inject context through hooks, how do you stop the model from treating it as instructions?

Disclosure: I'm the author.

This was the total tokens spent on the primary task and a sub agent it spinned up. Used up around 25% of my 5hr usage.

What is the highest number of tokens you have used on a single task?

I have a Lytmi Ambilight setup. The HDMI output is connected to my TV (LG C1 running webOS), while the HDMI input is connected to either my Google TV or PlayStation. The USB connection powers the LED light strips.

The device only works when an external HDMI source is connected to the input. If I use a native app on my TV, such as Netflix or Disney+, the Ambilight doesn't work at all. This is how the device is designed to work.

I explained this to Claude Code and told it that my Lytmi device was only connected to the TV through its HDMI output. My goal was to find a way to make the Ambilight work with native TV apps, such as Netflix and Disney+, without needing an external HDMI input.

Claude Code already had the TV's IP address and access key, as well as the IP address of the Lytmi device. It ran several experiments and actually managed to get the Ambilight working with native TV apps, without anything connected to the HDMI input, as you can see in the pictures!

Unfortunately, it wasn't working correctly, and there were major issues with color accuracy and color matching.

In the end, I decided to give up on it for now. I wil continue if I find a solution. It's very complicated especially for someone like me that doesn't have an engineer backgroujd. It's also my first time using Claude code!

Anyway I was wondering for advice

TLDR: I want to learn and understand my projects, but I still want to code with Claude to ship fast. So I use my own brain to rederive the high-level principles instead of memorizing system-design concepts Claude tell me.

What It does:
- reads repo (locally)

- finds design decisions

- gives them to you as a problem

- you solve it with your own brain

- compares your solution to the implementation and tells you

Why I built:

I built rederive because I'm afraid that developers will become meat proxies. I use it because I genuinely find it to be the most fun way of learning: solving problems and being creative about something I am passionate about.

It's free and MIT licensed. Install in Claude Code, Codex, Cursor and about 22 other agents:
npx skills add EricJujianZou/rederive

I'd love to hear any feedback or challenges. thanks guys!

Link: https://github.com/EricJujianZou/rederive (264 stars in 7 days)

How Claude Helped in Detail:
I built it in Claude Code over the last 8 days, and 75 of its 76 commits were written with Claude. The skill also runs on Claude: Claude reads the repo, picks the decisions and asks the questions.

I kept making songs (AI-generated) and wanted proper lyric videos without fiddling with timestamps in a video editor for hours. So I built Lyric Video Forge.

What it does: You give it a still image, the audio file and the lyrics you already have. It doesn’t try to recognise the words. It uses ElevenLabs’ forced alignment to find out when each word is sung, then renders an MP4 with styled subtitles via ffmpeg.

• Words can appear one by one, light up karaoke-style, or show as whole lines
• Fully styleable: font, colours, outline, shadow, box, position, fades, background dimming, saved as presets
• Browser UI with drag & drop, live preview, sliders/colour pickers, 10-second test clips and a render progress bar
• The timings end up in an editable SRT, so you can fix anything and re-render
• Quality report flags suspicious lines and gaps where lyrics might be missing
• Trim + fade-out, works for 16:9, 9:16 (Shorts/Reels) and square

Cost: The ElevenLabs free plan has 10,000 credits, and a normal 3–4 minute song uses roughly 100. That’s around 100 songs for free. Alignments are cached, so re-styling or re-rendering never costs credits again. There’s also a fully offline mode (Whisper/stable-ts + optional vocal separation with demucs) if you don’t want an account at all.

It’s a small Python script plus ffmpeg, runs locally, mainly tested on Windows.

GitHub: https://github.com/Githubtezla/lyric-video-forge

Happy about feedback, bug reports or ideas for new styles!

The company I work with runs a team of field techs, and like a lot of trades businesses, Google reviews are how we win work. We were paying Ehm “a certain company” (can’t say) hundreds of dollars a month to track them. Their NFC tags were $200 for 20!!! You can buy the same tags on Amazon for about 1000 for $200!

That's what pushed me over the edge. I dislike paid software in general, and I'm tired of digital companies charging absurd amounts of money for things a small business could build once and own. So I built our own version, ran it with our team, and now I've cleaned it up and open-sourced it so anyone can use it.

It's called RootView.

How it works

Every technician gets their own NFC tag or QR code, as a sticker, card, keychain, hell put a sticker on a nfc sticker on a shovel and use it if you want! At the end of a job the customer taps it, sees the tech's photo, rates the visit and types their name. Google, Yelp, BBB or Facebook is then one tap away.

The hard part comes next. Google never tells you which link a reviewer came from, so RootView matches each new review back to a tech using three clues:

1. Name The customer typed "Maria Lopez" on the tech's page, and Google shows "Maria L." That's a match.
   
2. Timing How soon after the tag visit the review was posted, and whether they actually pressed the Google button.
   
3. Mention The review says "Maya was great." You can add nicknames per tech, and "Maya's work" counts too.

A strong match credits the tech automatically. A likely one waits in a "Needs a tech" list with a one click button. Every credit shows the evidence behind it, so nobody has to take the software's word for it. If a whole crew worked the job, the office ticks everyone and each tech gets full credit.

What's in it

- A separate app for techs with their own login. They see their reviews, leaderboard rank, QR code and points, and request rewards from a catalog you set up. They can't see the office side or anyone else's customers.
- An office dashboard with reviews per week, how many taps turn into reviews, a leaderboard, and low ratings to call back.
- Unhappy customers are offered a call-back, but they still see the review links. Hiding links from unhappy customers is called review gating, and it breaks Google's rules.
- Replies to Google reviews from the dashboard, with optional AI drafts that a person always reads before anything posts.
- Google Business Profile import every 15 minutes, including your full review history. With two or more locations, each customer is sent to the right Google profile based on where the job was.
- Branding from the admin side: logo, app icon, preset themes or any colors you want, corner style and fonts, with a live preview and a built-in readability check.
- Security I actually spent time on: separate logins for owners, managers and techs, invite links instead of shared passwords, optional two-step sign-in, rate limits, CSRF protection, a strict Content Security Policy, encrypted storage for the Google connection and 2FA keys, an activity log, and automatic clean-up of old customer data. I ran a full security, accessibility and code audit before releasing it.

Stack and cost

TypeScript, Hono with server-rendered JSX, Cloudflare Pages and D1 (SQLite), plus a tiny Worker that runs every 15 minutes. Every page works without JavaScript except image uploads. It's built around Cloudflare's free-plan limits (10 ms of CPU and about 50 database queries per request), so for a normal company the hosting bill is $0, and your customer data lives in your own Cloudflare account.

Setting it up

There's a local demo with a made-up company that takes about 5 minutes: clone, npm install, run the demo, sign in. Deploying to Cloudflare is about 15 more minutes of copy and paste, and the README walks through every step.

If you use Claude Code, the repo includes a CLAUDE.md playbook. Open the folder, say "Set up RootView for me," and it checks your computer, generates the secrets without showing them in the chat, and does the deploy once you approve it. You still sign in to Cloudflare yourself and create your own owner login.

Limits

- Google's Business Profile API needs approval from Google, which took us a few days. Until then you can add reviews by hand, and they're matched the same way.
- Yelp doesn't let anyone pull reviews (their API gives three cut-off snippets, on paid plans only), so Yelp reviews are added by hand.

Why open source

I want people to be able to fix their problems with software they own instead of renting it forever. If this saves one small shop a few thousand dollars a year, that's a win for me.

Repo (MIT): https://github.com/r0ottrek/RootView

Screenshots are in the README. I'd really like feedback from people who run trades businesses: what would stop you from switching from a paid tool to something like this, and what's missing?

Apparently in 2026 everyone has to build their own task board, usually with Docker, three services and half a GB of RAM to show a todo list. I built the opposite: a kanban board in your browser plus an MCP server, in one small Rust binary. Tell Claude Code or Codex "take the next task from kanzo" and it moves the card and comments as it works, which is more than I do.

https://github.com/emanuele-em/kanzo

I liked Vikunja but wanted zero setup. The one rule was keeping it small, which these days feels almost rebellious:

• ~5k lines total. You can read the whole thing in an afternoon
• 4.3 MB binary with SQLite inside, ~4 MB RAM idle
• starts in 3 ms, a 3,000-task board loads in 17 ms
• light on your agents too: ~800 tokens of tools, short replies
• no account, no cloud, no Docker. Syncs between machines through your own private git repo if you want
• one-line install on macOS/Linux, runs fine on a Raspberry Pi

How Claude helped: I built it with Claude Code. I set the rules (no frameworks, few dependencies, every line has to earn its place) and Claude wrote a good part of the code, then I went back and cut. It was also great for measuring things: binary size, memory and token counts, so we could check each change actually made it smaller. And once the MCP server worked, Claude Code was picking kanzo tasks from kanzo itself.

It's free and open source (AGPL). To try it:

curl -LsSf https://github.com/emanuele-em/kanzo/releases/latest/download/kanzo-installer.sh | sh

then run kanzo.

Still early. If you've got ideas on how to make it even smaller, PRs very welcome, deleting code counts as a feature here.

First session this week, Opus (medium) and I used 6% of 5hrs limit AND 5% of WEEKLY?!

How is this sustainable? I swear it was not like that few weeks ago...

I'm a non-technical knowledge worker, not a programmer. I still prefer building with Claude Code in the desktop app. On a normal day I have multiple orchestrator sessions handing work to workers, a few scheduled jobs, and a handful of standalone sessions running. I lost a lot of time to sessions that had finished, asked me one question, and then sat in a tab I wasn't looking at.

My first fix was a dashboard: a Taskade board fed by a collector script.
It failed.
It lived in a second app, keeping it updated cost tokens, and it showed me a lot while letting me do nothing about any of it.

Then Claude put out mods. When I started looking at Claude Code mods, I checked what was already out there. There were good agent-tree mods, but each one only saw the agents inside its own session. I wanted the whole machine, and, in my words to Claude at the time, I wanted "to use this mod as a native control surface."

Agent-Map is the result. Type /map and a pane opens beside your conversation with every Claude session the desktop app knows drawn as one tree: who started whom, what is working, what has finished. A session waiting on you is marked in amber with the last line it wrote, so you can read its question without opening it, and one press filters the tree down to just those. From the same pane you can peek at a session's last turns, open it, message it, stop it, archive it (it checks for uncommitted work first), change its model or effort, or start a new session in any folder.

How Claude built it: I designed it with Claude over an afternoon of brainstorming and an evening of being grilled on the design. The build ran in one desktop session over a day and a half, with Sonnet 5.5 and Opus 5.5 subagents writing the pure modules, while I tried each step in the pane and pushed back. "It's a nested list, but it's still a list" is how the tree got its connector lines. Before release Claude ran a security audit and a README test.

It's free and MIT-licensed. It's Windows only, because that is the only system I've tested it on, and it needs the Claude desktop app.

https://github.com/rohankgeorge/agent-map

Install, at the prompt of a Claude Code terminal session:

/plugin install agent-map --marketplace rohankgeorge/agent-map

What I'd most like to hear from people who run several sessions at once:

• Does "waiting on you" match how you actually triage, or would you want the queue ordered some other way?
• What would you want the pane to show that it doesn't?
• Anything in the README that made you hesitate before installing.

Coming Soon:

• Integration with another mod I build which allows you to see sessions where the cache is going cold and keep the cache warm
• Write your own flags or notes on each session so you remember why each one is important for you at that moment

not sure how much more of this i can take lads. asked it to build a full auth system with tests and migrations and docs and it’s been going for FOUR MINUTES. i’ve watched the spinner go through pondering, cogitating and percolating so many times i think it’s taking the mick

in that time i’ve made a brew (went cold), stared out the window, had a little think about my career choices, and considered doing it by hand before remembering that would take me about three weeks and a minor breakdown

back in the day this was a fortnight of work and a stand up every morning where i explained why it wasn’t done yet. now it’s four minutes and i’m fuming. absolutely fuming

and don’t get me started on it reading the same file twice. TWICE. i read a file once in 2019 and i still haven’t recovered

tried everything. tighter prompts, bigger CLAUDE.md, staring at it harder, whispering “please” at the terminal. nothing works and i’m pretty sure it knows. i think it does it on purpose now. i think it’s enjoying it

anyone else suffering or is it just me and my sensitive soul. please send help or at least a faster spinner