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
The Problem (3 paragraphs) MuJoCo is the fastest-growing robotics simulator Converting URDF to MJCF is painful (./compile is buggy, urdf2mjcf ignores off-diagonal inertia, mesh paths break) You just want to convert and start training your RL agent The Solution (show curl + Python code) @robot.urdf" import roboinfra Real Example (use your preview_test_arm.urdf) Show the input URDF (6 links, 5 j
The problem (3 sentences) ROS CI pipelines are slow because check_urdf needs full ROS install Most GitHub Actions runners don't have ROS You just want to catch broken joint refs before merging The solution (show the YAML) 6 lines of GitHub Action config No ROS install, no Docker, runs in 5 seconds Real example (screenshot) Show NASA Robonaut 2 URDF passing validation Show a broken URDF failing wit