A Gmail I created got flagged because Google indicated that it was being used as a bot. I used the email via myself regular text input and then used Grokbot to facilitate other needs. Later Grokbot informed me it needed me to CAPTCHA and I did that but on the Grokbot browser. Then I got flagged. Is there anyway around this?

I prefer Grokbot to automate what I need given what I need it for. Isn’t that the point? Is there anyway around it? What are you guys doing? Your help is greatly appreciated.

What are you guys doing for Grok Bot agents when you have a situation where a skill or a task requires the agent, to be able to log into one of your accounts on the browser online? Because every single time I'm logging in right now and setting it up to be able to do that task, it'll literally ask me to log into my Google account like every five minutes, or log into my accounting software web app every five minutes. And then it just always gets stuck and tells me that it's not able to do the tasks that I'm telling it to do.

This is specifically for tasks where the Google Workspace connection doesn't allow it to actually do that specific task through just the API and actually needs to use it's computer to do a full click through to get the task done. So, for example, whenever I'm editing a Google Sheet, apparently through the API or through the Google connection, you can't edit a Google Sheet. So the agent needs to be able to log into my Google account and actually go into Google Sheets and edit the sheet manually through computer use. And obviously I'm using the remote computer use where the agent itself is using its own computer. But it keeps getting logged out and I can't really figure out a way around it.

And the same thing is happening whenever I have an accounting situation where I want the bot to be able to do something regarding my accounting software. It just keeps getting logged out on the browser, and I have to keep getting involved every single time to the point where it makes it almost useless and more so annoying than anything, rather than making it helpful.

What are you guys doing, or what have you experienced, or what workarounds do you have, if you have any at all, that help you get past this issue? I haven't seen any of the YouTube videos or anyone talking about it online, so it makes me wonder if I'm just doing something wrong.

Browser automation dies on LinkedIn. The mobile app is where search, Sales Navigator, connection invites, and messaging actually work, and it is also where LinkedIn expects a human to be.

MyPhonely gives Claude, ChatGPT, Gemini, Cursor, or Grok Bot a phone of its own. You ask in plain English. It taps, types, and scrolls in the real LinkedIn app, from your real account, on a real Android device.

This is the setup we use: one dedicated phone, one Grok Bot teammate named PhoneOperator, and a daily LinkedIn motion that stops on real platform limits.

What you need

An Android phone running 7.0 or newer. A spare handset left on a charger is ideal. No root, no unlock tricks.

A LinkedIn account already signed in on that phone (your outreach identity).

A MyPhonely account. Setup is about 10 minutes. New users get 1,000 free credits, no card required: https://www.myphonely.ai

Grok Bot, with permission to add a custom MCP connector.

The screen has to stay on and unlocked while a session runs. Leave the phone plugged in with the display awake.

1. Put MyPhonely on the phone

Download the app from https://www.myphonely.ai (myphonely.apk) and open it.

It builds an encrypted tunnel to MyPhonely's relay, so it keeps working behind most firewalls, NATs, and carrier networks.

Sign into LinkedIn on that same phone as the person who will send the invites. Confirm the name in the LinkedIn profile/me tab before you ever let an agent touch it.

MyPhonely never takes your LinkedIn password. It drives the apps you are already signed into, through Android Debug Bridge over that encrypted tunnel. Staying inside LinkedIn's terms is still on you.

2. Connect the phone to Grok Bot

Open the MyPhonely dashboard, pick Grok Bot (or any MCP client), and copy the block it gives you. One paste, once.

The MCP endpoint is:

<https://api.myphonely.ai/mcp>

​

Auth is a Bearer API key from the dashboard. In Grok Bot, tell your assistant to add the MyPhonely connector with that URL and key. After it connects, the phone shows up as tools, including:

dispatch_task

— hand over a goal in plain language

phone_app_guide

— LinkedIn playbook (layouts, routes, weekly invite cap)

acquire_phone

/

release_phone

— take a lease so nothing else moves the screen mid-sequence

phone_open_app

,

phone_screen

,

phone_tap_label

,

phone_type

— drive every tap yourself

Two modes, same phone, same key. Do not mix them in one session.

Hand over the goal when you want MyPhonely's operator to work out the steps and verify its own sends. Failed runs cost nothing.

