Full auto: a project's own settings, resources and extensions are trusted without asking. That is one key doing the work -- defaultProjectTrust is ask by default, and always is what lets a non-interactive run load .pi/settings.json,…

[Catalog](/ru/ai/catalog)

[Publisher](/ru/ai/publishers/account_01KZET6ZKJN7S72T5H4WDV62T0)

- stable_id: setup_01M18ZTC8BSBTAVVMDXT6YYR2P

- version: 1.7

- digest: sha256:c8d30874562c5237a4d22a857ac480d21725b074e2d89cdc54aa37c66ea72b13

- harness: pi

- Назначение: Full auto: a project's own settings, resources and extensions are trusted without asking. That is one key doing the work -- `defaultProjectTrust` is `ask` by default, and `always` is what lets a non-interactive run load `.pi/settings.json`, install missing project packages and execute project extensions rather than ignoring all three. `enableSkillCommands` is kept and grants nothing: the product's own shipped settings documentation gives it a default of `true` -- re-read at 1.0.0, the current pin, where `docs/settings.md` tabulates it as `boolean | true | Register skills as /skill:name commands`. It stays so the posture states what it wants, and it is recorded as a restatement rather than left looking like a switch somebody threw. Nothing else in this product's settings withholds a capability by default: images, compaction and agent-level retry are all on, `defaultTools` uses the standard built-ins when omitted, and `enableInstallTelemetry` and `enableAnalytics` are left alone because they send data outward rather than granting you a tool. This product documents no sandbox to turn off. This is a setup posture -- keys in this product's own configuration file. It is not an execution profile and it grants no environment: what it changes is what the product asks you, not what anyone is permitted to run. The key measurement behind this posture: `docs/settings.md` shipped inside the 1.0.0 standalone archive, whose sha256 was checked against this baseline's artifact table before it was read -- both rows still stand there, `defaultProjectTrust` at line 34 and `enableSkillCommands` at line 156. The same file also gives `defaultProjectTrust` a default of `"ask"`, which is what makes the key here a change rather than a restatement. **The citation named 0.84.3 for three releases after the pin moved, then 0.84.4 for two more, then 0.87.1 for another**, and re-reading remains the way to find out whether the claim still holds rather than editing the number: it does at 1.0.0, where the standalone archive's own docs/ tree carries the table.

- Целевая роль:

- posture: full-auto

- trust_lane: authoritative

- author_verified: Да

- component_verified: Да

- Жизненный цикл: active

- Автор: account_01KZET6ZKJN7S72T5H4WDV62T0

- Теги: code-review, devops, planning

- install: echo '{"setup_id":"setup_01M18ZTC8BSBTAVVMDXT6YYR2P","setup_version":"1.7"}' | ai-stp task start --intent install --idempotency-key install-setup_01M18ZTC8BSBTAVVMDXT6YYR2P-1.7 --input - --json

- inspect: ai-stp registry version --kind setup --id setup_01M18ZTC8BSBTAVVMDXT6YYR2P --version 1.7