Leak: Grok Bot gains templates and Chrome profile import

xAI is preparing four unreleased controls for Grok Bot: a Templates tab in Settings, multi-account switching, Chrome profile import and Desktop Egress Routing. The features were found inside the app by Testingcatalog, which reports that several of the settings are currently hidden.

At a glance

• The Templates tab lists shared templates whose function the report does not pin down, sitting alongside the Skills, Routines and Record & Replay demonstrations Grok Bot already uses to learn tasks.
• Chrome Profile Import would carry over browser profiles together with cookies, which would let a Bot open websites through sessions its owner has already authenticated rather than signing in again.
• Desktop Egress Routing would send the Bot's traffic through the desktop running Grok Bot, matching a beta option in xAI's documentation aimed at sites that block datacenter IP addresses.

Taken together the four settings read less like product features and more like the plumbing of an agent platform: identity, reusable configuration, credentials and network egress. Authenticated browsing and traffic routed through a user's own machine are the two things that decide whether an agent can finish a task on a real website, and both appear to be moving from xAI's documentation into the product itself. Templates point in the same direction, toward configurations that can be shared rather than rebuilt for each Bot.

The Templates tab lists shared templates with no stated purpose

The tab lets users browse shared templates, and their exact purpose is not spelled out in the report. Testingcatalog raises two readings: reusable tasks that Bots execute, which it compares to Perplexity's workflow concepts, or templates for the Bots themselves, so a new Bot starts from a predefined role or configuration rather than from scratch.

The first reading overlaps with capabilities the product already has, since Grok Bot supports Skills, Routines and workflows taught through Record & Replay demonstrations. The second would be broader than reusable task automation, supplying ready-made setups for roles such as researcher, sales assistant or operations agent. The report does not say which of the two xAI is building.

Multi-account support would put personal, work and organization accounts in one app

Multi-account support is also in development and would allow several accounts to be added to the Grok Bot app, with switching between them from inside the app. Testingcatalog describes the use case as separating personal, work and organization accounts inside one installation.

Chrome Profile Import sits among the settings that are present but not exposed to users, according to Testingcatalog. It would transfer Chrome profiles together with cookies, potentially letting Grok Bot reach websites through browser sessions the user has already authenticated, instead of signing in as the agent itself.

Desktop Egress Routing mirrors a beta setting in xAI's documentation

Desktop Egress Routing would push the Bot's network traffic through the desktop running Grok Bot by way of an egress tunnel. xAI's documentation already describes a beta setting that routes cloud-computer traffic through a user's own computer, including as a workaround for websites that block datacenter IP addresses. Testingcatalog lists the routing control among the settings not yet available in the interface.

Grok Bot launched in beta on August 11 as xAI's persistent agent product. Bots run through a cloud computer and work across apps and websites, the environment that Chrome Profile Import and Desktop Egress Routing would change if they ship. The Templates tab appears in the app's Settings.

Access after the August 21 expansion xAI widened Grok Bot access on August 21 to SuperGrok Plus, Cursor Pro+ and all Cursor Teams plans, and offered a free trial with limited usage to everyone else. SuperGrok Plus costs $100 per month. No release date has been given for templates, multi-account support, Chrome Profile Import or Desktop Egress Routing.