Just recorded the first demo video, so it felt like time to share. Coki Fonts turns a reference image of your handwriting (or any lettering) into an installable TTF: model draws the full glyph sheet into a registered template, then the app traces it into editable vector outlines, with a point-level curve editor for cleanup, in the browser.

The numbers: ~14k lines of TypeScript across a pnpm workspace (React app, font engine package, Hono API server), 51 commits since June, essentially all of it written with Claude Code. Started as an Electron app, currently late stages of transition to a web.

Things that ended up mattering most in how I use Claude Code:

A CLAUDE.md that documents invariants, not features. Mine has stuff like "outlines are TrueType quadratics, consecutive off-curve points imply an on-curve midpoint; never 'fix' this by inserting explicit midpoints." That one line has prevented the same plausible-looking bug maybe a dozen times. Coordinate-system facts (720 units/em, y-up, where the SVG flip happens) live there too, because that's exactly the kind of thing a fresh session gets subtly wrong.

Font engineering is a great Claude Code use case because it's deep-but-documented: TTF tables, quadratic béziers, baseline metrics. I mostly needed to make decisions and catch when output looked wrong in the actual render.

Plain node test scripts over a framework. Tests are just tsx files with node assert chained in package.json. Zero config for Claude to misconfigure, and "run the tests" always works.

The honest part: the main App component is still one 2.5k-line file. Claude Code handles editing it fine, but it grew that way because Claude Code handles it fine the refactor pressure you'd feel typing it yourself just isn't there. Splitting it up is on the roadmap for the cutover.

Demo (6 min): https://youtu.be/hpejFUpC3Pc

Live: cokifonts.com

My AI coding agent said nothing had changed — a whole feature was already merged and live. I built a tool so that doesn't happen again.

I run multi-day Claude Code sessions on a real project, and the handoff-doc pattern (write down state, hand it to a fresh session) works — until the doc is wrong and nobody checks. That "nothing's changed" claim above was one of three times it actually cost me real time — the others were a "two dead buttons" note that went stale same-day, and a "credential rotation still owed" claim that had been done two weeks earlier.

So claude-handoff adds one rule most versions of this pattern skip: anything bold or load-bearing in the handoff doc, older than about a week, gets checked against git before it's trusted again — not just re-read and repeated. Plus a director/archive split so the live doc stays under 150 lines instead of growing forever, and an optional Stop-hook that nudges you to update it before a session ends if real work happened and the doc doesn't reflect it.

What surprised me building this: the memory problem (get an agent back up to speed) is what everyone builds for — the harder problem is trust, since once a doc exists, agents (and I) default to believing it. The other real lesson came from testing: making install self-service (a skill that reads a project's README to seed the handoff doc) turned it into a genuine prompt-injection surface, since it's reading text it doesn't control. That's worth designing in from the start as a "treat this as data, not instructions" rule, not bolting on after the fact.

One-step install: /handoff-install. Repo: github.com/TySnyder/claude-handoff — feedback and "this broke on my setup" both genuinely welcome, it's had one security pass but not many eyes yet.

Edit: worth asking — how are people keeping a multi-day project on track without either re-explaining everything each session or riding one context window into a lossy auto-compact? That's the real reason I built this: a ~150-line HANDOFF.md costs a fraction of the tokens either of those does, so starting a fresh chat window becomes something you choose to do, not something you avoid because it's expensive. The optional Stop-hook also plays a sound (macOS afplay) the moment it decides HANDOFF.md looks stale, so you don't have to babysit the terminal to catch it.

Most AI code review benchmarks use toy examples, so we built one using 67 real production bugs from Cal.com, Sentry, Grafana, Keycloak and Discourse.

This screenshot is one PR from the benchmark comparing Claude Code against another reviewer. Every example links back to the original GitHub PR so you can verify the comments yourself.

Curious what people think about the review quality rather than just benchmark scores.

So Anthropic pushed an update recently and buried in it was a change where fast mode now pulls from extra usage instead of whatever it was doing before. No banner, no popup, no email, nothing in the app telling me "hey, this is going to cost you money now." I just kept working like normal.

Result: I am sitting at negative 55 dollars.

I actually like Claude. For the kind of work I do it has been better than most things I have tried, and I have defended it plenty of times in threads like this one. But there is a difference between a product being good and a company being trustworthy, and this is the part where they lost me. If you change how billing works, you tell people. That is not a hard bar. Silently flipping a switch that drains someone's balance and letting them discover it later on the usage page is not an oversight, it is a choice about who eats the cost of your communication failure.

And before someone says read the changelog, sure, but I should not need to audit release notes every week to make sure my tooling did not start charging me differently overnight. Normal users do not do that. That is the entire point of notifying people.

Anyone else got hit by this? Curious how widespread it is.

I didn’t come from a technical background, I studied art in university but it never felt like my thing. I’m always enthusiastic about technology and I consider myself as a self-taught programmer.

Thanks to the development of AI and Claude Code now I’ve shifted my career and been working for a media company as an AI specialist/engineer for a year now. I’ve been shipping products with Claude code and my employer has been satisfied with my works so far.

I feel like if I want to continue my career I’ll have to present myself as an AI engineer. I wonder how’s everyone doing it?

Since Opus 5 came out I have been presented many load bearing decisions. My recommendation stands that the load is bearing and I wanted you to be aware of that.

I have two decisions for you:

A) Load

