Designing Grok Bot for a world of persistent agents | SpaceXAI
How we designed Grok Bot for agents that persist beyond a single session — from a chat history to a Bot roster, presence, a computer of the Bot’s own, and work that starts without a prompt.
When we started designing Grok Bot, one of the central questions was how the interface should shape the relationship between user and agent. Most AI interfaces are organized around a chat session the user operates. Each session begins with setup, unfolds as the user looks on, and ends when the conversation stops. We wanted to design for an agent that persists beyond any one session and can carry responsibility on its own. That meant reconsidering some of the basic objects and signals of the interface, including what belongs in the sidebar, how an agent shows progress, and when its work…
saved by
related reading
- GitHub - Owl-Listener/designer-skills: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery.github.com
- LLM Powered Autonomous Agents | Lil'Loglilianweng.github.io
- AI Design Field Guideaidesignfieldguide.com
- Ando: Building Slack from Scratch — New Ontologiesnew-ontologies.com
- Why Chatbots Are Not the Future of Interfaceswattenberger.com
- Conversation Designconvodesign101.xyz
- Arjun Virkarjunvirk.com
- The Shape of AI | UX Patterns for Artificial Intelligence Designshapeof.ai
- Understanding Conversation Design for Better Relationshipstrailhead.salesforce.com
- Conversation Design Process Explained: Key Insightstrailhead.salesforce.com
- Building Effective AI Agents \ Anthropicanthropic.com
- Harness design for long-running application developmentanthropic.com