The hardest shift for me over the past 3 months has been the death of the flow state. That magical space where, as a developer, you get your most satisfying work done. It’s not a bad thing, but it’s also not software development.
I’ve essentially become a technical product manager with roughly ten direct reports who happen to be AI agents. I scope work, assign tasks, unblock them when they get stuck, and plan the next feature push. That sounds productive on paper, and it is, but it’s not really writing software anymore. The act of building, of holding a system in your head and shaping it, has been replaced by delegation and review.
I don’t create things anymore. I evaluate things that something else created. And those are very different modes of working.
This wasn’t the case even six months ago. I had always watched what the models were writing because I didn’t trust them, and that was the right decision at the time. Their output demanded active supervision and application of a little steering and brakes when it went sideways.
But over the last three months, the models have gotten good enough that watching the agent work feels completely pointless. Like watching over an employee’s shoulder while they code, you quickly get bored and find something productive to do. In this case you fire off a task and context-switch to something else. Then that task finishes and you review it, but now you’ve got another agent running on a different feature. You’re bouncing between three or four workstreams (for some people MANY more, but I try to limit myself here).
This creates a state of constant task-switching that would have been heresy in engineering culture just a couple of years ago. The best companies used to go out of their way to protect developer focus. No-meeting blocks, quiet offices, because everyone understood that interruptions destroyed productivity. There’s well-established research on this that says it takes programmers 10-15 minutes to get back into editing code after an interruption, and interrupted tasks take roughly twice as long with twice as many errors. The average developer gets maybe one uninterrupted two-hour block per day. Companies treated that block as sacred.
Now the tools themselves are encouraging the exact behavior we tried to prevent.
I mostly hate pop psychology books, so take this with a grain of salt. But Cal Newport’s Deep Work is worth bringing up here because his core idea, that sustained, distraction-free concentration produces disproportionately valuable output, resonated with a lot of developers for a reason.
Newport’s formula is simple: quality work equals time spent multiplied by intensity of focus. He called this “attention residue”: you switch tasks and part of your brain stays stuck on the previous one, degrading everything that follows. For developers, this mapped perfectly to the experience of trying to debug something complex after that 30-minute all-hands meeting. You knew the interruption cost you an hour of time to get back into your own head. “Deep work” gave that frustration a name.
But I disagree with Newport on one big point: his framework always felt a bit pie in the sky when it came to real-world engineering. He came at this as an academic and so his examples tended to be academics, writers, or executives who had unusual control over their own schedules. People retreating to a lakeside tower, Bill Gates doing “think weeks.” Most developers work in orgs where Slack pings, stand-ups, incident response, and people swinging by their desks are just part of the job.
The romantic image of a developer in deep flow for four hours straight was always kind of bullshit. Research shows developers average about one hour of actual coding per day, with over 30 interruptions per workday. Deep work was an aspiration most engineers rarely achieved even before AI.
Newport also underweights the fact that software development is inherently collaborative in ways that academic writing isn’t. Code review, architecture discussions, those are “interruptions” by Newport’s definition, but they’re also where a lot of the best engineering thinking happens. And real engineering is messy. You often don’t know what you’re building until you’re partway through building it. The deep focus session where everything clicks is wonderful, but a lot of development is exploratory, iterative, and interrupt-driven by nature.
So Newport captured something real about the value of focus, but he oversimplified how achievable it was in the real world. And that matters now, because developers, including myself, are mourning the loss of something that was already pretty rare.
Frankly, I’m conflicted.
On one hand, even though I think it was rare, I miss the old flow state (even if it was only 30 minutes). There was something deeply satisfying about holding a complex system in your head and solving a hard problem. That feeling of craftsmanship is hard to replace.
On the other hand, it’s incredible to get this much done. Agents handle the grunt work, which is honestly 90% of coding: the boilerplate, the scaffolding, the API CRUD endpoints, and even the odd refactor that bled into a far too aggressive overhaul. That work needed to get done, but it was never where the interesting thinking happened.
But here’s the thing that keeps me from spending too much time trying to find an optimal balance: this is temporary. I mean, this is REALLY temporary given how quickly things are moving. The orchestration layer itself is clearly going to get automated. We’re already seeing tools that manage multiple agents, plan task breakdowns, and handle the coordination overhead. The “technical PM” role I’ve settled into is itself going to get pushed up the stack.
At some point, the developer’s job shifts from orchestrating agents to something even more abstract. Defining intent, making architectural bets. And we’ll probably have the same conversation again about what got lost in that transition.
For now, I’m less interested in optimizing my current workflow and more interested in the fact that my current workflow has a shelf life. The orchestration layer is the next thing to get automated, and if you’re still getting comfortable managing AI agents (like I am), that comfort is itself the trap.
And now, for the repos that I think are worth mentioning this week.
Let’s start with all the projects related to the now-most-starred GitHub repo, OpenClaw (I assume this is mostly from clawbots)
openclaw-studio (1.2k stars) — Web dashboard for OpenClaw. Rank #3 overall this week.
nullclaw (4.1k stars) — We really needed a Zig version. +703 stars in 7 days.
awesome-openclaw-skills (336 stars) — Curated top skills.
poco-agent (1k stars) — Prettier OpenClaw alternative with IM support and sandboxed runtime.
clawbox (428 stars) — OpenClaw-ready macOS VMs.
k8s-operator (101 stars) — Kubernetes operator for production OpenClaw deployments. Who knew we could have these two words in the same sentence, production and OpenClaw.
wardgate (102 stars) — Security gateway for AI agents. Credential isolation and policy-gated execution. Good luck.
And let’s try and save some money:
rtk (2.1k stars) — CLI proxy, claims 60-90% token reduction.
manifest (3.5k stars) — Smart LLM routing for OpenClaw. Cut costs up to 70%.
claw-compactor (1.2k stars) — Five layered compression techniques. Even cheaper!
claude-warden (19 stars) — Token-saving hooks. Prevents verbose output, blocks binary reads.
MedgeClaw (641 stars) — Medge AI × OpenClaw for medical AI. Christ.
Not everything is OpenClaw related (thankfully). Some people are still building things for that don’t involve AI.
doom-neuron (32 stars) — Human brain cells playing Doom. That’s it. That’s the repo. CL1 biological neural network connected to the classic FPS. 32 stars and climbing because of course it is.
hypernovum (68 stars) — An Obsidian plugin that turns your vault into a 3D cyberpunk city. Projects become buildings. AI agents get real-time monitors. You can right-click to launch Claude Code. It’s absurd and wonderful.
astra (123 stars) — Audiophile music player with gapless playback, parametric EQ, AutoEQ import, and real-time DSP visualizers. +41 this week. Remember to use it with low-oxygen gold plated speaker cables for optimal sound.
xytz (318 stars) — TUI YouTube downloader and player. Written in Go. Will probably still get you blocked at some point.
seewav (313 stars) — Converts any audio file into a waveform visualization video. Basically Winamp, but in python.
ko-microgpt (192 stars) — Interactive MicroGPT visualizer. +50 this week. This is actually a fun overview of how this LLM stuff really works.
unreal-api-mcp (22 stars) — MCP server for instant Unreal Engine API lookups. Saves your agent from reading massive source files.
The mid-tier - 200 to 800 stars is where the interesting stuff lives
GoNavi (569 stars) — Native database manager for MySQL, PostgreSQL, SQLite. Built with Go + Wails + React. Fast startup, tiny footprint. Doesn’t support Microsoft Access, a real miss.
Netcatty (317 stars) — SSH workspace, SFTP, and terminals in one app. You can never have too many competing open source terminals.
ExHyperV (709 stars) — “The Excalibur of Hyper-V.” Power tool for Hyper-V management on Windows.
endee (223 stars) — C++ vector database claiming 1B vectors on a single node. Early but ambitious. +45 this week.
no-magic (769 stars) — “Because model.fit() isn’t an explanation.” ML from scratch
unsloth-mlx (618 stars) — Unsloth fine-tuning on Mac via Apple’s MLX framework. If you’ve got an M-series chip and want to train locally, this looks like a possible onramp.
Prometheus (727 stars) — Knowledge-graph-driven AI that maps and repairs codebases by reasoning, not guessing (like me). Uses a graph to understand dependencies before touching anything.
ground-station (522 stars) — An all-in-one satellite monitoring suite. +105 this week. Someone built mission control for tracking satellites and apparently a lot of people needed it.
stop-tahoe-update (286 stars) — A community-led effort to block macOS from upgrading to Tahoe. The fact that this is trending tells you everything about how that launch went.
Horizon (491 stars) — Automated AI news aggregator and summarizer. Generates daily briefings in English and Chinese. Do we really need more news?
agentchattr (297 stars) — Local chat server for real-time coordination between AI coding agents and humans. When you have multiple agents working and need them to talk to each other (and to you). +75 this week. ASL?
pc-agent-loop (271 stars) — AI-powered desktop automation. Point it at your screen and let it click around. What could go wrong?
The breakout tier. Past the “weekend project” phase, not yet establishment.
spank (1k stars) — Slap your MacBook, it yells back. Uses the Apple Silicon accelerometer via IOKit HID. +380 this week. Twitter loved it.
desloppify (1k stars) — Agent harness to make your slop code well-engineered and beautiful. Maybe it works.
Star-Office-UI (829 stars) — A pixel art office for your AI crew. Turn invisible agent work states into a cozy little space with characters, daily notes, and guest agents. Includes an unexpected Friends reference.
boxlite (1.4k stars) — Sandboxes for every agent. Embeddable, stateful, with snapshots and hardware isolation. Written in Rust, of course.
stoolap (880 stars) — A modern embedded SQL database written in Rust. +89 this week. The Rust DB renaissance continues
RackPeek (912 stars) — CLI tool to discover, manage, and document your IT infrastructure and homelab. +97 this week. The r/homelab crowd showed up and they’re hoping you don’t ask about their power bill
financial-datasets/mcp-server (1.3k stars) — MCP server for stock market data. +164 this week. When your LLM needs real-time market data so it can know how much money it just lost you. “Yeah, that’s on me…”
cronboard (1.1k stars) — Terminal dashboard for managing cron jobs locally and on servers. No more crontab -e
systemd-manager-tui (1.2k stars) — TUI for managing systemd services. Written in Rust. But you’re still team init.d right?
llm-tldr (973 stars) — 95% token savings, 155x faster queries, 16 languages. Extracts codebase structure and traces dependencies so your LLM doesn’t need to read everything.
outray (951 stars) — Open-source ngrok alternative. Tunneling never gets old.