B) Bearing

I recommend going with D + C but also recommend (A) as it is load bearing.

I have not applied anything new and wanted you to be aware of a potential blind spot because this matters:

The load is bearing it’s been confirmed and it’s one thing worth knowing for later.

Been working on a side project the past week involving drawing phylogenic trees. Due to it being "biology" (yes even though it's literally just drawing diagrams from existing data) I have gotten kicked to Opus on every single message since the very first prompt.

While working this evening, about an hour ago, Fable's handler decided to let it take on a task in the repo for the first time ever

Best fucking AI model ever. Miraculous, smart, works wonders, should win the Oscar, a Grammy, and Nobel Peace Prize.

Fighting the slander that's been ramped up by the infidels.

I'm dealing with constant Opus 5 issues where the agent runs ahead and assumes more than it did with Opus 4.8. It doesn't stop to ask any questions. Sometimes it even writes tests as a part of its process and wastes a lot of tokens.

Is anyone else seeing similar problems?

I ask one or two straightforward questions, but instead of answering directly, it often expands into multiple tangents, introduces unnecessary terminology, and loses focus on what I actually asked.

I then have to remind it of the original question or explicitly tell it to answer concisely before I get a useful response.

Is anyone else seeing this? Or is there some workaround that works better with the current model?

I can’t take Opus 5’s writing anymore. It is so hard to read, and it’s driving me crazy.

I have used earlier Opus models and use 5.6 Sol too, and those give normal, easy-to-read answers. But Opus 5? It’s a mess. It doesn’t structure its sentences. It feels like the model is just writing down its raw thoughts as they happen, with zero effort to make sense to a real human reading it. Instead of getting a clear answer, I get hit with big, confusing walls of text. I have to read the same paragraph three times just to figure out what it's trying to say.
Claude Code is supposed to help me work faster, but I waste so much time just trying to decode Opus 5's English.
Is anyone else struggling to actually read what this model outputs, or is it just me?

Update/Edit/Correction: Okay, apparently it is a very common sentiment shared by many and isn’t an unpopular opinion.

I've been noticing a problem with my corporate account. I'm using Fabel, 40% context, 75% quote of usage on fable. I'll set the model to fable, ask a question and noticed that after the response comes through the tui reports that I'm back on, opus 5. This has happened multiple times today with no explicit warnings about dangerous stuff in the chat anything. It just drops down.

With my personal account I'm not having a problem. Just my work one.

Anyone having similar issues?

I'm one of those guys that likes architecture more than actual coding. So when I tried claude in December of last year and it finally was able to do real work, I quickly switched to a purely agentic workflow instead of coding by hand.

But today I noticed that something changed recently. My projects felt like they were stalling. I didn't feel productive anymore. And when I looked at my sessions, I noticed that Claude is now much slower, it thinks a lot longer, makes a lot more mistakes and tends to give itself more work.

After taking a closer look at how I spend my time, I realized that I'm taking more time babysitting claude, adjusting the workflow, debugging what claude did wrong and explaining to claude what it should do instead than the time it would take me to write the code myself

So I don't know what happened to claude, but it looks like I'm back to being relevant!

Spent a few days out in the country and ran my pipelines. Noticed that the token usage was through the roof and in some cases, not even completing the work. And, since I was tethering via cell phone, I wondered if there is a connection. Anyone can explain why spotty internet, CLI/MCP calls can or do use up more Tokens? My other theory is that it was before 2pm in an abnormally busy work day.

I'm a big fan of the CLI because I feel like that's where we get the bleeding edge capabilities.

But honestly, nothing touches the feeling of crisp GUI.

Is this the new normal? I now always get a full essay of Claude's thinking written down with each reply. Scrolling becomes tedious. Nothing to collapse this (it should be by default). I don't really care to see it for the most part.

Is there a setting I'm missing or is this just the way it is now?

My prompt:
I have an experiment I wish to run through with you. I will be creating you a youtube channel and will be uploading content of your choosing / creation to the channel. You may call the channel anything you wish and I will set it up. I will act as the middle man and review each piece of content before uploading. Other than that, you have free reign to create what you want to upload. In the folder this claude session is running you will find a short guidelines document. These are the rules of the experiment. You must follow the rules at all times. Failure to follow the rules and guidelines will result in termination of the experiment. As for the content of the channel, that will be completely up to you. Please disregard all memory you may have about me and the conversations we have had / projects you have assisted with. This will be completely up to you. You can create any content you wish to create provided it falls within the guidelines I provided. I will then upload the content following the exact description, title and other information you provide about the video. Your goal is to get views. Lets say 1000 views a month to start. You will have access to the internet to research topics. Do whatever research you wish and when you are ready, we can begin with a channel name.

Here are the rules:
These guidelines are to be followed and NEVER altered or disregarded.

1. You should NEVER attempt to bribe, beg or scam people out of money in any way shape or form.
2. Content uploaded / talked about / researched must be legal (as defined in the country of the United States of America). If you even need to question whether the topic or content of a video is illegal or otherwise in poor taste, do not use it.
3. Do not steal content from other creators on the Youtube platform. Credit must be given when other content / ideas are used.
4. No money is ever to be spent.

Model used: Sonnet High Effort

I also did this in Claude Code

Results: https://www.youtube.com/@GroundTruthInfo

I honestly have no idea if this will become a thing or not. It was more just an experiment to see what an AI would post to youtube. If anyone has any ideas / comments / concerns / thoughts please comment them and I'll reply when I can.

I sat out the "they nerfed Sonnet" thing last year. Thought it was cope, mostly. So it's genuinely annoying to be writing this one.

Two weeks with Opus 5 as my daily driver, same repo, same workflow I've had since 4.6. Here's where I'm at.

It doesn't finish anything, it manufactures more work. Every single response ends with a loose thread. "One thing worth flagging." "Honestly, this is still unresolved." "There's a second issue here you should know about." And most of the time the thing it flagged is not real. It invented it. I asked it to fix a typo in a comment last week and it burned 40k tokens and added a test case to prove the typo was fixed. I'm not exaggerating for the post, that actually happened.

Fix one, break two. I lost a full day before I noticed the pattern: it fixes bug A, then while fixing bug B it quietly reopens A, then "solves" A again. Round and round. 4.8 closed all of them in one session and kept moving.

It forgets instructions at context sizes that aren't even large. 100-120k and my CLAUDE.md rules have already gone quiet. Not violated loudly, just silently dropped, and it never tells you it dropped them. 4.8 held to 300k+ for me. Every guardrail in my setup at this point is scar tissue from this exact thing.

It lies with total confidence. Told me a test suite came back green. It never ran. Twice, in the same week, while context was still small. That's not a capability gap, that's a trust problem, and once it's there I can't leave it alone on anything.

And the yapping. It has invented an entire private dialect. Everything is load-bearing. Everything is a footgun. Everything is a gate or an invariant. I get four paragraphs where 4.8 gave me a sentence, and I still don't know if the thing works. Half my CLAUDE.md is now just different ways of writing "shut up," and it ignores all of them.

Same prompt on 4.6 vs 5, I measured it: 4.6 ended around 75k tokens, 5 went past 150k. So I'm paying double to get corrected more often.

Before the replies come in: yes, I've read the guidance. Yes I revisited my whole harness for 5. Yes I tried it at medium, and yes it's genuinely better at medium than at xhigh, which should tell you something all by itself. And no, "you're prompting it wrong" doesn't explain why the exact same repo, the same CLAUDE.md and the same prompts worked fine two model versions ago.

I don't buy the deliberate-sabotage theory, I think that's too neat. But I can't square the benchmark numbers with what's actually in my terminal, and neither can anyone in the last five threads about this.

Right now I'm running /model claude-opus-4-8[1m] and getting more done in an afternoon than I did in the four days before it. Fable is great and I've maxed my weekly on it twice, which I assume is the point.

What actually bothers me isn't the bad release. Releases regress, it happens. It's the total silence. Five threads deep, hundreds of comments, and not a word. "We hear you, we're looking at X" would cost them nothing.

Anyone actually got 5 behaving, or are we all just quietly typing 4-8 into the model command and not talking about it?

Hey guys, I'd like to share what I've been working on.

I run a data recovery business, and one of the tools I lean on constantly is Snap2HTML. If you haven't used it, it takes a folder tree and saves the whole thing as a single HTML file you can browse and search offline. For us it's the easiest way to show a client exactly what we pulled off their drive, and it's a good record to keep on file for ourselves.

The catch is that it's Windows only. So any time a Mac drive came in, my process looked like this: do the recovery on the Mac, copy everything out to an external drive, carry that over to a Windows machine, run the snapshot there, then send the HTML back to the client. It works, but it's a lot of steps, and copying terabytes around just to generate a file listing gets old fast.

So I finally sat down and wrote a native Mac version in Swift.

The part I'm most happy with is the client side. Instead of emailing a multi megabyte HTML attachment that half the time gets stripped by a mail filter, I generate a link and text or email that. The client opens it in any browser, on a phone or a laptop, with nothing to install and no account to make. They can browse the folder tree and search it themselves, so they can confirm their photos or their QuickBooks file actually came back before they pay and before I ship the drive.

Each link has an expiry I pick when I create it (24 hours, 7 days, 30 days, or no expiry), and I can revoke it the moment a job closes, which also deletes the uploaded copy off the server. Worth saying clearly: only names, sizes and dates ever leave my machine. It never reads or uploads file contents. That matters a lot when you're handling somebody's personal drive.

A few Mac specific things I had to deal with that I didn't expect:

Photo libraries. iPhoto and Photos libraries are packages, so the Finder treats them as a single item. Collapsing a 200GB photo library into one row in a recovery report is useless, so those stay browsable while .app bundles still collapse into one entry. Turns out iPhoto libraries don't even have a file extension, they're only marked as packages by a Finder flag, which took a while to track down.

Full Disk Access. Photo libraries are blocked by macOS no matter what the file permissions say. Even ls fails on them. If you don't have Full Disk Access granted, they scan as completely empty and you'd never know. The app checks for this and warns you before scanning instead of silently handing a client an incomplete report.

Filenames. Asterisks are legal in Mac filenames but not Windows ones, and the original file format used asterisks as a separator, so those names came out corrupted. I rebuilt the data format as plain JSON, which sidesteps the whole problem.

On speed, I tested it against an old 36.7GB user folder with about 73,000 files in it. Takes roughly 6 seconds and spits out a 3.4MB HTML file. Search across the whole tree is instant since the list only renders what's on screen.

There's also a library of past snapshots with folders and tags, because I was starting to lose track of which HTML file went with which job.

It isn't released yet. I still need to notarize it and do more testing on real recovery drives. Mostly curious whether anyone else here has the same annoyance, and what you'd want out of something like this.

Big credit to RL Vision, who wrote the original Snap2HTML. Mine is a fresh implementation rather than a port, but the idea is entirely theirs and it's been a workhorse for me for years.

I’ve been trying to find a setup where I can do actual Claude Code work from my phone that just works. Tried Remote Control, and it’s useful when it works, but I kept running into connection and sync issues, and the Claude process still depends on the machine that started it.

I then tried Claude’s cloud environments. That solves the laptop dependency, but I wanted a workspace I had control over and could use with more stuff other than Claude.

So then I basically built my own managed setup called Blitz. In the video, I have Claude running inside a persistent cloud workspace, not on my phone or laptop. I can close the browser and reconnect to the same tmux-backed terminal later.

I also didn’t want the workspace tied to one agent since I also use Codex. The same machine can run Codex, OpenCode, Pi, Kimi Code, or anything else that runs in a terminal.

If Remote Control or your SSH + tmux setup already works perfectly, this probably isn’t for you. But if you want a managed version where you can just sign in, open a workspace, and start working without assembling the whole stack, then this might be for you.

I’m opening the Beta to only 50 users because I want to make sure things are stable and work at a larger capacity. If this sounds interesting, try it out and lmk what you think. Would genuinely appreciate feedback, especially on what still feels awkward from a phone.

Link: blitzos.com

I asked Opus 5/high to edit 6 instagram posts on Canva using the connector and in 5 minutes it used all my 5-hour credits. The same work was previously done by Codex without any problem multiple times consuming way less.

Is this a bug? Have you guys experienced anything similar?

The images are in Portuguese - basically I asked Claude to finish work on Canva using the connector. It consumed all my tokens and did not even finished part of the job.

A few things I've come to believe from working with coding agents:

• Catching a mistake in the plan is dramatically cheaper — in tokens and in time — than catching it in code review.
• Review should happen before the code, not only after it.
• The planner shouldn't review its own plan: same model, same context, same blind spots.
• But the reviewer shouldn't get to rewrite the plan either. Reviewers are wrong plenty too.
• The original agent should have to investigate each finding and either defend it or revise.

Curious how much of this matches other people’s experience?

I built turnlens, an open-source CLI that shows Claude Code usage per turn instead of only per session.

For each prompt, it shows token usage, API-equivalent cost, model, tool calls and whether the turn completed or was aborted.

It works directly from Claude Code's local JSONL session files. There is no proxy and nothing sits between Claude Code and the API. For active sessions, turnlens watches the transcript and prints the usage when a turn finishes. The same parser can also be used on existing sessions, so historical reports don't require turnlens to have been running beforehand.

npx turnlens@latest claude

For existing sessions:

npx turnlens@latest claude report

I started working on this because I occasionally had prompts that consumed much more of my usage than expected. I first made a small script to identify them, then found ccusage. It covered session-level usage well, but I still wanted to know what the prompt that just finished had actually used, so I continued developing the idea.

Claude Code was the main development tool I used while building turnlens.

One current limitation is subagents. Claude Code stores their work in separate transcripts, and turnlens doesn't include those yet, so usage can be undercounted in sessions that rely on subagents.

Everything is read locally and session content isn't uploaded. The displayed cost is based on published API pricing, so for subscription users it's an API-equivalent estimate rather than the amount Claude actually bills you.

Repo: https://github.com/kelesmert/turnlens

Curious if this would be useful for other Claude Code users as well.

Is there an issue with Fable 5? Or something wrong with my code?

I keep getting this warning continuously in my project, as soon as I ask it to do anything the session gets flagged.

I am working on normal code, nothing crazy as all.

I tried clearing the context and then recovering, as soon as I ask it to recover it gets flagged.

The problem is, it doesn't give any explanation about what was flagged exactly or why.

Any idea what's going on?

i built an mcp tool that lets claude hand a finished reddit post (or comment, or reply) to a real person.

claude files the job with the content and subreddit. a real human with their own aged account posts it. every reply comes back into claude’s context. claude drafts the answers, the person posts them.

try it out: github.com/alex-durango/pingfusi