{"version":"2.1.242","anchor":"a-per-app-computer-use-tool-family-that-drives-one-window-wi","canonical_anchor":"a-per-app-computer-use-tool-family-that-drives-one-window-wi","heading":"A per-app computer-use tool family that drives one window without taking the screen","tier":"soon","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/a-per-app-computer-use-tool-family-that-drives-one-window-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### A per-app computer-use tool family that drives one window without taking the screen\n\nA set of tools can drive a single app window instead of your whole screen.\n\n**What**\n\nA new tier of computer-use tools operates a single application through Accessibility instead of taking over the whole display: app_screenshot, app_click, app_type, app_key, app_scroll, app_drag, app_menu, app_list_windows, app_ax_find, app_batch, app_release, app_bring_to_current_space and list_apps. They only work when the host program running Claude Code provides an app-scoped implementation; otherwise every call returns \"Per-app background tools are not available in this build.\"\n\n**Details**\n\n- Each call re-checks an enabled flag, so remote configuration can switch the family off part-way through a session. When that happens the message is \"Per-app background control (the app_* tools) was just turned off for this device by a remote configuration change.\"\n- app_screenshot returns a JPEG plus an <ax-summary> listing interactive elements; the indices in that summary can be passed back as element_index to click or type into a specific control.\n- None of these tool names existed in v2.1.241, and the implementation module moved position in the bundle.\n\n**Evidence**\n\n`Per-app background tools are not available in this build.`\n\n- Area: Computer Use\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}