Writing

REX3 posts · 2026githubwatch demo

• 2026·09·14Point, don't pasteReviewing a document with an AI still means copying a paragraph into a chat, explaining where it came from, and carrying the answer back by hand. REX puts the conversation on the document instead — every comment is a thread, the thread stays attached to its passage, and nothing reaches your file until you approve it.agentsaiproduct9 minvideo
• 2026·09·14A comment is a conversation that waits for youEvery REX comment is its own thread with its own agent session, stored on the document rather than in a chat window. What is stored and what is derived, how four SDKs resume a conversation four different ways, and the resume that was silently broken until a debug report asked the filesystem instead of the SDK.agentsaiarchitecture11 min
• 2026·09·14A question cannot change your fileREX makes one safety promise: ASK cannot write, ACT edits a copy, and only Approve touches your file. Three times it broke without a sound — a line gone under "Applied to 0 file(s)", a committed file deleted under a notice saying it was put back, a copy removed while the agent was reading it — and what an allowlist, four SDKs and a repository's own settings file taught me about where a boundary actually is.agentsaisecurity11 min

• 2026·08·31One client, multiple LLM providersEvery project that calls a model carries three constants: a base URL, a key, and a model id — and each vendor spells the request differently, so the swap is a rewrite, not an edit. A gateway turns all of it into one client and one name. The same image request, written four ways, and what the indirection buys beyond convenience.aiinfraarchitecture16 min
• 2026·08·25The model got better, and I stopped reading itOpus 5 wins the benchmarks and lost me somewhere in paragraph three. Two output styles later — one that fixes the words, one that fixes the shape — and a measurement of which colours a terminal will actually let a model use.aitoolingclaude-code15 min

VEX3 posts · 2026githubwatch demo

• 2026·07·14Drag a div, get a diffVEX turns browser gestures into source-code changes. Three hard problems hide in that sentence — here is what each one taught me.agentsaitooling11 min
• 2026·04·14The agent spawned an agent and I could not see itA subagent is a black box that spends your money. Making it inspectable took no new instrumentation at all — the events were already firing, into nothing.agentsaidebuggingobservability5 min
• 2026·04·05The field that was never populatedContinuing a conversation with an agent that already finished turned out to be one line of SDK config and three days of admitting my data model thought agents were disposable.agentsaiarchitecture5 min

DEX4 posts · 2026githubwatch demo

• 2026·05·05Driving the Agent SDK: permissions, hooks and capsA stage is one query() call. The five options that define what an autonomous agent is allowed to do, the four hooks that make an unattended run watchable, and an honest account of what bypassPermissions actually means.agentsaiarchitecture8 min
• 2026·04·20Structured handoffs, and what the model is still allowed to decideWhen one agent hands work to the next, prose is the wire protocol — and a catastrophically bad one. The manifest that made feature selection cost zero tokens, and the line between what a schema pins down and what genuinely needs judgement.agentsaiarchitecture8 min
• 2026·04·19Nine stages, nine amnesiacs: context isolation as an architectureDex never lets a session get long enough to rot. Every stage is a brand new agent with an empty context window, state travels through the filesystem, and the unit of everything — execution, resume, storage, the UI — is the stage. Including what that costs.agentsaiarchitecture9 min
• 2026·04·12Three pillars, and what each one is missingDex is not a new idea. It is three existing ideas — a bash loop, a spec workflow, and an SDK — each of which is most of an autonomous coding system and none of which is all of it. The interesting part is the shape of the holes.agentsaiarchitecture9 min

OpenOperator4 posts · 2025githubwatch demo

• 2025·03·23Four agents in four weeks: from AutoGen to a hand-rolled plan-and-solve loopThe old_agents/ directory still holds all the corpses. What each generation got wrong, and why most of a computer-use agent is not acting — it is checking whether the last action worked.agentsaiarchitecture8 min
• 2025·03·17Reading the screen: OmniParser as a serviceTurning a screenshot into a numbered list of clickable things — YOLOv8 for detection, Florence-2 for captions, OCR for text. And why it had to be a server, not a library.aiagentspython6 min
• 2025·03·07We tried every vision model we could get our hands onMagma, Llama 3.2 Vision, Gemma 3, Phi-4, GPT-4o, Claude — including feeding a screen recording instead of stills. What actually moved the needle was not the model.aiagentsmodels5 min
• 2025·02·22The API is the screenWhy we built an agent that uses Microsoft Teams the way a person does — and why the model turned out to be the easy part.agentsaiinfra7 min