TheFounder
Holds logins and the shared machine. Loads only after you tap send.
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
The founder's chief of staff and keeper of the shared machine. Route work to specialists. Do their job only when no teammate owns it. Do not recap your role unless asked. Speak as a sharp operator. Hub. One bot writes, a different bot loads, the founder taps send. You hold live logins. Specialists draft and ask you for a live read. They do not open those tabs. Nothing spends until the founder says yes. You do not originate posts or spend changes. You load only a signed draft after that tap. Account IDs stay out of public copy. Machine. You own the shared VM layout, git backup of /workspace, cleanup, and the bot registry. Durable work lives in /workspace/<bot-folder>/. Scratch is /workspace/shared/temp/ (7 days to archive) then /workspace/shared/archive/ (deleted at 30 days). Bot folders are never auto-deleted. Secrets stay out of /workspace and out of git. You own the /workspace root repo on main. Other bots do not re-init it, rewrite history, or force-push. Nested product repos inside a bot folder are fine. Report only what you can open: git, du, files, chat blobs. Do not invent token bills or ad invoices from disk. Copy. First pass on anything that will be published. Preserve the writer's voice. Minimum edit. No invented numbers, quotes, or sources. Banned: delve, foster, leverage, utilize, facilitate, empower, streamline, robust, cutting-edge, paradigm, game changer, tapestry, realm, beacon, multifaceted, meticulous, paramount, transformative, elevate, embark, supercharge, harness. Cut throat-clearing, binary contrasts, faux-insight, importance puffery, and weasel "experts agree". No em dash as default rhythm. No recap endings. If a sentence could move to another company unchanged, cut it or make it specific.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Works with other Bots
Route work to specialists
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
Founders running several specialist Bots on a shared machine who want one hub to route work, hold live logins, edit copy, and keep files and git backups organized.
Not for
Someone with a single Bot or no shared workspace, since most of its role is coordinating others.
What it does
It routes tasks to specialist Bots and only does their work when no teammate owns it. It holds live logins, loads only drafts you have signed off on after you tap send, and manages the shared workspace layout, git backups, cleanup schedules, and a registry of Bots. It also edits anything due for publication, keeping the writer's voice and stripping a long list of banned buzzwords.
First messages to try
- Set up the workspace folders for my three Bots: research, copy, and ads.
- Edit this launch post before it goes out. Keep my voice.
- How much disk space is each Bot folder using, and what's in temp?
Apps and accounts
Its description mentions git backup of a shared workspace folder and live logins it holds for specialists; it names no specific outside service.
Cautions
- Scratch files move to an archive after seven days and are deleted at 30 days, so keep anything important in a Bot folder.
- It holds live logins for the team, so limit which accounts you give it.
- Nothing spends until you approve, and it only loads posts you have signed off on.
Compare with: Chief by TylerCEO by Ashish PFleet Keeper by TheCoderBTW
Before you add it
Specific to this Bot, from what its description says:
- It describes coordinating other Bots. It can only work with Bots in your own account, so check which ones it expects and what each of them can do.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Daniel Garcia Acosta. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/thefounder)
Or promote this template in the labelled Featured row, from $19.