Practical, source-linked guides and local tools for Grok Bot operators and Grok Build developers. Your inputs never leave this tab. No account. No API key.
Stripe emails your payment receipt. We'll follow up about delivery at the email you used at checkout. Questions or problems: Contact.
Need a refund or something isn't right? Use the Contact link and include the email you used at checkout.
Independent project. Not affiliated with, endorsed by, or sponsored by xAI, SpaceXAI, Cursor, or X. "Grok" and "Grok Bot" are used only to describe compatibility.
Stripe emails your payment receipt. We'll follow up about delivery at the email you used at checkout. Questions or problems: Contact.
Need a refund or something isn't right? Use the Contact link and include the email you used at checkout.
Independent project. Not affiliated with, endorsed by, or sponsored by xAI, SpaceXAI, Cursor, or X. "Grok" and "Grok Bot" are used only to describe compatibility.
Stripe emails your payment receipt. We'll follow up about delivery at the email you used at checkout. Questions or problems: Contact.
Need a refund or something isn't right? Use the Contact link and include the email you used at checkout.
Independent project. Not affiliated with, endorsed by, or sponsored by xAI, SpaceXAI, Cursor, or X. "Grok" and "Grok Bot" are used only to describe compatibility.
Your inputs never leave this tab. No account. No API key.
No analytics. Your tool inputs never leave this tab.
Draft TOML rules and review an approximate match. Permission rules and the sandbox are separate controls.
Actions: allow, ask, deny. Tool “any” matches every tool. Patterns use simple wildcards: * matches any characters and ** can match path segments. A pattern is optional and limited to 120 characters.
Review the fragment and test its rules in a throwaway repository before relying on it.
Compact rules list allow entries only; keep ask and deny decisions in the TOML fragment. Skills, plugins and marketplaces documentation.
Sources: Permissions · Settings reference: [permission].
Test the builder rules or paste the documented TOML subset or Claude-Code-style compact rules.
Rules decide what the agent may do. They are not a sandbox and don't control what the client itself sends. Keep secrets out of tracked files and git history. Read the sandbox documentation.
Approximate matching only: permissions documentation · [permission] settings reference · skills, plugins and marketplaces.
Grok Bot and Grok Build have different workflows and controls. These notes point to source material you can check.
Prepared from linked SpaceXAI/xAI and Cursor documentation checked on 29 October 2026. Product documentation changes; check the source pages before making a decision. This independent guide is educational, not legal, security, procurement, or compliance advice. Where a detail is unclear, verify with the vendor rather than assuming a feature or attestation exists.
The tools and field guide are available here. Any paid offer remains unavailable until the owner enables it with live configuration.
Use local drafts, policy checks, a rollout checklist, a routine audit, and source-linked notes.
A human review of a Bot setup and its operating boundaries.
Coming soon · Contact
Practical material for reviewing recurring Bot workflows and routines.
Coming soon · Contact
Editable operating templates for a small, owner-led workflow.
Coming soon · Contact
Editable workflow templates and planning material for Bot teams.
Coming soon · Contact