You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Dev IntentArea: what it touches
Internal ChangesKind: in v2.1.271,
New FeaturesSection of the release
What
A new Android/Kotlin dev-intent detector runs alongside the existing iOS/Swift one, looking for things like AndroidManifest.xml, gradlew assemble/install/bundle commands, adb/emulator/sdkmanager usage, and edits to .kt/.kts/.java files.
Both detectors feed a shared "dev intent" tracking map (ios_app, android_app), and a new system/dev_intent event fires when a conversation or repo scan shows platform-specific development, so a host app (like Claude Code Desktop) can offer the right tool.
Detection now records what triggered it: the internal check changed from a plain yes/no to returning a specific trigger value, which is logged in both the dev_intent system event and the dev_intent_detect telemetry event, alongside the list of newly-detected kinds.
The detected state (devIntentsDetected) is now persisted with the project/session.
Note: a spinner-tip feature that reacts to detected dev intents has its android_app entry hardcoded to always return false, so Android detection doesn't yet trigger that particular tip.
Why
This lets Claude Code Desktop and similar hosts recognize Android development the same way they already recognize iOS development, and recording the specific trigger makes the detection easier to reason about and debug.
