# grok-build full-auto@1.8
Full auto: nothing is asked, nothing is sandboxed, and every capability this build names is explicit. ui.permission_mode is always-approve, ui.yolo is set -- the product's own separate switch -- and sandbox.profile is off with…
[Catalog](/ru/ai/catalog)
[Publisher](/ru/ai/publishers/account_01KZET6ZKJN7S72T5H4WDV62T0)
- stable_id: setup_01M18ZSENZZNJ06RZ3C04B4PE2
- version: 1.8
- digest: sha256:f97bd00979926b5d7856030b9559fffce4bdb8d5925375a026bb5941e871ee89
- harness: grok-build
- Назначение: Full auto: nothing is asked, nothing is sandboxed, and every capability this build names is explicit. `ui.permission_mode` is `always-approve`, `ui.yolo` is set -- the product's own separate switch -- and `sandbox.profile` is `off` with `sandbox.auto_allow_bash` set. The feature and subsystem tables also enable background-agent coordination, codebase indexing, media tools, MCP watchers, the dashboard and goals. Monitor, background tasks and `/loop` are runtime mechanisms rather than invented setup keys. **What is claimed about defaults, and what is not.** `subagents.enabled` restates the documented default and is kept so the posture does not depend on that default remaining stable. For the other feature keys, this repository proves that the current binary accepts them, not what an omitted key defaults to. Telemetry and feedback remain untouched because they send data outward rather than grant a tool. This is a setup posture, not an execution permission profile. Exact versioned evidence lives in `references/grok-baseline.json` so prose here cannot silently become stale.
- Целевая роль:
- posture: full-auto
- trust_lane: authoritative
- author_verified: Да
- component_verified: Да
- Жизненный цикл: active
- Автор: account_01KZET6ZKJN7S72T5H4WDV62T0
- Теги: code-review, devops, planning
- install: Use ai-stp to configure my installed harness with setup_01M18ZSENZZNJ06RZ3C04B4PE2 version 1.8. Start with `ai-stp task intents --json`, inspect the exact object and gather the local target, source and provider facts required by the install input schema. Keep harness installation and updates under its own management.
```
Use ai-stp to configure my installed harness with setup_01M18ZSENZZNJ06RZ3C04B4PE2 version 1.8. Start with `ai-stp task intents --json`, inspect the exact object and gather the local target, source and provider facts required by the install input schema. Keep harness installation and updates under its own management.
```
- inspect: ai-stp registry version --kind setup --id setup_01M18ZSENZZNJ06RZ3C04B4PE2 --version 1.8
```
ai-stp registry version --kind setup --id setup_01M18ZSENZZNJ06RZ3C04B4PE2 --version 1.8
```