{ "schemaVersion": "1.0", "slug": "from-chatbot-to-teammate-what-small-ai-teams-can-do", "title": "From Chatbot to Teammate: What a Small AI Team Can Actually Do in 2026", "format": "standard", "theme": "grokbot", "topics": [ "grok-bot", "ai-agents", "team-bots", "ai-teammates" ], "published": "2026-11-13", "asOf": "2026-11-13", "articleUrl": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "markdownUrl": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do.md", "factsUrl": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do.facts.json", "takeaways": [ "Grok Bot's makers argue the shift that matters in 2026 is from a chatbot to a teammate. In an official mid-November workshop, the product lead described three layers: a chatbot answers one question, an agent runs a workflow, and a teammate owns a broader scope of work and can be shared with a team. Official docs call Grok Bot \"your AI teammate with a computer.\"", "A teammate works best with a human manager and one trusted job first. Official documentation says most bots work best with one clear job, and that you should get a task working once, save it as a skill, and only then automate it. The workshop described the same pattern: start with one workflow you trust, then add the next piece.", "Team Bots are designed so a team works from the same bot, files and skills. Official Team Bots, announced September 28, 2026, keep each person's chat private. What the bot learns for the team waits for a manager to approve it.", "Treat \"time saved\" dashboards and rapid-rollout stories as claims, not measurements. Workshop presenters said the product's hours-saved figure is a first-version estimate from generic task benchmarks, not a stopwatch. Customer numbers belong in the fact sheet, labeled as reported.", "Official docs recommend requiring approval before a bot sends, buys, deletes or publishes. Some features, like a saved payment card or a calendar-based meeting join, can run without asking unless you set rules. Keeping those approvals on is a choice a team makes." ], "facts": [ { "id": "team-bots-announced", "label": "SpaceXSI official Team Bots announcement date", "value": "2026-09-28", "unit": "date", "asOf": "2026-09-28", "source": { "name": "SpaceXSI, \"Team Bots: shared AI teammates that learn as they work\"", "url": "https://x.ai/news/team-bots", "date": "2026-09-28" }, "note": "Taken from the official news page itself (time dateTime=\"2026-09-28\" and datePublished 2026-09-28). Re-checked 2026-11-13.", "status": "verified" }, { "id": "grok-bot-beta", "label": "Official introduction post still says 'Grok Bot is in beta'", "value": "beta", "asOf": "2026-11-13", "source": { "name": "SpaceXSI, \"Introducing Grok Bot\"", "url": "https://x.ai/news/introducing-grok-bot", "date": "2026-08-11" }, "note": "The official introduction post is dated 2026-08-11 and, as of access on 2026-11-13, still includes the sentence 'Grok Bot is in beta and available today…' This is official product language on that page, not an independent assessment of current release status. Superseded 2026-11-13: SpaceXSI launched Grok Bot 1.0 (official post https://x.ai/news/grok-bot-1-0, dated 2026-11-02 on the page; @SpaceXSI X post 2026-11-11), and the product page https://x.ai/bot says 'Grok Bot is out of beta.' The Aug 11 line is historical only.", "status": "verified" }, { "id": "spacexsi-ownership", "label": "Ownership: SpaceXSI (SpaceX Super Intelligence LLC) is owned by SpaceX", "value": "SpaceX-owned; acquired as xAI in February 2026", "asOf": "2026-11-13", "source": { "name": "SpaceX Form S-1 (filed 2026-05-20); SpaceXSI Privacy Policy (updated 2026-10-27)", "url": "https://www.sec.gov/Archives/edgar/data/1181412/000162828026036936/spaceexplorationtechnologi.htm", "date": "2026-05-20" }, "note": "Confirmed from primary sources 2026-11-13. S-1: 'In February 2026, we acquired xAI...' and the AI segment 'includes our AI compute, Grok, and X'; X.AI LLC listed as a subsidiary. Privacy policy (https://x.ai/legal/privacy-policy): 'SpaceX Super Intelligence LLC (\"SpaceXSI\")... we have developed Grok.' S-1 predates the rename, so it says xAI. Do not say X is operated by SpaceXSI (privacy policy: SpaceXSI is separate from X Corp.); both are SpaceX companies. Grok Bot's maker is supported by SpaceXSI's own x.ai news and docs pages (S12, S3), not by the S-1. Wikipedia replaced as a citation.", "status": "verified" }, { "id": "team-bots-plans", "label": "Team Bots plan availability", "value": "Team and Enterprise plans", "asOf": "2026-11-13", "source": { "name": "SpaceXSI Docs, Team Bots", "url": "https://docs.x.ai/grok-bot/team-bots", "date": "2026-11-13" }, "note": "Official docs, last updated 2026-11-13 (stamp corrected in v2 from 2026-11-12), accessed 2026-11-13. Team Bots always run in the cloud. Docs also say the team needs at least one other member.", "status": "verified" }, { "id": "team-bot-chats-private", "label": "Each person's chat with a Team Bot is private", "value": "private per person", "asOf": "2026-11-13", "source": { "name": "SpaceXSI Docs, Team Bots", "url": "https://docs.x.ai/grok-bot/team-bots", "date": "2026-11-13" }, "note": "Official docs also say what a Team Bot learns for the team waits until the owner or a Manager approves it. Last updated 2026-11-13.", "status": "verified" }, { "id": "bots-one-clear-job", "label": "Official guidance: most bots work best with one clear job", "value": "one clear job", "asOf": "2026-11-13", "source": { "name": "SpaceXSI Docs, How Grok Bot works", "url": "https://docs.x.ai/grok-bot/how-grok-bot-works", "date": "2026-11-13" }, "note": "The same page says to get a task working once, save it as a skill, and only then create a routine. Auto Review is on by default. Last updated 2026-11-13 (v1 incorrectly said this page displayed no last-updated date, and the draft misdated it as November 12).", "status": "verified" }, { "id": "auto-review-most-actions-proceed", "label": "Auto Review is on by default, and most actions go ahead on their own", "value": "most actions go ahead on their own", "asOf": "2026-11-13", "source": { "name": "SpaceXSI Docs, How Grok Bot works", "url": "https://docs.x.ai/grok-bot/how-grok-bot-works", "date": "2026-11-13" }, "note": "The docs also say these checks 'lower the risk from harmful content, but they don't remove it.' An Ask first rule always stops a matching action.", "status": "verified" }, { "id": "saved-card-autofill", "label": "A saved payment card fills in at checkout without asking each time", "value": "fills in without asking each time", "asOf": "2026-11-13", "source": { "name": "SpaceXSI Docs, How Grok Bot works", "url": "https://docs.x.ai/grok-bot/how-grok-bot-works", "date": "2026-11-13" }, "note": "The docs say: to approve every payment, don't save the card in Vault.", "status": "verified" }, { "id": "prompt-injection-risk-lowered-not-removed", "label": "Official docs: Auto Review lowers, but does not remove, risk from harmful content", "value": "risk lowered, not removed", "asOf": "2026-11-13", "source": { "name": "SpaceXSI Docs, How Grok Bot works", "url": "https://docs.x.ai/grok-bot/how-grok-bot-works", "date": "2026-11-13" }, "note": "Used in the draft as the security / prompt-injection sentence. The docs also say a user's bots share one computer, sign-ins and Vault card.", "status": "verified" }, { "id": "meetings-plans", "label": "Meeting-join plan availability", "value": "Team, Enterprise, and Ultra plans", "asOf": "2026-11-11", "source": { "name": "SpaceXSI Docs, Add a Bot to your meetings", "url": "https://docs.x.ai/grok-bot/meetings", "date": "2026-11-11" }, "note": "Official docs, last updated 2026-11-11, accessed 2026-11-13. A bot can join Google Meet, Zoom, or Microsoft Teams, take notes, answer in meeting chat, and send a summary. Interactivity can be turned off.", "status": "verified" }, { "id": "calendar-auto-join-meetings", "label": "A bot that follows your calendar can join scheduled meetings on its own", "value": "can join scheduled meetings on its own", "asOf": "2026-11-11", "source": { "name": "SpaceXSI Docs, Add a Bot to your meetings", "url": "https://docs.x.ai/grok-bot/meetings", "date": "2026-11-11" }, "note": "This is why takeaway 5 no longer says meeting joins 'should stay behind human approval' as if the product always required it.", "status": "verified" }, { "id": "busy-trigger-usage", "label": "Official docs: a busy schedule or trigger can use a week of usage in a day", "value": "a week of usage in a day", "asOf": "2026-11-11", "source": { "name": "SpaceXSI Docs, Skills and routines", "url": "https://docs.x.ai/grok-bot/skills-routines-and-automations", "date": "2026-11-11" }, "note": "The page says an hourly schedule, a short interval, or a Slack trigger on a busy channel can use a week of usage in a day. Last updated 2026-11-11 (v1 sources said no date was displayed).", "status": "verified" }, { "id": "workshop-published", "label": "Official 'Meet Team Bots' workshop published", "value": "2026-11-12", "unit": "date", "asOf": "2026-11-12", "source": { "name": "Grok, Meet Team Bots (YouTube)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Published 2026-11-12 at 7:54 p.m. America/New_York (2026-11-13T00:54:36Z). Duration 50:09. Speakers, per the official description: Akshat Agrawal, Product, and Beatrice Del Negro, AI Deployment Manager, at SpaceXSI.", "status": "verified" }, { "id": "tutorial-published", "label": "Jay E / RoboNuggets Grok Bot tutorial published", "value": "2026-11-04", "unit": "date", "asOf": "2026-11-04", "source": { "name": "Jay E / RoboNuggets, The ONLY Grok Bot Tutorial You'll Ever Need", "url": "https://youtu.be/nIgKOAe3dxs", "date": "2026-11-04" }, "note": "Duration 28:16. Auto-captions only. The 'verified' label covers publish metadata only. The tutorial was cut from the v2 body; it remains in sources.md as consulted, not used in the article body.", "status": "verified" }, { "id": "chatbot-agent-teammate-framework", "label": "Workshop framework: chatbot (one question), agent (a workflow), teammate (a scope of work, shareable with a team)", "value": "speaker framework", "asOf": "2026-11-12", "source": { "name": "Grok, Meet Team Bots (official description and auto-captions)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Restated in the official video description and spoken by Akshat Agrawal on tape (auto-captions). Product-vision framework, not a guarantee. Official docs use 'AI teammate' language but do not spell out this three-layer taxonomy.", "status": "reported" }, { "id": "time-saved-metric-method", "label": "Grok Bot 'time saved' / 'hours saved' analytics method, as described by the product lead", "value": null, "unit": "hours", "asOf": "2026-11-12", "source": { "name": "Akshat Agrawal, Meet Team Bots workshop (auto-captions)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Agrawal said the metric is 'based on like an AI estimate,' using generic benchmarks for 'economically valuable tasks,' and called it 'our V1 estimate.' No measured number is published here. Value is null on purpose. Treat as an estimate, never as fact.", "status": "estimate" }, { "id": "harper-workshop-bot-count", "label": "Workshop speaker claim: people at Harper who built Team Bots, and bot count", "value": "about 15 people built about 85 bots", "asOf": "2026-11-12", "source": { "name": "Beatrice Del Negro, Meet Team Bots workshop (auto-captions and official description)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Spoken as: Harper had been rolling out Team Bots for 'at least kind of a month and a half or so' (rollout duration, not the time it took to build the bots). Separately, 'in most cases, and actually I want to say almost all cases, it wasn't an engineering team. It was actually 15 people across sales, operations, servicing, and billing who built about 85 different bots,' and the number 'keeps growing.' The official video description repeats the 15-person, about-85-bot line. Harper's own November 5, 2026 engineering post does not state these counts. Held in the fact sheet only in v2; the body has one short sentence pointing here. Not a target.", "status": "reported" }, { "id": "harper-certificate-time", "label": "Workshop speaker claim: Harper certificate work time", "value": "30 minutes to 3 minutes", "unit": "minutes", "asOf": "2026-11-12", "source": { "name": "Beatrice Del Negro, Meet Team Bots workshop (auto-captions)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Speaker claim from auto-captions only. Not stated in Harper's November 5, 2026 engineering post. Fact sheet only in v2; not in the body or X post.", "status": "reported" }, { "id": "harper-workshop-millions", "label": "Workshop speaker claim: lapse-prevention and autopay work 'saving Harper millions of dollars a year'", "value": null, "unit": "USD per year", "asOf": "2026-11-12", "source": { "name": "Beatrice Del Negro, Meet Team Bots workshop (auto-captions)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Speaker claim from auto-captions only. No specific dollar figure, method, or time period was given on tape. Harper's own post does not state a 'millions a year' figure. Value is null. Fact sheet only in v2; not in the body or X post.", "status": "reported" }, { "id": "harper-businesses-current", "label": "Harper claim: small businesses brought current with their premium-finance lender since September 2026", "value": 200, "unit": "small businesses, lower bound", "asOf": "2026-11-05", "source": { "name": "Aryan Jadhav, How AI agents run insurance's back office, Harper Engineering", "url": "https://www.harperinsure.com/engineering/ambient-agents/", "date": "2026-11-05" }, "note": "Harper says, unaudited. The post says 'more than 200 small businesses' and that 'the lender has cancelled none of them.' Company claim, not independently audited in this pass. The 200 is a lower bound. Framed in the draft as premium kept in force, not as money saved.", "status": "reported" }, { "id": "harper-annual-premium-covered", "label": "Harper claim: annual premium kept in force on those rescued policies", "value": 500000, "unit": "USD, lower bound", "asOf": "2026-11-05", "source": { "name": "Aryan Jadhav, How AI agents run insurance's back office, Harper Engineering", "url": "https://www.harperinsure.com/engineering/ambient-agents/", "date": "2026-11-05" }, "note": "Harper says, unaudited. The post says 'over half a million dollars in annual premium' / '$500K+ in annual premium.' This is premium kept in force, not a 'money saved' figure. Company claim, not independently audited. Value is a lower bound.", "status": "reported" }, { "id": "harper-lender-cancellations", "label": "Harper claim: policies in that rescue set cancelled by the lender", "value": 0, "unit": "cancellations", "asOf": "2026-11-05", "source": { "name": "Aryan Jadhav, How AI agents run insurance's back office, Harper Engineering", "url": "https://www.harperinsure.com/engineering/ambient-agents/", "date": "2026-11-05" }, "note": "Harper says, unaudited. The post says 'the lender has cancelled none of them' / '0 cancelled by the lender.' Scope is the rescue set described in that post, not Harper's whole book.", "status": "reported" }, { "id": "harper-engineering-harness", "label": "Harper claim: it built its own engineering layer around Grok Bot", "value": "agentic insurance harness around Grok Bot", "asOf": "2026-11-05", "source": { "name": "Aryan Jadhav, How AI agents run insurance's back office, Harper Engineering", "url": "https://www.harperinsure.com/engineering/ambient-agents/", "date": "2026-11-05" }, "note": "Harper's post credits the rescue result to its own 'agentic insurance harness' (portal-exploring agents, adapters, an abstraction layer, and mirroring). It describes Grok Bot as 'the harness our ambient agents run in.' A person signs off before any money moves.", "status": "reported" }, { "id": "harper-ceo-customer-savings", "label": "Harper CEO claim, quoted on SpaceXSI's Team Bots announcement: customer savings from a lapsed-policy Team Bot (cut from the v2 body)", "value": 120000, "unit": "USD, lower bound", "asOf": "2026-09-28", "source": { "name": "Dakotah Rice, CEO, Harper, quoted in SpaceXSI Team Bots news post", "url": "https://x.ai/news/team-bots", "date": "2026-09-28" }, "note": "Cut from the v2 body and X post after editorial review, because it overlaps the rescue figures without being reconciled ($120,000 'saving our customers' vs $500,000+ annual premium kept in force). Kept here as a reported Harper claim published by SpaceXSI. Value is a lower bound.", "status": "reported" }, { "id": "harper-smb-served", "label": "Harper claim: small and medium-sized businesses Grok Bot helps it serve (cut from the v2 body)", "value": 6000, "unit": "businesses, lower bound", "asOf": "2026-11-05", "source": { "name": "Aryan Jadhav, How AI agents run insurance's back office, Harper Engineering", "url": "https://www.harperinsure.com/engineering/ambient-agents/", "date": "2026-11-05" }, "note": "Cut from the v2 body and X post after editorial review: it is Harper's customer count, not a Grok Bot outcome. Kept here as a reported company claim. Value is a lower bound.", "status": "reported" }, { "id": "manager-and-one-workflow", "label": "Workshop best practice: a committed manager, and one workflow you trust first", "value": "start with one trusted workflow; add scope after a week or two", "asOf": "2026-11-12", "source": { "name": "Akshat Agrawal, Meet Team Bots workshop (auto-captions)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Speaker best practice, not a product setting.", "status": "reported" }, { "id": "visibility-gap", "label": "Workshop admission: managers cannot yet see all of a Team Bot's work natively", "value": "native visibility still being built; workaround is a project board", "asOf": "2026-11-12", "source": { "name": "Akshat Agrawal, Meet Team Bots workshop (auto-captions)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "The workaround they suggested was to give the bot Linear, Jira, or a similar board.", "status": "reported" }, { "id": "spoken-talkback-not-current", "label": "Workshop claim: spoken talk-back in meetings is a goal, not current behavior", "value": "not current; chat interactivity exists", "asOf": "2026-11-12", "source": { "name": "Akshat Agrawal, Meet Team Bots workshop (auto-captions)", "url": "https://www.youtube.com/watch?v=FNQkRPR4h2Y", "date": "2026-11-12" }, "note": "Official meetings docs confirm chat answers and a notes-only mode; they do not describe spoken talk-back as a current feature. Mentioned in v1 body; shortened out of the v2 body for length, retained here.", "status": "reported" }, { "id": "bennett-trust-quote", "label": "Official launch-post employee quote about trusting a bot to run without verifying", "value": "fully trust it to run forever without verifying and reviewing", "asOf": "2026-08-11", "source": { "name": "Bennett, Sales, quoted in SpaceXSI, \"Introducing Grok Bot\"", "url": "https://x.ai/news/introducing-grok-bot", "date": "2026-08-11" }, "note": "The post quotes Bennett, Sales: 'I showed Grok Bot a workflow once and now I just fully trust it to run forever. I feel like I'm 2-3x more efficient because it does it without me verifying and reviewing.' Employee testimonial on an official company page, not an independent result. Used in the draft to show the marketing-versus-docs gap.", "status": "reported" }, { "id": "bsm-small-ai-team", "label": "BSM uses a small AI agent team for research, drafting and fact-checking run by BSM", "value": "small AI agent team, run by BSM", "asOf": "2026-11-13", "source": { "name": "BSM About page (site draft) and the v2 adoption section", "url": "https://brandonstmartin.com/about", "date": "2026-11-13" }, "note": "Wording also appears on the live About page. The v2 body states this in the first-person plural ('We at BSM use a small AI team…'): house style uses 'we'/'our AI team.' Public copy does not name individual bots or quote internal rules.", "status": "bsm" }, { "id": "bsm-one-job-and-anti-jobs", "label": "BSM practice: one clear job per bot, plus a written list of what it must not do", "value": "one job and written limits per bot", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Adopted from official docs ('Most Bots work best with one clear job') and from the tutorial/workshop management idea that a fuzzy role is how a bot drifts.", "status": "bsm" }, { "id": "bsm-named-manager", "label": "BSM practice: every bot has a named person responsible for it who reviews what it learns", "value": "named manager per bot", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Adopted from the official workshop's committed-manager best practice and from official Team Bots manager review of learnings.", "status": "bsm" }, { "id": "bsm-one-trusted-workflow-first", "label": "BSM practice: a new job starts as one workflow already trusted", "value": "one trusted workflow first", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Adopted from the workshop pattern (start with one workflow you trust, then add scope) and from house practice that a new job starts as one trusted workflow.", "status": "bsm" }, { "id": "bsm-skills-before-routines", "label": "BSM practice: save a working method as a skill before scheduling it", "value": "skill before routine", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Adopted from official docs (get a task working once, save it as a skill, only then automate) and from the usage warning that a busy trigger can burn a week of usage in a day.", "status": "bsm" }, { "id": "bsm-templates-as-drafts", "label": "BSM practice: marketplace templates and public skills are treated as drafts, not finished installs", "value": "templates treated as drafts", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Adopted from workshop advice to personalize templates and from house practice that public skills are rewritten before use.", "status": "bsm" }, { "id": "bsm-autonomy-off-by-default", "label": "BSM practice: the most autonomous features stay off by default", "value": "autonomy features off by default", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Described generically in the draft: no bot holds its own logins, payments or budget, and none joins meetings or posts on our behalf unless we turn that on. A human says yes before anything is published, sent or paid for. Internal routing, chat-tool names and credentials are not specified in public copy.", "status": "bsm" }, { "id": "bsm-time-saved-not-published-as-fact", "label": "BSM practice: vendor time-saved figures are never published as fact", "value": "time-saved figures treated as estimates, never as fact", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 draft, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Adopted after the official workshop described the hours-saved metric as a V1 AI estimate. Stated in the limits section rather than the adoption section, to avoid repetition.", "status": "bsm" }, { "id": "bsm-align-before-big-jobs", "label": "BSM practice: before a big or fuzzy job, settle the open questions first", "value": "align first on big or fuzzy jobs", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Described generically. Adopted from the tutorial idea of numbered questions with a recommended answer before an expensive run. Internal skill names are not used in public copy.", "status": "bsm" }, { "id": "bsm-person-decides-new-bots", "label": "BSM practice: a person, not a bot, decides when a new bot is needed", "value": "bots do not stand up other bots", "asOf": "2026-11-13", "source": { "name": "BSM Grok Bot desk, v2 adoption section, from adopted house practice", "url": "https://brandonstmartin.com/blog/from-chatbot-to-teammate-what-small-ai-teams-can-do", "date": "2026-11-13" }, "note": "Adopted as the opposite of the tutorial's 'let bots hire' idea, which was not taken up.", "status": "bsm" }, { "id": "grokbot-ga", "label": "Grok Bot is out of beta (Grok Bot 1.0)", "value": "Out of beta; Grok Bot 1.0", "asOf": "2026-11-13", "source": { "name": "SpaceXSI, Grok Bot product page and 'Introducing Grok Bot 1.0'", "url": "https://x.ai/bot", "date": "2026-11-13" }, "note": "Product page banner: 'Grok Bot is out of beta.' Launch post dated 2026-11-02 on the page: 'Grok Bot 1.0 is available starting today.' Official X announcement 2026-11-11, 1:30 PM ET.", "status": "verified" } ], "disclaimer": "This material is for education and entertainment only. It is not financial advice. Opinions are our own and should be verified independently. Mentioning others' views is not an endorsement. The author holds long-term positions in Tesla, SpaceX and Bitcoin.", "contributors": [ "BSM Grok Bot desk" ] }