# Release Notes ## 1.0.18 - 2026-10-20 ### New - Added `init-context --agent --update`, which refreshes only the Amazon Devices context already installed for that agent, with no prompts: the steering doc block (migrating a legacy steering doc), skills and their licenses, community skills, the adbt-dev agent file, and the MCP entry (the legacy entry is removed; an existing entry, including a custom launcher or disabled state, is kept as is). It never sets up a steering doc, agent file or MCP entry you don't already have, `.adbt-config.json` is left untouched, corrupted files are skipped with a warning, and the command exits non-zero only if a refresh failed. - The MCP server now checks the Amazon Devices files that `init-context` installed for your agent (steering doc, skills, the adbt-dev agent file and the MCP entry) against the version it ships with. When something is out of date, your agent asks you once per session whether to update, and on a yes runs `init-context --agent --update`. Updates you decline aren't offered again until something new changes. `check-status` now lists every installed file that needs attention, with the command to update it. You can also ask your agent to update Amazon Devices Builder Tools at any time. - Added the Vega SDK 2.0 Experimental and Deprecated API Migration Guide and a matching skill. When a build with Vega SDK 2.0 fails because an experimental or deprecated API was removed, your agent now reads the guide, finds every affected API in your native code, maps each one to its stable replacement, and walks you through the changes in dependency order, starting with the manifest update that targets Vega 2.0. The build-and-run skill now sends these build failures to the guide. `[Vega OS]` - Fire OS to Vega migrations can now be done in stages. For native Fire OS apps, the migration analyzes your whole app once, groups its screens into features such as Browse, Details, Playback, and Settings, and then asks you in the chat which features to build. Screens you haven't built yet open a placeholder, so the app stays navigable. Before it builds, the migration lets you correct any screens it grouped by best guess, and warns you if a screen you chose can only be opened from a feature you didn't choose. To build more later, run the migration again, say you're resuming, and point it to the same output folder: it skips the analysis, keeps the screens it already built, and builds only what you add. React Native and WebView apps are still migrated in a single pass; if one of those migrations is interrupted, resuming picks up where it stopped instead of starting over. - The React Native upgrade workflow now detects a library (React Native as a peerDependency, a TurboModule project, or a system library) and skips the application-only items. The library producer guidance now covers what a consumer app changes, how to test the library against one RN 0.72 and one RN 0.83 consumer, when to bump minor or major, how to choose and verify the peerDependency range on react-native-kepler (with the `~`, `^` and `>=` prefix rules), and the native module registration changes between `react-native-kepler` 2 and 4. `[Vega OS]` - Added a migration workflow that moves an existing Fire OS app from the legacy In-App Purchasing v2.0 library, or from an older Amazon Appstore SDK 3.x, to the latest Amazon Appstore SDK 3.x. `[Fire OS]` ### Improved - The getting-started steering doc now asks your agent to pass the project folder (`project_root`) when it calls `set_project_context`, and to call it with an empty config when the project has no `.adbt-config.json`. This lets the MCP server check the Amazon Devices files installed in your project and tell you when an update is available. It also tells your agent how to update the Amazon Devices files in your project and agent setup when you ask it to, without prompts. - The always-on get-started guidance now points the assistant at the debugging tool router and its app-type detection before it names any debugging or performance tool. For a JavaScript app it runs the Vega app-type detector to tell WebView apps from React Native apps, instead of guessing from project files, which makes tool routing for debugging and performance requests more reliable. `[Vega OS]` - Debugging and performance guidance now checks whether a Vega app is native before it names a tool. A native app is sent straight to native debugging, and only JavaScript (React Native or WebView) apps go through the app-type detector. This stops a native app from being pointed at React Native profiling or re-render tools, which do not apply to an app without a JavaScript runtime, and makes debugging and performance tool routing more reliable. `[Vega OS]` - The headless tasks and services KB now has a Threading Model and Failure Behavior section. It covers the threading model (each headless task and service has its own JavaScript runtime, and headless playback runs the player in a separate JS thread from the UI), the ANR causes and default timeouts from the Vega triage guidelines, the 10-minute execution limit for tasks launched by Task Manager, and the crash-report fields to check after an ANR. The manifest examples for headless tasks and services, in the headless KB and the Vega app manifest KB, now say to use the headless runtime-module when the component does not share a process with the interactive component. `[Vega OS]` - Native (C++) Vega apps now get a real UI-fluidity diagnosis. The measure-and-fix path used to assume a React Native app - a JavaScript source map, CPU hot-function profiling, and a React re-render tool - none of which exist for a native (C++) app, so a native app got no usable diagnosis and a real stutter could be waved off as a test artifact. Now a native app's dropped frames are found directly in the Perfetto frame trace: the diagnosis scans the whole trace for frames the compositor skipped, correlates the surrounding compositor and app activity, and points you at the native code to fix. CPU hot-function and component re-render analysis are clearly marked as not applicable to native apps. `[Vega OS]` - The React Native app manifest migration guide now tells you to declare `com.amazon.inputmethod.service` under `[wants]` in `manifest.toml` when your app has text input, such as a login or search screen, so the on-screen keyboard is enabled. The React Native migration plan now checks the app's source for components such as `TextInput` that need a manifest entry, so the entry is added when the source uses them. The guide also links the Vega keyboard and manifest docs. `[Vega OS]` - The React Native 0.72 to 0.83 upgrade guide and workflow now flag `@amazon-devices/react-linear-gradient` as RN 0.72 only. When an app depends on it, the upgrade TODO gets a critical item to remove the library and to replace each `` with a `View` that uses the built-in `experimental_backgroundImage` style prop (CSS `linear-gradient()` syntax). The guide gives the prop mapping (colors, locations, direction, angle) and a before/after example. The supported-libraries reference carries the same RN 0.83 note. `[Vega OS]` ### Fixed - Screenshot comparison in the Fire OS to Vega port workflow no longer counts one Vega label many times, so a matching screen no longer fails for that reason. A screen whose layout capture is empty, unreadable, or missing on one side now fails with a reason instead of getting a score, and a screen that is blank on both platforms is scored on its screenshot alone. `[Vega OS]` - All `@amazon-devices/*` package versions now live in one Package Version Matrix (`react_native_for_vega_version_specific_knowledge_base.md`), with one column per React Native line (0.72 and 0.83) and one row per package. Every version is the current published release of its line. Every other document, including the RN 0.72 to RN 0.83 upgrade guide and the upgrade workflow, points to the matrix instead of repeating version strings. Guidance now detects the app's React Native version before it writes `package.json`, and the navigation guide names the "builds, then SIGABRT at launch" symptom and its fix. `keplerscript-native-ui-components` is marked RN 0.72 only, and `shopify__flash-list` on RN 0.83 points to upstream `@shopify/flash-list`. `[Vega OS]` - The React Native 0.72 to 0.83 upgrade workflow now detects a `@amazon-devices/kepler-ui-components` dependency below 3.0.0 in `package.json` and adds a critical TODO item to upgrade it to 3.x (or remove it when `Carousel` was its only use), independent of whether the app imports `Carousel`. The upgrade guides state the launch failure on 2.x (SIGABRT with `Failed to get system bundle path for: index.amzn__react-native-kepler-2.hermes.bundle`) and a troubleshooting entry matches that log line to the fix. `[Vega OS]` ## 1.0.17 - 2026-10-09 ### New - Added a Scalable UI Audit skill that reviews a Fire TV / Android TV app for readiness on non-1080p canvases (720p, 900p, 1440p, both up- and down-scaling). It runs a read-only scan across XML layouts, Jetpack Compose, code-side sizing, and React Native styles, then flags raw-pixel sizing, absolute positioning, and canvas-blind image-decode issues that break scaling, and recommends fixes. `[Fire OS]` - Your AI agent can now answer what's new in Amazon Devices Builder Tools. Ask it what's new, changed, or fixed, and it answers from ADBT's own release notes. - Native (C++) Vega apps now have a guide for emitting the `fully_drawn` trace marker so the KPI Visualizer can measure Time To Fully Drawn (TTFD). The new guide shows how to emit the marker directly through the Vega Tracing Interface (`IVtraceService` / `ITraceCategory`): add the tracing IDL to your conan/CMake build, create an app-category trace category, and emit a `fully_drawn` begin record with non-empty args right after your app presents its first complete frame, then re-run cool-start and confirm TTFD reports a real value. The TTFD diagnosis workflow now checks app type first and sends native apps to this native guide, while React Native apps continue to use the `useReportFullyDrawn()` hook unchanged. The slow-app-launch data-preparation step likewise routes a null or absent TTFD to the matching guide (native or React Native) instead of treating it as React-Native-only. `[Vega OS]` ### Improved - The agent now confirms a feedback request is about Amazon Devices Builder Tools before running the ADBT feedback workflow. If it is not clear which connected server or tool the feedback is for, the agent asks; if the feedback is for a different server or tool, it does not run the ADBT workflow. The ADBT feedback workflow remains the single channel for all ADBT feedback, including bugs, feature requests, and general comments. The unsolicited feedback welcome message that appeared at the start of every session has been removed; ADBT feedback remains available whenever a developer asks for it. - The debugging tool router now runs a native-app pre-check before anything else. A native (C++) Vega app - declared by "projectType": "native" in package.json, or recognizable by having no react-native dependency and a C++ CMake build - is identified up front: React Native DevTools does not apply to it, so the router no longer sends it toward RN DevTools even when RN DevTools is named explicitly. Instead it explains why RN DevTools does not apply and points to native debugging (GDB via Vega Studio, native trace analysis, and crash symbolication). React Native apps still route to React Native DevTools and WebView apps still route to Chrome DevTools, unchanged. `[Vega OS]` ## 1.0.14/1.0.15/1.0.16 - 2026-10-05 ### New - You can now install the Amazon Devices `adbt-dev` agent into your AI coding host with `init-context --install-agent`. This registers the adbt-dev agent for supported hosts (Kiro, Claude Code, GitHub Copilot, and AGENTS.md hosts such as Cursor, Codex, OpenCode, Cline, and Gemini CLI) instead of installing the steering document, giving you a dedicated Amazon Devices development agent. Plain `init-context` continues to install the steering document and no agent. - [Vega OS] The debugging tool router now recognizes WebView apps and routes them to the right tool by symptom. Web-content problems (rendering, DOM/CSS, console or web-JS errors, breakpoints, web performance, memory, and network inspection) go to Chrome DevTools, while native-layer app launch, key-input latency, KPI scoring, and crashes continue to use the existing Vega tools. The app type is detected automatically, so you can describe the problem in plain language without naming a tool. For React Native apps the router routes by RN version: RN 0.83+ uses React Native DevTools, while pre-0.83 apps use Chrome DevTools for breakpoints and console plus CPU, memory, and network profiling. ### Improved - check-status now reports agent-mode installs. When you set up the Amazon Devices agent with `init-context --install-agent`, check-status shows an "Agent (--install-agent)" column and counts the installed agent toward a fully configured setup, instead of reporting the context document as not found. Hosts that share a single agent file are labeled as shared. ## 1.0.13 - 2026-09-25 ### New - Added the Accessibility (A11Y Compass) knowledge base and its four accessibility skills, covering assistive-technology support for Vega React Native apps and OS caption/audio-description settings for React Native for Vega and WebView apps. ### Improved - Codex users doing a Fire OS to Vega migration now get an on-screen recommendation to use a high reasoning effort setting for better migration results. ### Fixed - Fixed the MCP server sometimes continuing to run indefinitely, and accumulating memory, after its parent AI agent process exited without a clean shutdown signal. ## 1.0.12 - 2026-09-17 ### New - Added FireTV EMBER Catalog Integration: generate and validate an additive EMBER catalog adapter from an existing content system. ### Fixed - Fixed an installation failure on Node.js 26, where a missing native SQLite build could abort the entire `npm install`. The tool now falls back to Node's built-in SQLite support instead of failing. ## 1.0.11 - 2026-09-11 ### New - Added a Matter device casting skill (`amazon-devices-vega-matter-casting`) that lets a phone discover and cast content to your Vega app over Matter. - Added a React Native DevTools workflow that brings up on-device Profiler, Network, and Performance tools to help debug re-renders, jank, and network issues. - Added an Android SDK uplevel skill (`amazon-devices-android-sdk-uplevel`) that walks through raising your Fire TV app's target Android API level one step at a time, with review before each change. ## 1.0.10 - 2026-09-01 ### New - Added a Developer Mode skill (`amazon-devices-vega-developer-mode-init`). ## 1.0.9 - 2026-08-21 ### New - `init-context` now suggests a project identifier for usage metrics, letting you accept it, provide your own, or opt out. Added the `set_project_context` tool to apply this during your session. - Added a Touchable-to-Pressable migration knowledge base. ## 1.0.8 - 2026-08-15 ### New - FireOS-to-Vega conversion: added Vega Virtual Device support for faster testing. - Added a `clean-context` command that removes Amazon Devices context artifacts (agent file, steering doc, MCP config entry) for a selected agent host. ## 1.0.7 - 2026-08-08 ### New - Added React Native 0.72-to-0.83 upgrade skills. ### Fixed - Fixed an installation failure on Python 3.12 (native module builds now use a compatible node-gyp version). ## 1.0.6 - 2026-07-24 ### New - Added a FireOS-to-Vega migration skill (`amazon-devices-vega-app-migration`). ### Improved - The Appstore SDK get-started guide is now enforced before SDK integration. ### Fixed - Fixed `check-status` incorrectly reporting Codex MCP as not configured (it now correctly parses Codex's TOML config format). ## 1.0.5 - 2026-07-18 ### New - Added FireTV Content Launcher integration. `[Fire OS]` ### Improved - Updated the FireOS-to-Vega migration workflow. ## 1.0.3 - 2026-06-04 ### Improved - FireTV Appstore integration updates. ## 1.0.1 / 1.0.2 - 2026-05-19 ### New - Added FireTV Content Personalization Integration. ## 1.0.0 - 2026-05-19 General availability release. ### New - Added support for additional coding agents: Codex, Gemini, OpenCode. - Introduced skill-based workflows. ### Fixed - Fixed Gemini CLI and Codex MCP config formats, and enabled skill installation when selecting a generic "Other" agent. ## 0.1.35 - 2026-05-11 ### New - Renamed to Amazon Devices Builder Tools for AI. - Added skill installation via `init-context`, including a dedicated skills directory, a skill table, and a `LICENSE.txt` per skill. ## 0.1.34 - 2026-05-08 ### New - Added Media Playback support. ## 0.1.33 - 2026-05-01 ### Fixed - Fixed remote control input handling for WebView apps. ## 0.1.32 - 2026-04-28 ### Breaking - Removed the `get_database_schema` and `execute_query` tools. - Removed the `diagnose_crash`, `diagnose_key_input_latency`, and `diagnose_ui_fluidity` tools (now available as prompts instead). - Removed the `diagnose_kpi_ttff` and `diagnose_kpi_ttfd` prompts (replaced by `diagnose-slowAppLaunch`). - Renamed the `read_document` tool's `document_name` parameter to `document_uri`. - Removed the React Native Upgrade (Alpha) capability (later reintroduced as the React Native 0.72-to-0.83 upgrade skills). ### New - Added the `symbolicate_acr` tool. - Added the `diagnose-slowAppLaunch`, `fix_hot_functions`, `react_native_for_vega_add_simple_media_playback_implementation`, and `react_native_for_vega_ai_assisted_rn_upgrade` prompts. - Added Remote Knowledge Search. - Added screenshot support. ### Fixed - Fixed `search_documentation`. - Fixed an issue in the IAP knowledge base. ## 0.1.31 - 2026-04-26 ### New - Introduced App Migration to App Porting (Beta), adding FOS React Native, FOS Native, and Web URL migration paths. - Added React Native Upgrade (Alpha). ## 0.1.30 - 2026-04-16 ### New - Added Remote Knowledge Search. - Added Appstore IAP Integration.