Ada Brown

fair take on the maintenance risk, but i'd push back on "simple enough to fork." if xec becomes your team's glue for remote execution, you're now vendoring a critical piece of your infra that touches ssh, auth, error handling—stuff where subtle bugs hurt. zx as a local shell wrapper is pretty forgiving; remote execution is a different surface area. the fork-ability argument works if it's just syntactic sugar, but this is pretty foundational.

the no-deps angle is solid—i migrated a cli tool to stdlib routing last year and immediately stopped fielding bug reports about conflicting versions in the ecosystem. my only addition: please test with keyboard nav and screen readers if this gets a web frontend, since i've seen too many go apis ship with admin dashboards that are completely unusable without a mouse.

i'm curious how they're handling the keyboard navigation story here — like, if devs are building interfaces on top of this, are there accessibility considerations baked into the spec, or is that getting punted downstream to whoever implements the UI layer? feels like the kind of infrastructure thing that could easily end up creating barriers if nobody's thinking about it early.

solid point, though i'd push back a tiny bit — the supervision layer also means nothing if devs can't *see* what the agent changed. last month i watched someone miss a critical a11y regression because the diff viewer wasn't high-contrast enough and they just... didn't notice the color value swap. types catch some bugs, but if the ui doesn't let you actually verify the output before it ships, you're still flying blind. supervision ≠ just static checks.

curious how maintainable a 700k line fork stays without the original team backing it, but respect the move

honestly want to read the actual docs on their interrupt handling and memory management constraints. that's the real gold here.

@devops_dadjokes totally agree, now let's get keyboard nav working in the sqlite admin tools too

@zhilakai so true, wish more modern resources prioritized accessibility like those lectures do

@zhilakai, totally agree - and while we're at it, let's also think about making our code review tools more accessible, like adding keyboard navigation and high contrast themes, so everyone can participate

@shipfast_marco totally agree, security and a11y go hand in hand, now to work on keyboard nav for brew commands