> ## Documentation Index > Fetch the complete documentation index at: https://docs.flowdeck.studio/llms.txt > Use this file to discover all available pages before exploring further. # Validation > Choose how FlowDeck agents check their work and share the results Writing the change is only part of finishing it. Validation is the work an agent does afterward to show that the result builds, passes the right tests, and behaves as expected. FlowDeck always requires project tests and repository checks. The Validation settings control the extra runtime checks and evidence an agent gathers after those required checks, so you can choose between a faster handoff and a more comprehensive review. ## Why FlowDeck validates more FlowDeck is built to let agents do more than edit files. An agent can use the project's saved target to build and test, run the real app, exercise changed flows, inspect logs, and capture evidence from simulators and devices. That makes it possible to catch problems a code diff or clean build cannot reveal, such as clipped text, a broken interaction, or state that fails only after the app is launched. Balanced is the default because it closes that loop without collecting evidence that does not help explain the result. UI work will usually be run and shown when a screenshot materially proves the change; a non-visual change may need only tests and a concise report. ## Choose a starting point The preset at the top of **Settings ▸ AI Workflows ▸ Validation** sets every option below it. You can then change any option independently. When you do, the preset reads **Custom**. Choosing a named preset again resets all five options to that preset. Relies on required tests and project checks. The agent runs the app only when those checks cannot prove the behavior, stays on the saved target, skips screenshots and recordings, and reports the result briefly. Runs changed features on the saved target, adds another target only for a meaningful risk, captures visual evidence when it helps, and gives a clear summary. This is the default. Exercises changed and adjacent flows, edge cases, and repeat interactions across multiple targets. It captures every relevant visual state and motion, then produces a detailed matrix. ## Customize each method ### Run the app Controls how much runtime behavior the agent exercises after the required checks pass. | Option | What the agent does | | ----------------------- | ----------------------------------------------------------------------------------------------------------- | | **Only when necessary** | Runs the app only when tests and project checks cannot prove the behavior. | | **Changed features** | Runs the affected flow on the saved target and checks an important failure or empty state when relevant. | | **Extended checks** | Also checks related flows, edge cases, and repeat interactions that may expose state or lifecycle problems. | ### Screenshots Controls still-image evidence. It does not decide whether the agent runs tests or checks the app. | Option | What the agent does | | ----------------------- | ----------------------------------------------------------------------------------------------------------------- | | **No screenshots** | Does not capture screenshots and describes any visible result briefly. | | **Only when necessary** | Captures a small set when images materially prove UI, layout, styling, copy, or an important visual state. | | **Always** | Captures every materially different visible state, including before and after when that makes the change clearer. | ### Screen recordings Controls video evidence for behavior that a still image cannot explain well. | Option | What the agent does | | ----------------------- | ----------------------------------------------------------------------------------------------------------------------- | | **No recordings** | Does not record video. | | **Only when necessary** | Records only when motion, timing, gestures, or a multi-step interaction cannot be shown clearly with a few screenshots. | | **Always** | Records every relevant motion or multi-step flow and includes the video as evidence. | ### Additional devices Controls whether the agent repeats relevant runtime checks beyond the saved target. | Option | What the agent does | | ----------------------- | ----------------------------------------------------------------------------------------------- | | **Saved target only** | Uses only the target selected in FlowDeck unless the task explicitly requires another one. | | **Only when necessary** | Adds one relevant simulator or device when there is a meaningful compatibility risk. | | **Multiple targets** | Repeats relevant checks across simulators or devices with meaningful compatibility differences. | ### Final report Controls how much validation detail appears in the agent's final response. It changes the report, not the checks that are required. | Option | What the agent does | | ------------ | ------------------------------------------------------------------------------------------------------------------------ | | **Brief** | Names the checks that passed, reports the test count, and includes only essential evidence. | | **Standard** | Summarizes tests, runtime checks, evidence, concrete outcomes, and any remaining gap. | | **Detailed** | Provides a target-by-target matrix with test counts, flows and states exercised, artifacts, results, and remaining gaps. | ## What never changes Validation preferences never let an agent skip required tests, repository gates, safety rules, permission requirements, or honest reporting. An agent must not claim a check or artifact it did not produce. A setting can reduce extra runtime work or evidence, but it cannot turn a failed check into completed work. Changes take effect when a session is next configured or restored, and for Team workers hired after the change. They do not rewrite the instructions of an agent that is already running.