Artifacts & Compatibility
Everything is published to Maven Central under the group com.kitakkun.jetwhale, all at the same version as the host release they belong to.
Artifacts
| Artifact | Where it goes |
|---|---|
jetwhale-agent-runtime | The app being debugged. Brings jetwhale-agent-sdk and jetwhale-protocol-core with it, so you rarely need to name those. |
jetwhale-agent-sdk | Only when a module writes agent plugins without depending on the runtime. |
jetwhale-protocol-core | The shared module of a plugin pair, for JetWhaleEvent / JetWhaleRequest. |
jetwhale-annotations | @McpDescription and the opt-in markers @ExperimentalJetWhaleApi / @InternalJetWhaleApi. Reaches both SDKs transitively, so it rarely needs declaring. |
jetwhale-host-sdk | A host plugin module, as compileOnly — see Developing Plugins. |
jetwhale-host-ui | The host's theme and component library, for a host plugin module as compileOnly — see Theming and components. |
jetwhale-host-gradle-plugin | Applied as the com.kitakkun.jetwhale.host Gradle plugin id. |
jetwhale-agent-gradle-plugin | Applied as the com.kitakkun.jetwhale.agent Gradle plugin id — see Baking in the build machine's address. |
jetwhale-agent-compiler-plugin | The Kotlin compiler plugin the above points at. Never named directly. |
jetwhale-qa-agent | Run, not depended on — see QA Agent. |
jetwhale-network-inspector, -agent, -agent-ktor, -agent-okhttp, -protocol | Network Inspector. |
jetwhale-nav3-navigator, jetwhale-nav3-agent, jetwhale-nav3-protocol | Nav3 Navigator. |
jetwhale-compose-semantics-inspector, -agent, -protocol | Compose Semantics Inspector. |
jetwhale-storage-inspector, -agent, -agent-datastore, -protocol | Storage Inspector. |
jetwhale-debug-actions, -agent, -agent-compose, -protocol | Debug Actions. |
jetwhale-device-mirror | Device Mirror; host-only, no app artifact. |
In each plugin row, the first artifact (the one without an -agent or -protocol suffix) is the host plugin jar. You install it into the host rather than into your app; see Host Settings → Plugins.
Kotlin Multiplatform targets
Targets differ per artifact:
| Artifacts | Targets |
|---|---|
jetwhale-agent-runtime, jetwhale-agent-sdk, jetwhale-protocol-core, jetwhale-annotations, every plugin's -protocol, jetwhale-network-inspector-agent and -agent-ktor, jetwhale-nav3-agent | android, jvm, js, wasmJs, iosArm64, iosSimulatorArm64, macosArm64, linuxX64, linuxArm64, mingwX64 |
jetwhale-storage-inspector-agent and -agent-datastore, jetwhale-debug-actions-agent and -agent-compose | android, jvm, js, wasmJs, iosArm64, iosSimulatorArm64, macosArm64 |
jetwhale-compose-semantics-inspector-agent | android, jvm, js, wasmJs, iosArm64, iosSimulatorArm64 |
jetwhale-network-inspector-agent-okhttp, the host plugin jars, jetwhale-host-sdk, jetwhale-host-ui, the Gradle plugins and the compiler plugin, jetwhale-qa-agent | JVM only |
No artifact has an iosX64 or macosX64 target, or a watchOS or tvOS one. A desktop app on an Intel Mac uses the jvm variant like any other; what cannot resolve them is a native macOS build for x64 or an app built for the Intel iOS simulator.
Kotlin compatibility
JetWhale artifacts are built with a recent Kotlin release (currently 2.4.10), and your app needs Kotlin 2.3 or newer to use them. With an older Kotlin, the build fails with metadata-version errors: upgrade your app's Kotlin plugin, or pick an older JetWhale release built with a matching Kotlin.
If you cannot upgrade, -Xskip-metadata-version-check is an unofficial escape hatch:
kotlin {
compilerOptions {
freeCompilerArgs.add("-Xskip-metadata-version-check")
}
}It only silences the metadata check and does not guarantee compatibility. It is verified to compile and run against the current release with Kotlin 2.0–2.2, but it is unsupported by JetBrains and may break with future releases, especially around inline functions. Prefer upgrading Kotlin.
buildMachineWss relies on a Kotlin compiler plugin with a narrower range; see Baking in the build machine's address.