Skip to content

Core Concepts

This page explains the core terms required for initial setup and first-run verification.

The Six Terms That Matter First

Term

Provider instance

One saved model connection profile, including provider type, model, endpoint, and auth.

Where you see it: Project Settings > Plugins > GrayGooAgent

Term

Default Provider Instance

The main provider used by the primary workflow.

Where you see it: GrayGooAgent settings

Term

Default Lightweight Provider Instance

The provider slot used for lighter delegated work. For the first run, set it to the same instance as the default provider.

Where you see it: GrayGooAgent settings

Term

Startup guide

The readiness card inside the panel that tells you whether provider, dependencies, instructions, bridge, and quickstart are ready.

Where you see it: GrayGooAgent panel

Term

Session

One conversation container inside the panel. Start a fresh one for the first successful run.

Where you see it: GrayGooAgent panel

Term

Quickstart

The built-in read-only onboarding action used to verify that the plugin can see real editor context.

Where you see it: Startup guide card

First-Day Mental Model

Use this simple model:

  1. The plugin needs one working provider connection
  2. The panel needs one fresh session
  3. The startup guide tells you whether the basics are ready
  4. The quickstart proves that GrayGooAgent can inspect real editor context
  5. Only after that should you move to a small real task

Read-Only First, Mutating Later

For the first run, prefer read-only tasks such as:

  • list actors in the current level
  • inspect one Blueprint
  • explain the current editor context
  • capture a screenshot for visual verification

Move to mutating tasks only after the basic path is stable.

What To Ignore On Day One

These are real features, but not required for the first success path:

  • custom Instruction Paths
  • lightweight provider specialization
  • Python-backed editor changes
  • external-agent bridge setup