
Vib3Craft
Vib3Craft is a Minecraft Fabric mod that lets you chat with Claude AI and run Claude Code directly from in-game chat, with support for setting working directories, file permissions, and multi-step coding tasks on your PC all without leaving Minecraft.
1.0.0
Compatibility
Changes
Changelog
[1.0.0] — 2026-04-05
Initial release.
Added
Claude Code CLI route (default)
/claude <message>pipes directly to the localclaudeCLI via--printmode — no API key or credits required- Conversation history maintained across messages using
--continue - Session resets automatically when working directory changes
Anthropic API route
/claude api <message>calls the Anthropic API directly usingclaude-sonnet-4-20250514- Full agentic loop with
run_terminal_commandtool — Claude can propose terminal commands /claude yes//claude noto approve or deny proposed commands/claude setkey <key>to save API key toconfig/vibecraft.properties
Working directory
/claude setdir <path>sets the working directory for the Claude CLI session/claude dirshows the current working directory- Changing the directory automatically resets the active session
Permissions
/claude allow <tools>sets allowed tools via--allowedTools(e.g.Write,Edit,Bash)/claude allow allbypasses all permission prompts (--dangerously-skip-permissions)/claude denyrevokes all permissions/claude allowwith no argument shows current permission state
General
/claude clearresets conversation history, working directory, and permissions- ANSI escape codes stripped from CLI output before display in chat
- Long responses automatically word-wrapped to fit Minecraft chat width
- Stdin closed immediately after process start to suppress CLI stdin warnings
- Build output redirected to
C:\claudemod-buildto avoid OneDrive sync conflicts
Supported versions
Minecraft 1.21 through 1.21.11 (Fabric).
Dependencies
- Fabric Loader 0.18.6
- Fabric API (version varies per Minecraft release — see README)
- Claude Code CLI installed and in PATH
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:fZynQXKE:bXTSyJqX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fZynQXKE:bXTSyJqX"
}
