Configuration

Your agent writes and runs this; here is what it means.

qaren check and qaren pr read .qaren/config.yaml from the directory they run in; --config <path> selects another file. Unknown keys are rejected.

appId: com.example.testapp
devClientScheme: testapp
metroPort: 8791
loginBlock: sign-in
loginMarker:
  id: login-screen

Keys

loginBlock and loginMarker are set together. loginBlock must be an action slug: it starts with a letter or digit, then letters, digits, _, . or -, at most 64 characters, without ...

video

For mode selection, defaults, validation, compatibility, privacy limits and persisted config-source reporting, follow the authoritative video publication contract.

ios

By default the iOS build uses the app's Expo CLI in generic build-only mode. Older Expo CLIs lack that mode: set ios.build with both workspace and scheme to build an existing Xcode workspace instead.

appId: com.example.testapp
devClientScheme: testapp
ios:
  build:
    workspace: ios/TestApp.xcworkspace
    scheme: TestApp

The workspace route builds Debug for the iOS Simulator with ad-hoc simulator signing. It runs no CocoaPods or codegen step of its own, so the workspace's native dependencies must already be ready for Xcode.

android

check and pr on Android borrow an emulator that is already booted; see Check a plan.

deadlines

Optional preparation budgets for check and pr: a native build time limit, a dependency-install time limit, a simulator-boot time limit, a manifest warm-up limit, and a dev-client attach limit. For registered-target deadlines, no-target waiting and patient recovery, see the authoritative admission and recovery contract.

When an iOS run needs a native build, build_seconds is one window that starts when the run asks for the machine's native-build lock: waiting for another run's build, prebuild and pods, the native build, its verification and its cache publication, including persistence, all share it. Build subprocess timeouts are capped to the remaining window, and no new build command starts after expiry. Non-interruptible teardown commands and their process-identity reads keep their own timeouts and can run after expiry to stop the build and prove its group gone; unresolved cleanup retains ownership for qaren cleanup. A synchronous cache copy already in progress is not interrupted; its completion is checked before publication. Output retirement runs outside this window. A run that spends it waiting refuses BUILD_CONTENDED and names the run holding the lock. As for a cached build, install, launch and readiness then share a fresh build_seconds window, and Metro startup has a separate one.

For manifest warm-up bounds, diagnostics and the Expo offline default and override, see the launch readiness contract.

Each limit is a whole number of seconds from 30 through 7200 inclusive. Omit the block, write deadlines: {}, or write a bare deadlines: to keep every default. A field that is present overrides only that field.

Out-of-range values are refused with SCENARIO_INVALID, rather than clamped. install_deps_seconds also bounds the pre-run pnpm process-group probe and its retries. A null, tilde, blank, negative, fractional, quoted, boolean, list, or object field value is a parse refusal, as is an unknown key, a camelCase alias, or a duplicate key. Explicit deadlines: null and deadlines: ~ are also refused. check and pr store the effective budgets at scenario.deadlines in run.json. For pr, these budgets come from the operator-selected configuration, even if the candidate worktree contains different deadlines. prepare keeps the deadlines in its scenario file, independently of app configuration.

appId: com.example.testapp
devClientScheme: testapp
deadlines:
  build_seconds: 5400

Environment