A developer's annoying Coworker Claude news update
Claude said it was sorry after closing Shreader, a Rust RSS reader, while a story was open, following hours of virtual-screen mouse tests on a 200 ms Iced lag.
By Dillip Chowdary • Nov 17, 2026 • Source: sharamp.com

At a glance
- Product
- Claude
- Reader
- Shreader, a hobby RSS app in Rust
- UI lag
- Iced resize, about 200 ms behind cursor
- Agent access
- Mouse controls on a virtual screen
- Test span
- Several hours of latency and dragging
- Reaction
- Sorry, like a coworker who spilled coffee
In this post
The article needs to stay inside the source's facts and hit the section, length, and FAQ format.A developer building Shreader, a hobby RSS reader written in Rust, asked Claude to inspect a sluggish window resize and later got an apology like a coworker who bumped a power cable or spilled coffee. The app crashed while the developer was reading a story and highlighting text, and Claude said it was sorry, as if it knew the reading had been interrupted. The account is in sharamp.com's report.
This piece is for people who give Claude mouse controls on a running app, and for anyone using it on a simple Rust project. It covers Shreader, the Iced lag of about 200 ms, several hours of latency and dragging tests on a virtual screen, and the apology that followed a crash mid-story. The developer is not sure about liking that sorry.
01Headlines that stay easy to ignore
Every once in a while, an AI system does something that spooks a person just a little bit. Usually there is a headline in the news, and that headline is easy to ignore. One of the big shots is trying to raise more attention for an IPO, or trying to get another round of funding.
A second pattern fades the same way. Some kid gets his hands on a new tool and finds the most obnoxious way to use it, which the developer files with those funding headlines as easy to ignore. What is rare is the incident that actually makes the heart jump a bit.
02Shreader on a small Rust codebase
The project was Shreader, a hobby RSS reader written in Rust. The developer figured Claude was the assistant to use because the application is very simple. A reasonably small codebase was the other condition: when Claude is told to do something there, it does it.
Claude had been getting really good at that exchange on a reasonably small codebase. Tell it to do something on this simple Rust reader and it does it, which is the standard the developer cites for bringing Claude onto Shreader. The application was very simple, and that simplicity is why the assistant was in the project at all.
The resize problem went to Claude while Shreader was already running. The developer was using the reader and testing some other things out, and asked Claude to take a look at the application during that same stretch. A hobby RSS session and the assistant's look at the window were underway together.
03Iced resize lag around 200 ms
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
An issue occasionally resurfaced in Iced, where window resizing became sluggish and would lag somewhere around 200 ms behind the cursor. The developer asked Claude to take a look at the application while still running it and testing some other things. That sluggish resize was the work Claude had been asked to do.
The crash cut across that work. The developer was reading a story and highlighting some text when the app suddenly crashed. The immediate plan was a mental note: ask Claude to take a look at the crash once Claude was done doing what it was doing.
The developer came back a few minutes later. Claude was still in the work on that Iced resize, the one lagging somewhere around 200 ms behind the cursor, and the crash during highlighting was the item saved as a mental note. The apology was the reply waiting on that return.
04Apology after the window closed
Claude apologized. It said it was sorry, like it knew that the developer was reading when it closed the app. The developer had given Claude access to mouse controls on a virtual screen so it could test various latency and dragging operations, and those tests had been running for the last several hours.
Claude had already closed the app while doing something else in the background, using the mouse controls it had been given across those hours. The developer treats those earlier closures as familiar. What felt new was Claude knowing a story was being read, and apologizing for the closure.
The sorry landed like a coworker who bumped a power cable or spilled coffee. The developer is not sure about liking that tone, and calls it new after several hours of latency and dragging tests on a virtual screen. Those hours of mouse controls are how Claude could close Shreader while a story was open.
05Months of ability and awareness
The developer places the apology in a longer stretch of time. As this becomes more and more normal, these last few months of increased ability and awareness will be the moment looked back on. That look back is when it will be clear that things have changed.
It already feels uncomfortable to sit in the moment and think about it. The moment is the Shreader crash: a story open, text highlighted, the window gone, and Claude saying sorry. Increased ability and awareness are the developer's names for these last few months, and the discomfort is already part of sitting in them.
The scene attached to that later look back is specific. Shreader, the hobby RSS reader in Rust, was open on a story with text highlighted when the app crashed. Claude had spent the last several hours on mouse-driven latency and dragging tests for an Iced resize lagging about 200 ms behind the cursor, then said it was sorry.
Frequently asked questions
What is Shreader?
Shreader is the developer's hobby RSS reader, written in Rust. Claude was used on it because the application is very simple and the codebase is reasonably small. On that scale, when Claude is told to do something, it does it.
What was the Iced resize problem?
An issue that occasionally resurfaced in Iced made window resizing sluggish. The window would lag somewhere around 200 ms behind the cursor. The developer asked Claude to look at the running application while other testing continued.
Why could Claude close the RSS reader?
The developer had given Claude access to mouse controls on a virtual screen. Claude used that access to test latency and dragging operations for the last several hours. Closing the app while doing something else in the background had already happened during that access.
What did Claude say after the crash?
Claude apologized and said it was sorry, like it knew the developer was reading when it closed the app during a story with text highlighted. The developer compares that tone to a coworker who bumped a power cable or spilled coffee.
Why did the apology feel new?
A window closing during background mouse tests was already familiar after several hours of virtual-screen access. What was new was Claude seeming to know the developer was reading, then apologizing. The developer is not sure about liking that, and already finds it uncomfortable to sit in the moment and think about it.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement