Treating web chat as a special page instead of a real channel split my agent state in two and caused silent delivery failures.
I thought my web chat was the simplest surface in the whole product.
Telegram, Feishu, and DingTalk were the complicated ones. Web chat was just the dashboard. Same browser, same server, same app. What could possibly go wrong?
A lot, apparently.
The bug looked random from the UI
A task would start from the web chat UI just fine.
A practical model for AI coding agents that need to remember projects, tasks, executions, and runtime sessions separately.
Three threads on the front page of Hacker News in the same stretch of about ten days turned out to be different views of the same…
When AI agents mix imperative control flow with stochastic LLM calls, you get unmaintainable spaghetti. Here's how to refactor…
Have you ever spent 15 minutes re-explaining your database schema, architecture, or codebase...
Introduction Building reliable, low-latency communication for AI agents feels like a...
I built my first agent last night using the Anthropic Python SDK directly. No LangChain, no CrewAI,...