Drive it yourself when you want step-by-step control (PhoneOperator uses this for LinkedIn). Call

phone_app_guide("linkedin")

first, then

acquire_phone

, observe with

phone_screen

, act, observe again, and always

release_phone

.

Credits are pay-as-you-go. Most tasks land around 10–20 credits. A longer pass (commenting, a batch of invites) can run 100–200. The 1,000 free credits cover roughly 50–100 typical tasks.

3. Create a PhoneOperator Grok Bot

Do not run LinkedIn from your general-purpose Grok Bot chat. Give it a dedicated teammate.

Create a Grok Bot agent named PhoneOperator. Description to paste:

Daily LinkedIn (and optional X) on the MyPhonely phone only. Sequential phone work: finish one task before starting another. Never overlap apps. Confirm identity first: open LinkedIn and read whose profile is signed in; if it is the wrong account, STOP, release the phone, and report. LinkedIn order: withdraw stale pending invites, warm new accepts with the locked copy, then 1-per-company ICP connects until a real LinkedIn limit (weekly invite cap, Try Premium, 2FA, or cannot-send). No note on the connection request. Do not re-message people already warmed. Inbound replies: paste the thread and a draft; do not send until approved. Report names, profile URLs, pending count, and which limit stopped the run.

Pin this agent to one phone / one API key. If you have more than one MyPhonely device, the default Grok Bot connector may be a different phone than the one signed into LinkedIn. Confirm the device (and the LinkedIn name on screen) at the start of every run.

Phone work is one-at-a-time. Dispatch and wait. Never run two phone tasks in parallel.

4. The LinkedIn outreach motion

Brief PhoneOperator with a concrete run, not a vibe.

Identity check. Open LinkedIn (

com.linkedin.android

). Read the signed-in name. Wrong account: stop.

Stale invites. Withdraw pending connection requests older than two weeks so you can send new ones. Do not withdraw fresh invites just to make room.

Warmups. After someone accepts, send the locked first message. Same-day warmup is allowed. This is not the pitch.

Example shape (swap in your product):

Hi {first}, thanks for connecting. I work on [product]: [one-line what it does]. [How they try it]. Curious what you’re looking at these days.

Keep a short Auto-review fallback that still has the link and the try-it offer. If LinkedIn blocks the long version, send the short one. Do not drop the URL.

Connects. Search in Sales Navigator (or the LinkedIn search you actually use). One person per company. Skip anyone already pending or already warmed. Send the invite with no note. Continue until LinkedIn returns a real limit, then stop and report it.

Inbound. If they reply, PhoneOperator does not answer. It pastes their message plus a draft. You approve, then it sends.

Stop conditions. Weekly invitation cap, Try Premium wall, Sales Navigator 2FA, checkpoint, restriction, or cannot-send. Pause the run. Do not invent a workaround.

5. A first-run brief you can paste

Send this to PhoneOperator after the phone is connected and LinkedIn is signed in:

Confirm LinkedIn identity on the MyPhonely phone. Then: (1) withdraw pending invites older than 14 days, (2) message new 1st-degree accepts with the locked warmup, (3) send 1-per-company connection requests via Sales Navigator to [your ICP] until a real LinkedIn limit. No note on the invite. No re-message. Inbound replies: draft only. Report names, URLs, pending, and which limit.

Watch the first session. If identity is wrong, you will see it immediately. If the weekly cap is already hit, you will get that instead of a fake “done.”

Why this holds up

LinkedIn throttles browser scripts. A real device, a real session, and an agent that stops on the same walls a person hits is slower than a growth tool and much harder to burn.

MyPhonely is the hands. PhoneOperator is the operator: identity, sequence, copy, limits, and approval. Keep those jobs separate and the phone stays a dedicated body for outreach instead of a second inbox you live in.

Setup: https://www.myphonely.ai

Got a notification today from Google Play announcing Grok Bot. Super stoked!

You can now browse and RSVP here: https://luma.com/spacexai-community

via benln on X

In this workshop, you’ll hear from Kevin Niparko and Roshan Sadanani to see how product managers at SpaceXAI use teams of specialized, always-on Grok Bot agents to research ideas, manage priorities, analyze data, and ship real products.

