For years I thought my only options were dual booting or using a clunky virtual machine. Dual boot meant constant reboots, and VirtualBox ate my RAM. Then I discovered Windows Subsystem for Linux 2, and honestly it changed how I work. Now I run a complete Ubuntu desktop right next to my Windows applications. I can code in a native Linux environment, test web servers, and even fire up Linux-only GU
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