Grok, Claude, and Hermes agents get job titles — and persistent permissions

7 relevance

Persistent permissions for AI agents is a novel paradigm directly relevant to agent orchestration and platform engineering.

AI/ML thenewstack.io

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For platform engineers building multi-agent systems, this shift from session-oriented to identity-oriented design directly impacts how you model permissions, state isolation, and handoffs between agents—treating agent profiles as routing tables rather than chat threads.

Key Takeaways

Design your agent orchestration around persistent, named profiles with scoped credentials and job descriptions, not transient sessions, and explicitly document where state separation ends and security boundaries begin.

Grok, Claude, and Hermes agents get job titles — and persistent permissions

Summary

xAI's Grok Bot, Anthropic's Claude Tag, and Nous Research's Hermes are converging on a model where persistent agent identities—with memory, permissions, and job titles—replace ephemeral chat sessions as the unit of reuse. Hermes open-sources this via Agent profiles (config, keys, SOUL file, cron state), Grok Bot uses a shared account-scoped computer, and Claude Tag provisions a service identity in Slack. The critical insight: persistence is currently a configuration and state-separation concern, not a security boundary, and none of the vendors have demonstrated long-term agent coherence.

Author

Janakiram MSV