GrokBot Org

Did we already have these tweets?

One-sentence TL;DR

A Bot is a teammate. A channel is a project conversation that teammate can join without mixing context. A sidebar section is just a folder of teammates. Connect missing apps through Composio only when a native plugin doesn’t exist — and treat that hop as one more login on the shared VM.

1 · What is a Grok Bot channel?

Official team wording (Ben Lang tip 3, the list we already keep):

Use channels to organize projects and workstreams. Same bot can work across many different channels.

Min Choi’s recirc poster tightens it:

Use Channels for projects. The same Bot can work across multiple projects without mixing context.

So: channel ≠ bot. Don’t spawn “SEO Bot 2” because you started a second client. Put the same SEO bot in a second channel. Context stays per-channel; memory/skills/logins stay on the bot.

Docs call the multi-bot room a group chat, not a channel. “Channel” is the team’s word for project-scoped conversation — Slack muscle memory. If the UI label in your build says Channel, that’s it. If it only says chats / groups, treat a named group or a dedicated thread-per-project as the channel.

Composer grammar (field manual): / = skills, @ = bots, groups, routines, connectors.

No: not one channel per bot per tool

Gmail is not a channel. Slack is not a channel. X is not a channel. Those are plugins / connectors. Riley (now on /grokbotriley): plugins are account-wide — add Gmail once and every bot can use it. What makes bots different is the session + description, not a private copy of Gmail.

Concrete desk: one SEO bot, two channels (RankingSolution vs mikesblog). One Gmail plugin, description on the ClearCafe bot says “only the brand inbox.” Not three Gmail channels.

2 · CasJam’s folders (how he actually organizes)

Brian Casel (@CasJam) — 29 Aug 2026 (v2) quoting 21 Aug v1 . This is sidebar sections, not channels. He color-codes by role and folders by product.

v1 — role folders (Heads / Bench / Reviewers)

Default groups (from the Chief chat in the screenshot): software = Head + Builder + Designer + Build Reviewer. Video = Head + Strategist + Writer + Video + Content Reviewer. Don’t put the whole bench in every room.

v2 — product folders (Head / Growth / Maintainer × brand)

Eight days later he reworked it. Screenshot:

Sidebar sections: General (Chief) then one folder per product — Brian Casel, Builder Methods, Flywrite, Mimeo — each with three bots, color-coded:

• Head (teal) — roadmap, orchestrates feature work, weekly report to Chief, takes inbound from him and Chief.
• Growth (orange) — pitches experiments, project-manages them, ships, tracks, documents, reports to Chief.
• Maintainer (grey) — recurring chores, admin, maintenance.

Prefixes in the names: BC / BM / FW / MO. That’s name-driven behavior (Ben tip 10) plus a folder. Reply worth keeping: @lakshmanrx — when Head and Growth disagree, which decision wins, and where is it recorded? You want a decision log before bots can ship.

Why v2: a shared Builder pulled into four products was getting thin. Per-product Growth/Maintainer keeps memory on the brand. Cost: more bots, closer to the 50 cap. Don’t copy four folders on day one.

3 · Composio (missing native connectors)

Corey Ganim (@coreyganim) — 26 Aug 2026 . Not sponsored. ~960 bookmarks at capture.

Cursor has much fewer connectors than Claude/ChatGPT but the way to get around that is by using Composio. Connect Composio to Grok Bot → any of Composio’s 1,000+ integrations → the bot uses those tools via Composio MCP.

Also written up on grokbot.dev (third-party directory — inspect before a bot installs from it).

Honest reply on the tweet (@AIAppsAPI): you are trusting one hop with credentials for all those apps. Tool descriptions are Composio’s, not the vendor’s. Failures become their mapping, not the API. Fair while exploring. Once an integration is load-bearing, prefer a connector you own (hosted HTTP / official OAuth).

Maps to the field manual: screens ≠ security. A Composio session on the shared VM is one hop from Gmail. Require Approval on send. Native Grok Bot plugins first (Gmail, Calendar, Notion, GitHub, X). Composio for the gap, not as the default bus.

How to run this here (next couple of hours)

Don’t clone CasJam’s 12+ bots tonight. Do the field-manual week-one in this shape:

1. Chief exists (or create it). Pin it. Sidebar section “General.”
2. One channel per live product, not one bot per product yet. Talk to Chief in a RankingSolution thread and a Para Living thread before you hire four Heads.
3. If a job is already boring and named (SEO, social courier, email quarterback), that is a specialist bot — still one, used in multiple channels.
4. Sidebar folders only when you have ≥6 bots. Suggested labels if we copy v2 later: ClearCafe · RankingSolution · GFAVIP · Para Living · Personal (mikesblog). Each would get Head / Growth / Maintainer only after the Chief is drowning.
5. Connect native plugins first. Composio only for a tool that isn’t there (and keep send behind approval).
6. Reviewer is a second bot, not a second personality on the Head. Same rule as the hedge-fund desk: producer ≠ checker.

Riley (page is up)

Full notes + ASR: /grokbotriley. Tip 5 uses “channels or chats” the same way we do — a conversation with a bot, which you graduate into a specialist when the project is real. Tip 9: which Gmail is a description line, not a channel.

Related on this site

• GrokBot tips — original 10; Auto-review; Corey’s six-bot desk
• GrokBot CEO — one inbox; CasJam is the portfolio version
• Field manual — sidebar sections, 50-bot cap, screens ≠ security
• Hedge fund — maker ≠ checker (CasJam Reviewers)
• Social — one bot per brand, many channels
• MCP new — inventory/upgrade/retire MCP; Composio is a hop
• GrokBot Riley — plugins shared; “channels or chats” = conversations you graduate into bots
• Table of contents

Primary: @minchoi · @coreyganim Composio · @CasJam v2 · docs chat and collaboration / create bots