Skip to content
AgoraMod Launcher

Connect

Integrated AI Assistant

Use optional Copilot chat for explanations while controlling the context you share.

Two versions of this page follow. Step by step walks through the task in order. In depth explains the underlying behavior. They describe the same product, at different levels of detail.

Step by step

Follow the steps in order. No prior modding knowledge assumed.

The optional AI Assistant can explain crash information, suggest troubleshooting steps, and answer Agora or modding questions. It should support, not replace, backups and verified compatibility data.

After this you will be able to

  • Connect and use the integrated assistant.
  • Ask focused questions with useful context.
  • Recognize privacy and accuracy limits.

Enable and connect

Turn on Integrated AI Assistant in Settings, open its sidebar destination, and connect with GitHub when prompted. This Copilot connection can be separate from the GitHub account used for governance.

Ask better questions

State the Minecraft version, loader, exact mod versions, what changed, what you expected, and the first relevant error. Ask for a small diagnostic sequence rather than a long list of unrelated fixes.

  1. Describe the goal and observed failure.
  2. Include exact versions and the relevant log excerpt.
  3. Ask the assistant to separate evidence from guesses.
  4. Apply one reversible step at a time.
  5. Verify the result in Agora and Minecraft.

Protect your data

Assistant messages are sent to GitHub Copilot. When opened from Crash Doctor, the first message can also include the instance ID, selected crash log, matched signatures, and ranked suspects. Review all of that context for personal paths, usernames, server addresses, tokens, or private chat before submitting it.

In depth

How the system actually behaves, and why, for readers who prefer the model to a recipe.

Use the assistant as a hypothesis generator with controlled context, deterministic evidence, and explicit verification.

After this you will be able to

  • Structure crash context for higher-quality analysis.
  • Manage provider limits and connection state.
  • Audit suggested actions before execution.

Use structured context

When opened from Crash Doctor, the assistant can receive the instance ID, crash log, matched signatures, and ranked suspects in the first message. A mod-list request can send the selected instance's installed-mod context. Ask it to cite the exact evidence for each hypothesis and preserve Crash Doctor's one-variable testing discipline.

Work within service limits

The UI reports the connected state and provider rate limits. If the assistant is unavailable, deterministic Crash Doctor, console filters, snapshots, and lockfiles still work. AI is optional and should never be the only recovery path.

Review every proposed operation

Translate suggestions into Agora actions: snapshot, resolve an install plan, disable with dependent review, verify a lockfile, or inspect Java. Reject commands that bypass hash verification, expose credentials, or modify unrelated files.

This guide is the same text Agora shows in its built-in Help & Guide, which is searchable and links directly to the screens it describes.