Skip to content

The agent of a project cannot tell what of the cost is its own, nor whether a change helped #9

Open

Description

@5hif7y

Summary

The editor's AI agent works on the game of a project, not on the engine. Its instructions send it to profile.capture when the game is slow, which answers with numbers and notes. Four things keep it from auditing a project on its own:

  1. No owner. profile.summary lists zones by name. A loop function of the game, one of an engine plugin and one of the engine look alike. The agent spends turns on zones it may not change, such as influence_update of behavior or history of the editor.
  2. No criterion. A project has no performance target, so "is it fast enough?" has no answer the agent can check.
  3. No ranking that crosses tracks. CPU zones, GPU passes, spikes, memory that grows and slow loads come from five methods. The agent has to merge them to decide where to start.
  4. No memory between sessions. Captures live in the editor and are gone when it closes. A turn that changes code after a restart cannot show what the change did.

The parts already exist:

Acceptance criteria

  • project.mirai has performance budgets, versioned with the game, editable in Project Settings and with project.set. 0 means no budget.
  • One method measures and answers a verdict against those budgets, plus findings ranked by severity across tracks.
  • Each finding says who owns it (the game, a project plugin, what the scene draws, an engine plugin, the engine), whether the project can act on it, and the call that explains it further.
  • A capture can be saved as a named baseline in the project, then compared against after the editor restarts.
  • The agent's instructions describe the loop: audit, act on what the project owns, audit against the baseline.

Out of scope

  • Attributing GPU passes to a material or entity. A pass is owned by "what the scene draws".
  • Running an audit automatically after each build. The agent audits when asked or when the game is slow.
  • A CLI command for a game's CI.

Activity

  1. self-assigned this
    on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions