Skip to main content
GlooCode has built-in self-documentation. It knows its own agents, commands, configuration, permissions, and workflows — so instead of hunting through these docs for every detail, you can just ask GlooCode directly. These docs intentionally stay lean: they cover how to install and launch. Everything else, GlooCode can explain to you itself.

​
How to ask

Open a GlooCode session (TUI or Web UI) and ask the plan or build agent a question about GlooCode, in plain language. For example:
  • “How do I create a custom agent?”
  • “What permissions can I give an agent?”
  • “How do I migrate my Cursor rules into GlooCode?”
  • “Which model should I pick for code review?”
  • “Where is my config file and what can I put in it?”
GlooCode answers from its own built-in knowledge of itself — it’s restricted to its own documentation, so the answers are accurate to your installed version.

​
What you can ask

Think of anything you’d normally look up in a product manual:

​
Why this works

GlooCode ships with knowledge of its own capabilities. Reference content lives inside the product rather than on this site, which means the answers stay accurate as GlooCode updates — no stale docs to wade through.
For account, billing, or API credential issues — things that aren’t about how GlooCode works — head to Gloo AI Studio or contact Support. GlooCode’s self-documentation covers product behavior, not your account.