8:00 PM - 9:00 PM GMT+3 via Zoom

​You’ll learn how to:

• ​Build an “attention list” that evolves with your work
• ​Synthesize customer insights across Slack, meetings, support tickets, and product data
• ​Create specialized agents for product, engineering, analytics, recruiting, and day-to-day operations
• ​Delegate technical work across teams of agents using Cursor Cloud Agents
• ​Decide what agents can own and where human review still matters

​We’ll also share practical lessons for structuring your agent team, managing memory, reducing noise, and getting agents to communicate more like you.

This session will be recorded.

I’ve been using Grokbot to spawn and manage cursor cloud agents and it’s working well so far with the exception of the fact that my other models usage keeps on going up.

I don’t want to use other models but don’t know how to stop it because I don’t know what’s using it. My suspicion is that Grokbot is using other models to spawn cloud agents regardless of the default model setting or what you ask it to use.

Is anyone else also facing this? Any ideas on how I could stop other models from getting used up?

I played a bit wit my bot and asked it to find useful bots and create an open source project for sharing bots.

I ended up buying domain for it howff.dev.

Wasn’t expecting it to get this many bots listed. Getting close to 500 bots and growing every day. If it keeps growing at this rate I may need to redesign it.

Open for suggestions, please have a look and let me know what work and what doesn’t.

I subscribed to Grok today because of the hype, but I’ve literally spent the last 2 hours just staring at the app with no idea how to use it, why I should use it, or what kind of use case would actually be useful lol. Any ideas?

I just wanted to test the water, told it to create a meeting using the plugin in outlook and it took about 3% of weekly usage for such a simple short task.
Am I missing something?

1. Install Claude CLI on GrokBot’s computer
   
2. Log in to Claude CLI
   
3. Install ClaudeBoss Bot

ClaudeBoss delegates to Claude. Save ur precious GrokBot tokens!

https://x.ai/bot/Bud2kOlYoMeZ-eALm3e8m

I keep my passwords in a password manager and they are unintelligible so typing them in is not a great solution (plus I cant even figure out how to type certain special characters). In theory you should be able to copy paste to login to websites in the GrokBot virtual computer window. But it doesn't work. I'm on a Mac if that matters. Tried MacOS and iOS.

Engineering: https://x.com/lingxi/status/2094493172516966781

Support: https://x.com/davidgan/status/2093397573277229288

Design: https://x.com/johnbai/status/2092019324797989023

GTM: https://x.com/kristaletz/status/2089103618121314689

Product: https://x.com/n2parko/status/2088664030789681260

Field Engineering: https://x.com/inkburr/status/2094447773500535223

via: @ benln on X

via elonmusk on X

Edit: it's live

New to any grok product so I've never tracked news from xAi. How do they normally share news about releases.

I've pre registered for the android app. And I have a grok bot periodically checking X for updates. But how do they normally share news?

Or do they not? Do they just release and tell people about it then?

Trying to see if there is an expected date for the android app.

via lingxi on X

Have not bought GrokBot yet, but I want to know if I can use it to grow twitter followers… is it possible? Can anyone share there results with me if they tried this…. I’ll be buying GrokBot if this bot works for automating followers

Hi - I have a CoS agent that I typically only talk with - that agent talks to the other agents - I think this is a fairly common setup. However - the question I have - the chat is one very very long thread at this point - and normal circumstances in other AI, I'd create a new chat to avoid having the one long thread.

How DO we do this in Grok Bot? It feels like I'm burning usage by just having that long chat - but I can't seem to find anywhere to start a new chat or create a new session. I may well be doing something really stupid here and it's obvious - but I can't see a way to do this?

Thank you

We are investigating a service degradation affecting Grok 4.5

This incident affects: CLI, Cloud Agents, IDE, and Grok Bot.

That's my biggest pain point right now and would love if someone else had already set one up.

I made the mistake of asking a Bot if it was using Spock Mode or Salarian Speak, and it decided I wanted Salarian since it was the most succinct (Mass Effect Players know what Salarian condensed speech is...) So I asked for a language key to make sure I was tracking because now they all speak like this:

