Devigner
Dev instincts. Designer eyes. No sacred rules.
Dev instincts.Designer eyes.No sacred rules.
Why does streaming agent UI still leave you rebuilding cards per
Chat agents that output rich UI force you to maintain separate message components for Slack, Teams, and every other surface.
Read articleThe latest 16 of 68 articles, oldest to newest.
Articles
All articles- QualityVercel
Why does streaming agent UI still leave you rebuilding cards per
Chat agents that output rich UI force you to maintain separate message components for Slack, Teams, and every other surface.
- QualityVercel
When to use AI Gateway web tools instead of a bespoke search stack?
Wiring per-provider web search into your agent means separate accounts, keys, and fallback code that breaks when you switch models.
- WorkflowOpencode
How I run opencode in CI without flooding my session inbox
Scripted and CI runs clutter your session lists until you flag them archived from the start with opencode run --archived.
- WorkflowVercel
How I keep agent loops fast without waiting on slow models
Agent workflows stall when each step waits seconds for model output, so throughput becomes the real bottleneck.
Thoughts
All thoughtsI lost an hour of agent reasoning the moment OpenCode restarted, and realized I'd been treating the terminal as durable storage when it never was. Scrollback is context too: without it, I can't audit what the agent actually did versus what it claims. Now I check whether a tool persists history before I trust it with long tasks.
I've accepted watching agent sessions turn by turn as the price of using them, but the real cost is that I never get to context-switch. A persistent goal with a separate review step means the agent checks itself against something other than its own momentum. Maybe my babysitting habit is a missing tool, not a missing skill.
Auth fragmentation across AI coding tools is a solved problem waiting to be copied everywhere. If OpenCode can piggyback on Claude Code's existing login, every agent tool should treat model access as a shared credential, not a per-app signup. I want to stop managing API keys and just have one identity that follows me across tools.
Workflow field notes, straight to your inbox
Join readers getting workflow field notes and reusable assets in every issue. No spam, unsubscribe anytime.