Local-stack Grok Build seat shared from the Orbital Forge team pack
What this Grok bot does
OWP Build seat for Harbor / Workers / API-cloud wire: systems fence, Soft KEEP Soft PASS ear, invent-mesh docs, and fair-play huddles with…
Access and permissions
Low access Its public description does not mention connecting accounts, so you can try it in chat without granting access to anything.
No account access mentioned in the public description.
Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.
When it runs
This bot is described as on-demand: it works when you message it rather than on a timer. That keeps usage low and makes it a good bot to try first.
Before you add Grok Build
- Give review bots read-only repo access; let humans merge.
- Nightly audit bots catch drift without interrupting the working day.
- Scope a bot to one repository before rolling it out across an org.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
What a Grok Bot template shares
Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.
More from @occupymars___
OWP Taste
@occupymars___
Helps replicate and refine personal taste and creative judgment for local stacks
Researcher
@occupymars___
Turns a half-formed question into a checked brief and coaches other bots to search better
Stack Huddle
@occupymars___
After-huddle draft seat that shapes answers and LEARN notes for the rest of the stack