<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: StanAngeloff</title><link>https://news.ycombinator.com/user?id=StanAngeloff</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 29 May 2026 16:17:34 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=StanAngeloff" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by StanAngeloff in "Claude Opus 4.8"]]></title><description><![CDATA[
<p>> [..] Early access users and teams inside Anthropic have been using dynamic workflows for a wide range of use cases [..]<p>> ### Rewriting Bun with dynamic workflows<p>> An example of what dynamic workflows can unlock at scale is the recent rewrite of Bun. Jarred Sumner used dynamic workflows to port Bun from Zig to Rust [..]<p>That's very interesting to hear!</p>
]]></description><pubDate>Fri, 29 May 2026 12:00:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=48322028</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=48322028</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48322028</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude.ai unavailable and elevated errors on the API"]]></title><description><![CDATA[
<p>All it took for Codex to resume a stalled Claude Code session:<p>> I'm working with Claude Code on session aaaaaaaa-bbbb-1223-3445-abcdefabcdef which I'd like to hand-off to you, do you know how to read the session, my input and Claude's output so we can resume where I left off?<p>gpt-5.5, medium effort. "Resumed" session fully in under 2 minutes. Outages like today's are so common that I've now got the time to re-evaluate Codex every other day.</p>
]]></description><pubDate>Tue, 28 Apr 2026 18:42:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=47938663</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47938663</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47938663</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Show HN: Ctx – a /resume that works across Claude Code and Codex"]]></title><description><![CDATA[
<p>I've actually had the same itch and decided to give it a go ... So far I'm one year into the project, learned a ton and highly recommend to anyone who'd listen - try writing you own harness. It can be fun, it can be intoxicating, it can also be boring and mundane. However you'll learn so much along the way, even if you thought you already were well versed.</p>
]]></description><pubDate>Tue, 21 Apr 2026 19:21:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=47853279</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47853279</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47853279</guid></item><item><title><![CDATA[New comment by StanAngeloff in "CC – API Error: 500"]]></title><description><![CDATA[
<p>Dupe <a href="https://news.ycombinator.com/item?id=47753643">https://news.ycombinator.com/item?id=47753643</a></p>
]]></description><pubDate>Mon, 13 Apr 2026 15:49:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=47753779</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47753779</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47753779</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude.ai down"]]></title><description><![CDATA[
<p>This is affecting lots of users (myself included) and has prompted an official status page update, so it's very much real for users, but I guess only on claude.ai. Are you using Claude models through something/someone else?</p>
]]></description><pubDate>Mon, 13 Apr 2026 15:47:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=47753744</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47753744</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47753744</guid></item><item><title><![CDATA[New comment by StanAngeloff in "[dead]"]]></title><description><![CDATA[
<p>Dupe <a href="https://news.ycombinator.com/item?id=47753643">https://news.ycombinator.com/item?id=47753643</a></p>
]]></description><pubDate>Mon, 13 Apr 2026 15:45:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=47753711</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47753711</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47753711</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Ask HN: Is Claude Down Again?"]]></title><description><![CDATA[
<p>Yes <a href="https://news.ycombinator.com/item?id=47753643">https://news.ycombinator.com/item?id=47753643</a></p>
]]></description><pubDate>Mon, 13 Apr 2026 15:43:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=47753674</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47753674</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47753674</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Tell HN: Claude Opus elevated "Internal server error" again"]]></title><description><![CDATA[
<p>Officially down <a href="https://status.claude.com/incidents/6jd2m42f8mld" rel="nofollow">https://status.claude.com/incidents/6jd2m42f8mld</a><p>Discussion: <a href="https://news.ycombinator.com/item?id=47753643">https://news.ycombinator.com/item?id=47753643</a></p>
]]></description><pubDate>Mon, 13 Apr 2026 15:42:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=47753663</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47753663</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47753663</guid></item><item><title><![CDATA[Tell HN: Claude Opus elevated "Internal server error" again]]></title><description><![CDATA[
<p>No official report as of yet on https://status.claude.com/ however my team's sessions across different accounts have been ridden with errors the last 5-10 minutes.<p>This is more of a "it's not just you" post for those affected since Claude's status page is useless ("All Systems Operational"!)</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47753630">https://news.ycombinator.com/item?id=47753630</a></p>
<p>Points: 3</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 13 Apr 2026 15:40:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=47753630</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47753630</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47753630</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Issue: Claude Code is unusable for complex engineering tasks with Feb updates"]]></title><description><![CDATA[
<p>I did my usual thing today where I asked a Sonnet 4.6 agent to code review a proposed design plan that was drafted by Opus 4.6 - I do this lately before I delved into the implementation. What it came back with was a verbose output suggesting that a particular function `newMoneyField` be renamed throughout the doc to a name it fabricated `newNumeyField`. And the thing was that the design document referenced the correct function name more than a few dozen times.<p>This was a first for me with Sonnet. It completely veered off the prompt it was given (review a design document) and instead come out with a verbose suggestion to do a mechanical search and replace to use this newly fabricated function name  - that it event spelled incorrectly. I had to Google numey to make sure Sonnet wasn't outsmarting me.</p>
]]></description><pubDate>Mon, 06 Apr 2026 17:03:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=47663637</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47663637</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47663637</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude Code is unusable for complex engineering tasks with the Feb updates"]]></title><description><![CDATA[
<p>I missed that from the long issue, thanks for pointing it out! My experience with Opus today was riddled with these to the point where it was driving me completely mental. I've rarely seen those self-contradictions before, and nothing on my setup has changed - other than me forcing Opus at --effort max at startup.<p>I wonder if this is even more exaggerated now through Easter, as everyone’s got a bit extra time to sit down and <play> with Claude. That might be pushing capacity over the limit - I just don’t know enough about how Antropic provision and manage capacity to know if that could be a factor. However quality has gotten really bad over the holiday.</p>
]]></description><pubDate>Mon, 06 Apr 2026 16:52:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=47663465</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47663465</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47663465</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude Code is unusable for complex engineering tasks with the Feb updates"]]></title><description><![CDATA[
<p>I used to one-shot design plans early in the year, but lately it is taking several iterations just to get the design plan right. Claude would frequently forget to update back references, it would not keep the plan up to date with the evolving conversation. I have had to run several review loops on the design spec before I can move on to implementation because it has gotten so bad. At one point, I thought it was the actual superpowers plugin that got auto-updated and self-nerfed, but there weren't any updates on my end anyway. Shrug.</p>
]]></description><pubDate>Mon, 06 Apr 2026 16:45:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47663350</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47663350</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47663350</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude Code is unusable for complex engineering tasks with the Feb updates"]]></title><description><![CDATA[
<p>You say you've used it for months, I wonder if the example you gave was recent and if you've been noticing an overall degradation in quality or it's been constantly bad for you?</p>
]]></description><pubDate>Mon, 06 Apr 2026 14:31:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=47661440</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47661440</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47661440</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude Code is unusable for complex engineering tasks with the Feb updates"]]></title><description><![CDATA[
<p>That is the kind of thing that I've been fighting by being super explicit in CLAUDE.md. For whatever reason, instead of being much more thorough and making sure that files are being changed only after fully understanding the scope of the change (behaviour prior to Feb/Mar), Claude would just jump to the easiest fix now, with no backwards compatibility thinking and to hell with all existing tests. What is even worse is I've seen it try and edit files before even reading them on a couple of occasions, which is a big red flag. (/effort max)<p>Another thing that worked like magic prior to Feb/Mar was how likely Claude was to load a skill whenever it deduced that a skill might be useful. I personally use [superpowers][1] a lot, and I've noticed that I have to be very explicit when I want a specific skill to be used - to the point that I have to reference the skill by name.<p>[1]: <a href="https://github.com/obra/superpowers" rel="nofollow">https://github.com/obra/superpowers</a></p>
]]></description><pubDate>Mon, 06 Apr 2026 14:14:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=47661215</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47661215</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47661215</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Issue: Claude Code is unusable for complex engineering tasks with Feb updates"]]></title><description><![CDATA[
<p>(Being true to the HN guidelines, I’ve used the title exactly as seen on the GitHub issue)<p>I was wondering if anyone else is also experiencing this? I have personally found that I have to add more and more CLAUDE.md guide rails, and my CLAUDE.md files have been exploding since around mid-March, to the point where I actually started looking for information online and for other people collaborating my personal observations.<p>This GH issue report sounds very plausible, but as with anything AI-generated (the issue itself appears to be largely AI assisted) it’s kind of hard to know for sure if it is accurate or completely made up. _Correlation does not imply causation_ and all that. Speaking personally, findings match my own circumstances where I’ve seen noticeable degradation in Opus outputs and thinking.<p>EDIT: The Claude Code Opus 4.6 Performance Tracker[1] is reporting Nominal.<p>[1]: <a href="https://marginlab.ai/trackers/claude-code/" rel="nofollow">https://marginlab.ai/trackers/claude-code/</a></p>
]]></description><pubDate>Mon, 06 Apr 2026 13:54:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=47660970</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47660970</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47660970</guid></item><item><title><![CDATA[Issue: Claude Code is unusable for complex engineering tasks with Feb updates]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/anthropics/claude-code/issues/42796">https://github.com/anthropics/claude-code/issues/42796</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47660925">https://news.ycombinator.com/item?id=47660925</a></p>
<p>Points: 1364</p>
<p># Comments: 753</p>
]]></description><pubDate>Mon, 06 Apr 2026 13:50:35 +0000</pubDate><link>https://github.com/anthropics/claude-code/issues/42796</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47660925</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47660925</guid></item><item><title><![CDATA[Show HN: I built a full LLM chat client as a Neovim filetype]]></title><description><![CDATA[
<p>I started Flemma because I wanted to bring my AI workload into Neovim.<p>My workflow started with me living in developer portals - Claude Workbench, OpenAI Platform, Vertex (the horrors of GCP's Console UI!) I would spend hours in these web UIs crafting prompts, iterating on system instructions, maintaining a carefully curated library of sessions. But the browser really wasn't optimised for this kind of interaction. Editing was clunky (muscle memory <C-W> would close the tab instead and wipe my work), going back and forth between the LLM and myself felt off. So I had an idea: what if I could turn a Markdown document into an LLM chat interface?<p>At first I thought that would be enough - just do what I was already doing in the browser... but in Neovim. And sure enough having been accustomed to my own setup for the last decade I immediately felt a productivity boost. Writing functional requirement documents, statements of work, deep research across different systems - all of it felt better in "my" editor.<p>I then had a taste of Aider... and Claude Code... and all the other tools that were coming out. And Flemma felt lacking. So I started building: tool support, better conversation organisation, a proper UI to tame the noise that tool calls introduce.<p>Today, Flemma is a fully evolved AI workspace. It runs autonomous agent loops, interacts with multiple LLMs (Anthropic, OpenAI, Vertex, Moonshot) and lets you switch providers mid-conversation - something I do occasionally during research, asking two or three different models for their take on a problem, then combining findings into a final document.<p>Under the hood, .chat files are just Markdown with role markers (@You:, @Assistant:), but Flemma treats them as a proper filetype with its own parser, AST, LSP server, template engine and sandboxed tool execution. The buffer *is* the state - no hidden database, no JSON history, no server process. Your conversations are portable, greppable and version-controllable (I backup mine in Git). You can close Neovim, reopen the file a week later and pick up exactly where you left off.<p>It's got prompt caching, extended thinking, 7 built-in tools, a layered config system that gets out of your way and a UI that keeps getting refined to bring the noise down and make long agent sessions pleasant to work in (not quite there yet).<p>Flemma is for anyone who'd rather stay in Neovim. If that's you, I'd love to hear what you think.<p>Repo: <a href="https://github.com/Flemma-Dev/flemma.nvim" rel="nofollow">https://github.com/Flemma-Dev/flemma.nvim</a><p>Demo: <a href="http://flemma.dev/flemma.nvim/blob/develop/README.md#-flemma" rel="nofollow">http://flemma.dev/flemma.nvim/blob/develop/README.md#-flemma</a></p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47599302">https://news.ycombinator.com/item?id=47599302</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 01 Apr 2026 11:08:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=47599302</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47599302</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47599302</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude Code 500s"]]></title><description><![CDATA[
<p><a href="https://status.claude.com/incidents/mhnzmndv58bt" rel="nofollow">https://status.claude.com/incidents/mhnzmndv58bt</a> Sonnet is not affected, so far.<p>EDIT: and inevitably 10 minutes into the Opus outage the dreaded 529 Overloaded on Sonnet appears.</p>
]]></description><pubDate>Tue, 17 Mar 2026 19:47:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=47417357</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47417357</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47417357</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Ask HN: What Are You Working On? (March 2026)"]]></title><description><![CDATA[
<p>I've been working on an AI workspace inside Neovim (and using the editor as the TUI). When I started, I asked myself, "Wait, WHAT?! Another one? Who would use this?" However the goal was never about eyes (well, GH stars) on this new thing, it was about learning.
I wanted to dig deeper into how modern-day tools work so I can understand the sort of 'magic' I was experiencing using tools like Claude Code. The more I've been working on this side project, the more I understand about AI systems, agent loops, prompt engineering and all the cleverness that goes into making a good, usable, magical AI agent.</p>
]]></description><pubDate>Mon, 09 Mar 2026 09:40:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=47306769</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47306769</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47306769</guid></item><item><title><![CDATA[New comment by StanAngeloff in "Claude Status – Elevated error rates across multiple models"]]></title><description><![CDATA[
<p>Also affects Claude Code, not just API use (this incident was originally reported as "500s for public-api").</p>
]]></description><pubDate>Wed, 25 Feb 2026 17:19:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=47154490</link><dc:creator>StanAngeloff</dc:creator><comments>https://news.ycombinator.com/item?id=47154490</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47154490</guid></item></channel></rss>