Introduction I've been seeing more developers say that Codex has become easier to use, more cost-effective, or simply a better fit for some workflows than it used to be. This is not a "Claude Code is bad, everyone should switch" article. I still use Claude Code at work, and if cost were less of a factor in my personal setup, I would probably be using both more actively. If you're already comfort
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
Hello everyone! I wanted to write this article to share my experience with agentic coding without Claude and Codex, I started dabbling with agentic coding a few months ago when Claude had decent limits on the 20$ plan, You prompt the agent: I want e2e tests, and it will study the codebase and implement them. When I've started hitting limits on Claude code, and this is not a secret that they reduc