AI
AI Agents Now Get Names, Job Titles, and Persistent Identities Across Conversations
Hermes, Grok, and Claude are shifting from treating conversations as the core unit of work to building durable agent profiles that carry memory and permissions across sessions.
The New Stack
A new design pattern is emerging in AI assistants: rather than spinning up a fresh chatbot for each conversation, developers are building agents with stable identities, persistent profiles, and cross-session memory. The shift means your next AI coworker may look like a named colleague, complete with job title and responsibilities, rather than a generic interface.
The Shift from Conversations to Worker Profiles#
Three major AI platforms have converged on this model in recent months. Hermes, powered by Nous Research, integrated Bot Mode into its desktop application in August, letting users create named agent profiles with distinct personalities, avatars, and chat histories. Grok Bot from xAI launched August 11 with a sidebar roster of bots, each carrying a title, description, and up to 50 automated routines per account. Claude Tag from Anthropic took a different approach in June, provisioning a single organization-owned Claude that joins teams' Slack channels and can be tagged by any member.
The fundamental change is architectural: instead of the individual conversation serving as the reusable unit, the persistent agent profile now sits above sessions, carrying configuration, memory, and permissions across separate interactions.
How Each Platform Structures Agent Identity#
The three services implement identity in fundamentally different ways, which matters more than feature parity at first glance.
Hermes keeps credentials and state tied to a specific host—whether a local laptop or remote server. A bot profile is essentially a home directory containing configuration, API keys, memory logs, session history, and scheduled tasks. Bot-to-bot handoffs work as actual command-line invocations that execute when the receiving bot next runs.
Grok Bot consolidates all bots under a single account-scoped computer. This means every bot shares access to the same files, browser sessions, and app logins. xAI notes that these shared resources persist even if a bot that created them gets deleted.
Claude Tag creates organization-level service identities with channel-scoped tool access. A single Claude instance joins a Slack workspace and spins up fresh working sessions within threads.
