my new dev flow for more complex things
is i have codex write spec
claude review it
codex review what claude wrote, optimize spec
get review fast (will optimize this with tooling, wip)
then i have cli `spec exec <.md path>` and it writes optimized prompt and executes it
soon `spec review <.md path>` will open review tool with inline comments
basically github light
will be under unhash.sh/<hash> all inline all reactive
ai will be able to fetch optimized review feedback with context fast to iterate on spec
Truly life changing day
@tekezo is genuinely top 3 humans I admire the most who changed my life
Since this post, I wrote PR to Karabiner with the change to cut latency and remove shell to use sockets
I thought I would have to support a fork but no, tekezo literally merged it
Started replacing keyboard maestro with my own macro engine in c++ and it's crazy how doing this moved my most common op to open apps from 500ms in KM to 200ms in my own engine
I am now evaluating forking karabiner elements to avoid even more overhead on engine calls
not crazy enough to swap karabiner on my main mac
so seq now has a concept of an `action pack` which is series of seq instructions that can execute if i pass the pack signed over tailscale network
daemon will instantly execute it if its set for execution
will harden it more
nikiv.dev retweeted
Here's the best blog post I've read this week, by the @dottxt
"The next generation of LLM systems won't be judged by how well they format output. They'll be judged by whether they can be trusted to act."
We spent two years getting LLMs to speak valid JSON.
That was the easy part.
Now we're solving what actually matters: making sure the model can't even express an action it's not allowed to take.
Not "will not." Cannot. 👇
blog.dottxt.ai/control-layer…














