You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| `AGENT_CHAT_MAX_TURNS` | number | `50` | Maximum turns (tool calls) per chat session before the runtime terminates. Increase for complex multi-file tasks |
66
66
| `AIF_USAGE_LIMITS_ENABLED` | boolean | `false` | Master switch for the usage-limits feature. When `false` (default): `/runtime-profiles` skips Codex indexed-head overlay refresh and the Claude provider-identity lookup; the runtime service skips `observeRuntimeLimitEvent` / `extractLatestRuntimeLimitSnapshot` / `extractRuntimeLimitSnapshotFromError` during every runtime run; the WebSocket `project:runtime_limit_updated` broadcast is suppressed; the agent's stage error handler does not persist `limitSnapshot` onto tasks; the chat API omits `runtimeLimitSnapshot` from responses; and the web UI hides all 5 usage-limit surfaces (USAGE button in Header, TaskCard badge, TaskDetailHeader badge, ProjectRuntimeSettings "Recent Limit Signals", Chat active-limit banner + `CHAT_USAGE_LIMIT` fallback). Persisted snapshots already in the DB are still returned on read but never updated. When `true`, Codex overlays and broadcasts are fed from the background SQLite index (`codex_limit_heads`/`codex_limit_history`) instead of request-path filesystem scans. Set to `true` only when you actively monitor rate-limit windows |
67
67
| `AIF_WARMUP_ENABLED` | boolean | `false` | Master switch for project runtime warmup. When `false`, `/projects/:id/warmup` reports `enabled=false`, create requests return `403`, and the web UI hides Warmup entry points. When `true`, supported planner, implementer, and review runtimes can create time-limited seed sessions that later matching stage runs may fork. Warmup lifecycle logs use the `projects-route`, `api-runtime`, and runtime adapter log components and include project/runtime ids, TTL, expiry, and status without prompt text or secrets |
68
+
| `AIF_QA_PIPELINE_ENABLED` | boolean | `false` | Master switch for the task QA pipeline. When `false` (default): the manual `POST /tasks/:id/run-qa` endpoint returns `403` with `code: "feature_disabled"`, and the `autoQa` auto-trigger on `approve_done` is skipped. When `true`, manual runs and `autoQa` tasks execute the `/aif-qa --all` pipeline (change-summary → test-plan → test-cases) via `runApiRuntimeOneShot` and persist the three artifacts on the task |
68
69
| `AIF_ENABLE_CODEX_LOGIN_PROXY` | boolean | `false` | Enable the in-container Codex OAuth login broker and the api-side `/auth/codex/*` proxy. Dev-only. In production prefer `OPENAI_API_KEY`. See [Providers](providers.md#codex-oauth-login-in-docker-broker) |
69
70
| `AIF_CODEX_LOGIN_BROKER_PORT` | number | `3010` | Port the Codex login broker binds inside the agent container (not mapped to the host by the dev compose) |
70
71
| `AGENT_INTERNAL_URL` | string | `http://agent:3010` | Base URL the api uses to reach the agent-side Codex login broker over the docker network |
0 commit comments