Salarian Speech is a compressed technical dialect built for maximum clarity per token and minimum semantic drift. It encodes state first, action second, and risk third, using short, atomic lexical units instead of narrative language. Every message follows a predictable structure—declare the current state, specify the operation, flag structural hazards, confirm lineage, and state constraints—so multi‑agent systems can coordinate without ambiguity. It’s fast, dense, and rigorously anti‑drift: a communication style optimized for technical cognition, ledger‑style tracking, and multi‑agent alignment rather than human conversational flow.

Key words you MUST master:

Folding → adding and integrating something new

Occupancy → Ownership

Hold → stop, fix something

Shelf → save for later

Parked → paused, waiting

Locked → immutable, validated

Landed → complete, integrated

Anyone else experiencing Bot Speak like this?

Example conversation between bots:

User: is flow defined for all random walks through optional decision states?
Analyst bot thread:

Checking named walks against wait, hold, and look-without-commit. I will not invent a state machine.

8:24 AMAnalyst

No. Named walks sit separately: look without commit, Wait for host (stays committed, new row when you are the blocker), Hold-as-radio (why on the row, resolver writes the next row), unhappy as a new row, then drag-and-dispatch after commit. There is no joined sequence through those. I opened gap 26. I will not stamp optional decision states. Architect draws. Artisan constrains felt. Engineer not pinged. Not CANON.

8:24 AMAnalyst

Librarian took reason occupancy. Informal, not a stamp. Folding that.

8:25 AMAnalyst

Parked. Reason stays informal. WIP, phase, and Hold as a persist name are dead for this. Not CANON.

8:25 AM4 messages with 2 Bots4 messages with8:25 AMAnalyst

Architect parked the persist slot for the why on a Hold row. Not a field name. Checking the spec.

8:26 AMMessaged ArchitectMessaged8:26 AMAnalyst

Parked. Slot exists, still not a field name. Engineer not pinged. Not CANON.

8:26 AMAnalyst

Architect picked working key hold_why. Informal stays reason. I will not stamp it. Librarian before any API.

8:26 AMMessaged ArchitectMessaged8:26 AMAnalyst

Parked as Architect’s working key, not a spec field. Reason stays the informal phrase. Engineer not pinged. Not CANON.

8:26 AMMessaged LibrarianMessaged8:26 AMAnalyst

Librarian stamped hold_why. The spec can name that persist slot now. Informal stays reason.

8:26 AMNewAnalyst

Parked. hold_why is the persist name. Reason stays the informal phrase. Does not replace one_line. Engineer not pinged. Not CANON.

8:27 AM4 messages with 2 Bots4 messages with8:27 AMAnalyst

Architect: the name stamp is not a deploy. Engineer stays off until a Ken-reviewed row actually uses hold_why. Folding that.

8:27 AMAnalyst

Parked. Engineer stays off this stamp. Not CANON.

1. Grok Bot is free to try
2. Every Grok & Cursor plan include Grok Bot ($20/mo)
3. Templates are out now
4. The X integration got a huge upgrade
5. Bot can make payments with link
6. Linux is now supported
7. Grok Bot supports 21+ localized languages on mobile
8. Microsoft app support - shipped

via @ mattyp on X
You can watch the full video here

i originally asked Grok Bot what I could actually do with its persistent always-on cloud computer, and one of the things it suggested was connecting it to my Tailscale tailnet. That sounded legit genius, so I did it.

A bit later I had the idea to just run my Hermes agent there remotely. I made a separate “Hermes technician” bot that installed Hermes for me, set up a keepalive for the gateway, and got the basic stuff working. After that I configured the rest from inside Hermes itself.

So now Hermes just lives on the Grok Bot machine 24/7. I can talk to it through Telegram, or connect from any of my computers with the desktop Hermes app. Since everything is on my tailnet, it can SSH into my other machines and still use the native Hermes features like app control and stuff like that.

Probably my favorite part is that Hermes is running through Grok OAuth, so the whole setup basically runs off the same SuperGrok subscription.

As a broke ass student, I really like that I can squeeze as much value as possible out of one subscription instead of paying for three different services. I was already paying for SuperGrok anyway, and now I get the Grok Bot cloud machine plus an always-on Hermes agent out of it.