Skip to content

Start Here

If this is your first visit to the GrayGooAgent docs, use this page to identify the most relevant starting point.

Choose Your Path

I am deciding whether this plugin fits my project

Start here if you have not installed anything yet and want to understand the product boundary quickly.

  • Read the home page for the supported launch baseline
  • Read the FAQ for common expectation-setting questions
  • Check the Fab listing for the commercial listing and package path

What GrayGooAgent is best at today:

  • inspecting levels, actors, Blueprints, widgets, and assets inside a real Unreal project
  • handling narrow editor tasks that you can verify in the editor
  • pairing editor-side execution with a stable provider setup

What it is not positioned as:

  • a packaged-game runtime gameplay plugin
  • a promise that every open-ended request will succeed
  • a requirement that you must use an outside agent

I already installed it and want my first successful run

This is the fastest onboarding route:

  1. Confirm you are on the current validated baseline: UE 5.7 and Windows / Win64
  2. Open Window > GrayGooAgent
  3. Configure one provider instance
  4. Point both default provider fields at that same instance
  5. Run the built-in quickstart in a fresh session

Continue with:

I need an outside agent to drive Unreal Editor

This path is not recommended for initial setup.

First make sure the normal in-editor quickstart works. After that, move to:

Use the bridge path when:

  • you already have an external agent workflow
  • you want orchestration outside the editor
  • you still need Unreal-specific execution to happen locally inside Unreal Editor

First-Run Readiness Checklist

  • GrayGooAgent is enabled in the project
  • Interchange and PythonScriptPlugin are enabled
  • one provider instance is configured
  • Default Provider Instance and Default Lightweight Provider Instance point to that same instance
  • the startup guide shows no blocking provider issue
  • Run Quickstart is available, or Insert Quickstart produces a coherent read-only result

Items You Can Defer During Initial Setup

You do not need these for the first success path:

  • custom Instruction Paths
  • lightweight provider overrides
  • Python-backed mutating workflows
  • the external agent bridge

Keep the initial setup narrow. Expand only after the quickstart is stable.