> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/changelog/releases/163.md).

# 163

Appfarm 163 opens Flow DevTools to everyone, adds one-click value mapping, and lets you move through Create's trees with the keyboard.

| Channel  | Date             |
| -------- | ---------------- |
| Early    | October 12, 2026 |
| Standard | October 19, 2026 |
| Stable   | October 26, 2026 |

## New and improved

### Flow DevTools

* **Debug Flows with Flow DevTools.** Open [Flow DevTools](https://docs.appfarm.io/reference/appfarm-client/developer-tools-for-flows.md) from the Flow tools menu to watch a run as it happens: **Listen for next run** waits for the Action to run from an app, its endpoint, a [schedule](https://docs.appfarm.io/reference/flows/schedules.md) or an [MCP tool](https://docs.appfarm.io/reference/flows/mcp-servers.md), or you can start a run yourself. You see each node's status, logs and duration, loop iterations, the run's data and its output.
* **Turning it on.** Select **Enable Flow DevTools** for the [environment](https://docs.appfarm.io/reference/configuration/environments.md) (it needs **Enable Flow endpoints and schedules**), and grant **DevTools for Flows** on the Login access tab of [Permissions](https://docs.appfarm.io/reference/security/permissions.md). The Developer role gets Development by default. Other environments need a role that also has Client access to that environment.
* **Secrets are masked,** including Authorization headers and credential query parameters. (DEV-2195, DEV-3095)

### Apps

* [**Keep Device Awake**](https://docs.appfarm.io/library/action-nodes/keep-device-awake.md) **reports when the browser refuses.** The node used to carry on silently. It now waits up to 10 seconds and then fails with "Could not prevent device sleep", which the Action's error handling can catch. (DEV-2751)
* **Chart events return the right values.** On Series Click returns the clicked date on a date axis instead of an interpolated value, and chart event outputs take the bound property's data type. (DEV-2748, DEV-2761)

### Appfarm Create

* **Map from source.** A **Map from source** button in value mappings fills each empty property from a data source, schema or Action param field with the same name and data type. (DEV-2742)
* **Keyboard navigation.** Move through the Action node tree, the data model lists and the views and components tree with the arrow keys, Home and End. Action node descriptions show as plain text under the node. (DEV-2754, DEV-2755, DEV-2756)

### Appfarm AI

* **Ask mode knows your Solution.** [Ask mode](https://docs.appfarm.io/reference/appfarm-ai/ask.md) can answer questions about your own Solution and link to the parts it mentions. It doesn't make changes. (DEV-2747)
* [**Build mode**](https://docs.appfarm.io/reference/appfarm-ai/build.md) **uses Claude Opus 5.5.** (DEV-2749)

## Fixes

* A theme color that couldn't be parsed brought down the whole app with the crash screen. (DEV-2730)
* Publishing a change that removed a data source another data source depended on stopped open apps from loading the new version, and live updates could stop after a publish. (DEV-2474, DEV-2619)
* Apps reconnect more reliably after a dropped connection. (DEV-2611, DEV-2613, DEV-2614)
* A drop onto a drop area covered by other content was silently ignored, and Escape could run On Drop. (DEV-3324)
* The link popover in rich text didn't use the theme's link color. (DEV-2729)
* A fixed-position Shareable Component drew over other panels in Create. (DEV-2758)
* Create froze on a corrupt Action node chain, and the data binding picker disabled data sources whose only matches were schema fields. (DEV-2743)
* Appfarm AI threads could get stuck rejecting every message. (COPS-962)

***

Covers 163 up to 163.0.24.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appfarm.io/changelog/releases/163.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
