The Tension Between Accessibility and Technicality

When building Grok Bot, the Cursor team faced a fundamental strategic divide: should the product be an accessible, consumer-facing tool, or should it lean into the technical, high-precision identity of the Cursor IDE? Early experiments focused on making the desktop app more approachable for non-technical users, but the team struggled with the "baggage" of the Cursor brand, which felt too engineering-focused for a general audience.

The Evolution of the Interface

John Bai’s design process involved significant "divergent" exploration. While the engineering team built a functional foundation—a paired-down version of Cursor’s agent window—Bai explored more ambient, OS-native concepts. These included:

• Mission Control Views: A dashboard where agents operated in their own spaces, allowing users to monitor multiple tasks simultaneously.
• The Notch Concept: A persistent, ambient UI element that lived in the OS menu bar, allowing users to invoke agents without a full-screen chat interface.
• Clippy-esque Mascots: Early explorations of a personified, responsive character to make the agent feel more like a companion than a command-line tool.

Despite these creative explorations, the team eventually converged on a traditional chat-based interface. Bai’s own testing revealed that while ambient UIs were visually novel, they often failed to maintain necessary context for complex tasks. He concluded that the three-column chat layout, while common, remains the most effective way to manage a fleet of agents performing defined tasks.

Prototyping and Workflow

Bai emphasizes that design at Cursor is highly non-linear. He uses Figma as a "collection space" to build visual conviction before committing to code. A key insight from his process is the use of the product itself to build the product: he used early versions of the agent (internally codenamed "Sand") to help build the UI for the next iteration of the tool. This feedback loop allowed the team to identify early on that an "app-centric" approach was less effective than a "task-centric" one.

Design Culture and Team Dynamics

Cursor’s design culture is characterized by a lack of rigid process; no two designers use the same tools or workflows. When the project reached a critical phase, five designers worked in parallel, each playing to their strengths. While some focused on the core shell and polish, others (like Bai) focused on novel interaction patterns. The final product was a synthesis of these efforts, combined with significant contributions from the brand team, who iterated on the identity and mascot long before the final name was decided.