
Nexa AI Chat
The Mod/Plugin Introduces Nexa Ai Agent into the Minecraft. Your sidekick in minecraft! Accessible from the chat. You can talk to it anytime, even ask it to do actions. it has all context of you and environment so when it talks, you better listen.
Tags
Creators
Details
2.5.0+1.20.1-forge
Compatibility
Changes
Nexa AI 2.5
š¬ Big change: Nexa is now Bring Your Own Key
The free built-in AI is gone. Running it for everyone got too costly to keep going, so instead of letting it slowly break, I've put Nexa fully in your hands. And it's honestly better this way:
- Still free to start: Google Gemini gives free keys, and Nexa walks you through it in chat (about 2 minutes).
- Or run it locally: Ollama / LM Studio are detected automatically. No key, no cost.
- Faster and more private: no shared limits, and your chat goes straight to the AI you picked.
Just type /nexa hi after updating. Thanks for sticking around, this is a fresh start! ā¤ļø
⨠New
- One-click setup for 54 AI services (Gemini, OpenAI, Claude, Groq, OpenRouter and more)
- Nexa now looks up real recipes, items and installed mods, modded ones included
- Modpacks and servers can add guide pages, custom tools and always-on instructions
- All settings in one file:
config/nexa/nexa.toml - Now on Minecraft 26.3, 1.21.1 (Fabric/NeoForge) and 1.20.1 (Forge)
- Redesigned
Nscreen with a new AI Setup tab, plus an option to turn the screen off
š§ Improvements & fixes
- Friendly error messages with a [Fix] button
- Faster replies, and lighter on servers
- Old key settings move over automatically
- Fixed idle messages, lost saved locations, duplicate AI names, screenshots on Forge/NeoForge, and more
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:eFhkNO4w:JeCO80yE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eFhkNO4w:JeCO80yE"
}
