# pi full-auto@1.2
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](/en/ai/catalog)
[Publisher](/en/ai/publishers/account_01KZET6ZKJN7S72T5H4WDV62T0)
- stable_id: setup_01M18ZTC8BSBTAVVMDXT6YYR2P
- version: 1.2
- digest: sha256:8c88fb3809870010f0450ac8fdc14fec1d9fce1609a120a3f73f6206b709f0de
- harness: pi
- Purpose: 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 0.84.4, 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 0.84.4 artifact, whose digest was checked against this baseline's artifact table before it was read. 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**, and re-reading was the way to find out whether it still held rather than editing the number; it does, and the file is byte-identical in the standalone distribution this provider now installs and in the npm package it used to.
- Target role:
- posture: full-auto
- trust_lane: authoritative
- author_verified: Yes
- component_verified: Yes
- Lifecycle: active
- Author: account_01KZET6ZKJN7S72T5H4WDV62T0
- Tags: code-review, devops, planning
- install: ai-stp registry version --kind setup --id setup_01M18ZTC8BSBTAVVMDXT6YYR2P --version 1.2
```
ai-stp registry version --kind setup --id setup_01M18ZTC8BSBTAVVMDXT6YYR2P --version 1.2
```