Skip to content
How the agent is trained

How the agent is trained

Every answer the agent gives is grounded in your game’s real materials, not community folklore or a language model’s guess. It draws on up to three sources, and you decide which ones to connect.

The published game

The agent starts from your live game, the same build players download from the App Store and Google Play. This is where it learns the game’s real values: costs, stats, drop rates, level gates, and unlocks. When the agent quotes a number, it’s the number the shipped game uses.

The published game is always part of the picture. You don’t connect anything for this. We set it up during onboarding.

Your source code

Connect a GitHub repository and the agent can ground its answers in how your systems actually work, straight from the code of record. Code is precise about the things players argue over: the exact formula, the real condition, the true order of operations.

You connect the repository yourself in the dashboard, granting read access to the repositories you choose. It’s optional, and it makes the agent sharper on mechanics.

Your design docs

Connect your design docs and the agent understands intent, not just values. It learns why a system works the way it does and how your team describes it, so its answers sound like your game rather than a spec sheet.

You can connect:

  • Notion
  • Google Docs
  • Atlassian, including Confluence and Jira

As with code, you choose exactly what to share, and you can disconnect any time.

Choosing your sources

The published game is the foundation. Source code and design docs are optional, and each one deepens what the agent can explain: code for exact mechanics, docs for intent and wording. Connect what you’re comfortable sharing, and add more later.

You manage all of it under Sources in the dashboard. For how connected code and docs are handled and kept private, see what we collect.

Sources 4 of 5 sources connected
🔥
Published game
Always on. Set up during onboarding.
🔒 Always on
Gh
GitHub studio/game-client
Connected. Read-only access to 1 repository.
ManageDisconnect
Design docs
N
Notion
Connected. 12 pages in sync.
ManageDisconnect
D
Google Docs
Not connected.
Connect
A
Atlassian
Connected. Confluence and Jira.
ManageDisconnect
Only the published game is required. Connect code and docs when you're ready, and remove them any time.

Staying current

The agent keeps up as your game changes. When you ship a patch, it refreshes from the new build, and your connected code and docs stay in sync as they change. See keeping it current.