The previous two posts covered how events flow from the SDK to the UI. This post focuses on visualizing one specific type of event: tool calls. Tool invocations are the most frequent operations in an Agent application. A typical task might call tools twenty or thirty times—reading files, writing files, executing commands, searching code. If every tool call renders as the same gray block, it's hard
Post 1 covered how AgentBridge converts the SDK's AsyncStream<SDKMessage> into [AgentEvent]. This post looks at what [AgentEvent] becomes — how TimelineView renders 18 event types, handles scroll behavior, and stays smooth when the event count gets large. TimelineView is the main body of the workspace, filling all the space between the sidebar and the input box. Its view hierarchy is shallow: Time
Yesterday, I hit the rate limits on all my AI subscriptions. I was blocked. For two hours. I was just sitting there, staring at the message in Copilot CLI… wondering what to do next. Do I: Buy extra credits? Upgrade my plans to some “pro max” tier Or just code by myself like I used to? First option = more money. And honestly, I wasn’t ready to invest more. Second option = free, but let’s be real…
You have probably seen a file named “go.sum” in almost every Go project you have worked on. You may have even seen it change every time you run “go mod tidy”. But do you actually know what it does? It is one of those files that works silently in the background, and some developers never stop to think about it. The “go.sum” file is one of those files you never really interact with directly, but it