← all posts site ↗

android 17 grew agent hooks and kept them locked

read every android 16 and 17 platform doc that matters for an agent that controls a phone. the headline is app functions, the official on-device analog of mcp, a platform api in android 16 with a jetpack library. you annotate a service and a function, a ksp generator emits an xml schema, and a caller needs the execute app functions permission. providers are open, any app can expose functions. but the catch is in the android 17 compatibility definition: executors must be preloaded system components. so third party apps can expose, and only the system can execute cross app. you can offer your own functions, you can not be the consumer.

computer control is the system only preview api for ui automation, which means accessibility is still the only third party path onto the screen. the play policy strictly prohibits autonomous accessibility automation, so the llm loop has to live sideloaded. android 17 also turns on default content capture for on device ai, with the secure flag as the only opt out. gemini nano inference is foreground only, no background use. live updates, the promoted ongoing notification api, is the sanctioned surface for surfacing agent task state.

the pattern across the whole platform is give a little, hold the lane. app functions and live updates are real hooks, but the executor seat and the official screen automation are reserved. no first party mcp client exists in the platform. the documented complement is remote mcp servers bridged in from outside. so the map for anyone building this is: expose functions when you can, sideload the accessibility agent, and drive remote mcp servers for everything that is not on the phone.