pi-auto-permissions 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,6 @@
+pi-auto-permissions
+Copyright 2026 pi-auto-permissions contributors
+
+This product includes material adapted from OpenAI Codex, Copyright 2025
+OpenAI, licensed under the Apache License, Version 2.0. See
+THIRD_PARTY_NOTICES.md for exact source revisions and modified files.

package/README.md

@@ -0,0 +1,304 @@
+# pi-auto-permissions
+
+`pi-auto-permissions` is a small, background permission guardrail for
+[Pi](https://github.com/earendil-works/pi). It has exactly two selectable modes:
+**Auto** and **Unrestricted**. Auto combines static rules, a Codex-inspired
+model reviewer, and an OS shell sandbox; Unrestricted stays available for the
+occasional session where the user deliberately wants no guardrail.
+
+There is no Ask mode, per-action confirmation prompt, approval file, or command
+catalog to maintain. A denied model action is not shown as a user approval
+dialog. The model receives this terminal result instead:
+
+```text
+Permission denied. This action was not executed. No override will be requested. Choose a materially safer action.
+```
+
+The model cannot appeal that result inside the action. It must issue a new,
+materially safer action. The user can still deliberately change the session's
+mode with `/perm`.
+
+## Requirements and installation
+
+- Pi `0.80.10`
+- Node.js `22.19.0` or newer
+- macOS or Linux for the strong shell sandbox
+- On Linux, the Sandbox Runtime's `bubblewrap` (`bwrap`), `socat`, and
+  `ripgrep` (`rg`) dependencies, plus its supported seccomp helper
+
+From a checked-out copy, install dependencies and register the package globally
+with Pi:
+
+```sh
+npm ci
+pi install /absolute/path/to/pi-auto-permissions
+```
+
+Use `pi install /absolute/path/to/pi-auto-permissions -l` for a project-local Pi
+package instead. During development, it can be loaded for one run:
+
+```sh
+npm ci
+pi -e ./src/extension.ts
+```
+
+The extension stores one private, machine-global permission record plus primary
+and recovery copies of an internal monotonic revision watermark under Pi's agent
+directory. Its only semantic settings are the enabled flag and reviewer tuple;
+schema/revision bookkeeping is internal, model credentials continue to be
+resolved by Pi, and credentials are never stored by this extension. There is
+intentionally no user-managed permission configuration file.
+
+## First use
+
+Auto is unavailable until its complete reviewer tuple has been selected. Until
+then, Unrestricted is the only effective mode and is shown as `Unrestricted`.
+Select an exact Pi model and an explicit thinking level:
+
+```text
+/perm-auto-model provider/model thinkingLevel
+```
+
+For example:
+
+```text
+/perm-auto-model openai/gpt-5.2 high
+```
+
+The example is illustrative; the provider, model, credentials, and thinking
+level must exist in the current Pi installation. Supported thinking-level
+values are `off`, `minimal`, `low`, `medium`, `high`, `xhigh`, and `max`, but
+each model may expose only a subset. The command validates availability,
+authentication, and support for that exact level before atomically saving
+`(provider, model, thinkingLevel)`.
+
+In an interactive Pi session, `/perm-auto-model` with no arguments opens a
+model picker followed by a picker containing only that model's supported
+thinking levels. A successful selection also puts the current session in Auto.
+It does not change the main conversation model or its thinking level.
+
+## Commands
+
+| Command | Effect |
+| --- | --- |
+| `/perm auto` | Select Auto for this session. Rejected without a valid reviewer tuple. |
+| `/perm unrestricted` | Select Unrestricted for this session. |
+| `/perm` | Open the two-item Auto/Unrestricted picker in an interactive session. |
+| `/perm-auto-model provider/model thinkingLevel` | Atomically select the global Auto reviewer tuple and put this session in Auto. |
+| `/perm-auto-model` | Interactively pick the reviewer and its thinking level. |
+| `/perm-enabled off` | Disable the extension's enforcement globally, including for existing and future sessions. |
+| `/perm-enabled on` | Re-enable global enforcement. Sessions then use their own requested mode. |
+
+`/perm-enabled` is an enable switch, not a third mode. Backends such as
+review-only are implementation states and never appear in `/perm`.
+
+Status is deliberately terse:
+
+- `Auto` — strong shell sandbox initialized and Auto is active.
+- `Auto (review-only)` — this OS is unsupported, so every model-originated
+  shell call is reviewed before any unsandboxed process can start.
+- `Auto (sandbox unavailable)` — macOS/Linux sandbox setup/runtime failed or
+  another same-process session owns Sandbox Runtime; Auto shell calls fail
+  closed.
+- `Auto (unavailable)` — catastrophic permission-engine construction failed;
+  all model tool gates deny and the extension's commands cannot mutate state
+  until a later successful session initialization (normally reload or process
+  restart).
+- `Unrestricted` — explicitly selected, or Auto is not yet configured.
+- `Off` — enforcement is globally disabled.
+
+In an Auto-requested session, invalid durable state is reported as
+`Auto (configuration fault)` and guarded actions fail closed. Explicit
+Unrestricted remains a deliberate bypass. The management commands remain
+available to attempt an explicit repair; repair refuses if neither private
+revision watermark is valid enough to prove a monotonic next revision.
+
+`Auto (unavailable)` is a narrower catastrophic construction state, not a
+normal mode or backend. No engine exists there to consult even a previously
+durable Off setting, so the outer gates deny rather than assuming a bypass.
+
+## Session semantics
+
+Every new, resumed, forked, cloned, or independently spawned Pi runtime starts
+with requested mode Auto. In particular, an Unrestricted parent cannot confer
+Unrestricted on a child process or subagent. If the reviewer has not been
+selected yet, that default Auto intent becomes effective only after a reviewer
+tuple exists.
+
+`/reload` is the sole exception: it restores the requested mode of that same
+logical runtime. Switching to another session or starting a child does not copy
+that checkpoint. The global enabled flag and reviewer tuple are reread at tool
+gates, so `/perm-enabled off`, `/perm-enabled on`, and reviewer changes also
+affect already-running Pi processes. A same-runtime command actively cancels
+that runtime's pending reviews. A sibling-process change cannot push an abort
+signal across processes; it is detected at the next pre-model, post-model, or
+final binding read and makes the old review stale.
+
+Permission admission is the policy linearization point. If a sibling commits a
+change before an action's controlling state read, the action uses the new state.
+An action already finally admitted before the commit may still enter its
+executor once; global Off is intentionally not a retroactive process-kill
+switch.
+
+## What Auto does
+
+Auto classifies the final Pi tool call visible to this extension:
+
+| Action | Auto behavior |
+| --- | --- |
+| Pi's built-in `read`, `grep`, `find`, `ls` | Statically admitted. |
+| Pi's built-in `write` and `edit` within the workspace or OS temporary roots | Statically admitted unless the resolved target is protected metadata. |
+| Other built-in `write` and `edit` targets | Reviewed before the direct file tool runs. |
+| Built-in `write` and `edit` targeting this extension's state/lock paths | Statically denied in Auto without model review. |
+| Ordinary `bash` on healthy macOS/Linux | Runs once in the fixed OS sandbox. |
+| Codex-dangerous `bash` with the default sandbox permission | Reviewed; an exact allow runs once inside the fixed sandbox. |
+| A `bash` call with `sandbox_permissions: "require_escalated"` | Reviewed; an exact allow runs once with normal host permissions. |
+| Any `bash` on an unsupported OS (including WSL1) | Reviewed; an exact allow runs once with normal host permissions. |
+| Any `bash` after a supported macOS/Linux sandbox failure | Denied before review or process creation. |
+| Third-party/custom tool | Reviewed; an exact allow invokes its trusted implementation without OS containment. |
+
+Static mutation admission resolves existing symlinks and the nearest existing
+ancestor of a new path. Workspace `.git`, resolved Git directories, `.agents`,
+`.codex`, and `.pi` are protected. The sandbox allows broad filesystem reads,
+writes only to the workspace and temporary roots, keeps protected metadata and
+the extension's durable state read-only, denies network and local binding, and
+applies to descendant processes.
+
+If direct-file path policy construction fails at startup, the fallback admits
+only the four known read-only built-ins and statically denies every `write` or
+`edit`. It does not guess path safety or ask the reviewer to replace missing
+classification.
+
+The reviewer sees a bounded conversation transcript and one canonical action.
+It has no tools. Its result must be exact schema-valid JSON; `ask`, prose,
+malformed output, timeouts, missing credentials, provider errors, cancellation,
+state changes, and every other non-allow outcome all deny. Reviews have one
+aggregate 90-second deadline, at most three provider attempts, and denial
+circuit breakers to prevent loops.
+
+A sandbox rejection is returned as an ordinary tool error. The extension does
+not replay a command that may have started. The model may issue a different
+command or a new exact `require_escalated` request, which is reviewed without
+opening a user dialog.
+
+The shell fallback matches the pinned Codex default Auto preset
+(`OnRequest + AutoReview + workspace`) without custom exec-policy rules or
+experimental permission features. Codex's optional rule files, managed-network
+flow, and additional-permission features are intentionally not reproduced.
+
+## Platform behavior
+
+On macOS and Linux, startup performs dependency checks, initializes
+`@anthropic-ai/sandbox-runtime`, and runs an actual contained `true` process.
+Only a successful probe enables sandboxed shell execution. On Linux, missing
+`bwrap`, `socat`, or strong seccomp/Unix-socket isolation is a sandbox failure.
+
+Sandbox Runtime owns process-global policy, so a supported-host Node process has
+one active strong-sandbox controller at a time. If another Pi session in that
+same process starts concurrently, its backend is reported as sandbox unavailable
+and its Auto shell calls deny; it never replaces or shares the first session's
+workspace policy. Unsupported-host ReviewOnly sessions do not claim this owner.
+The owner is released only after commands drain and reset succeeds. A failed
+final reset poisons strong-sandbox reuse until that Node process restarts, which
+prevents a later session from inheriting stale policy.
+
+An unsupported OS uses the visibly labeled review-only fallback. Review-only is
+functional but is not equivalent to containment: an allowed shell command has
+the user's normal host permissions. By contrast, a dependency,
+initialization, probe, or runtime failure on supported macOS/Linux never
+silently downgrades to review-only. It reduces availability and reports
+`Auto (sandbox unavailable)`.
+
+## Trust boundary and limitations
+
+This is a practical coding-agent guardrail, not a proof that model-approved
+actions are safe. Its formal routing and state guarantees are documented in
+[`docs/invariants.md`](docs/invariants.md), with the proof-linked construction
+in [`docs/implementation-plan.md`](docs/implementation-plan.md). Important
+limits are:
+
+- A reviewer model is probabilistic and can make a wrong allow decision.
+- Sandboxed shell commands have broad read access. The fixed sandbox blocks
+  network and unauthorized writes; it is not a general secret-reading boundary.
+- Reviewed escalated shell commands, reviewed out-of-root direct file writes,
+  and reviewed custom tools execute without OS containment after an allow.
+- Third-party tool implementations and other loaded Pi extensions are trusted.
+  They can have surprising effects, and this extension cannot sandbox their
+  implementation or stop a later extension from deliberately bypassing it.
+- Pi's user-entered `!` and `!!` shell commands are explicit user actions and
+  are outside this model-action guardrail.
+- Unrestricted and global Off intentionally bypass review and sandboxing.
+- Kernel, Pi, Sandbox Runtime, provider, filesystem, and hostile local-process
+  bugs or subversion are outside the guarantee. Static paths resist ordinary
+  symlink indirection but do not claim to defeat a hostile local TOCTOU race.
+- A compound sandboxed command can complete permitted effects before a later
+  operation is rejected. The extension never automatically retries it.
+- On an unsupported OS, review-only provides model review, not process
+  isolation. On supported macOS/Linux, failed containment instead fails closed.
+- Concurrent supported-host sessions in one Node process cannot each own a
+  different strong Sandbox Runtime policy. Additional sessions fail closed for
+  Auto shell until the owner closes successfully; reset failure requires a
+  process restart.
+- Global policy changes do not retroactively kill actions already admitted at
+  their final permission check.
+- A catastrophic permission-engine initialization failure denies all model tool
+  calls, but its slash-command host is unavailable until Pi successfully starts
+  the extension again.
+
+## Testing
+
+Run the deterministic suite from a clean install:
+
+```sh
+npm ci
+npm run check
+npm run pack:check
+```
+
+Most sandbox lifecycle coverage uses controlled adapters, while the real OS
+sandbox test stays gated. On a disposable macOS/Linux CI host with the native
+prerequisites installed, opt in to the real process-boundary test:
+
+```sh
+npm run test:real-sandbox
+```
+
+That gate starts actual descendant shells and verifies workspace and temporary
+writes, protected/outside/extension-state rejection, symlink and substitution
+escapes, a Node-interpreter escape attempt, local TCP denial, and a workspace
+that differs from the Node process cwd. Controlled controller tests cover
+dependency/probe/runtime failures, ownership and reset poison, shutdown drain,
+and no replay after ambiguous execution failure. The rest of the deterministic
+suite covers the effective-mode truth table, state durability and process races,
+path and symlink cases, pinned Codex dangerous-command cases, strict review
+verdicts, deadlines and cancellation, stale bindings, commands, public
+ExtensionRunner/ResourceLoader integration, two real print-mode `AgentSession`
+flows, lack of action-review dialogs, the explicit traceability manifest, and
+provenance hashes. The manifest maps every invariant to a named test file/title
+witness and fails if that witness disappears. The suite does not claim packaged
+CLI, live TUI, RPC, or JSON-mode coverage.
+
+## License and attribution
+
+This project is licensed under the
+[Apache License 2.0](LICENSE). See [NOTICE](NOTICE) and
+[THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md).
+
+- The Guardian policy and dangerous-command behavior are adapted from
+  [OpenAI Codex revision `0fb559f0f6e231a88ac02ea002d3ecd248e2b515`](https://github.com/openai/codex/tree/0fb559f0f6e231a88ac02ea002d3ecd248e2b515),
+  Apache-2.0. The exact upstream Guardian files and notice are vendored with
+  recorded SHA-256 hashes in
+  [`vendor/openai-codex/README.md`](vendor/openai-codex/README.md); derivative
+  source files identify their modifications.
+- Pi integration targets `@earendil-works/pi-coding-agent` `0.80.10` at
+  [revision `3da591ab74ab9ab407e72ed882600b2c851fae21`](https://github.com/earendil-works/pi/tree/3da591ab74ab9ab407e72ed882600b2c851fae21),
+  MIT.
+- Shell containment uses `@anthropic-ai/sandbox-runtime` `0.0.65`,
+  Apache-2.0.
+- Portable Codex-compatible shell parsing uses `web-tree-sitter` `0.25.10`
+  and `tree-sitter-bash` `0.25.1`, both MIT.
+- Atomic cross-process state locking uses `proper-lockfile` `4.1.2`, MIT.
+
+Runtime dependencies and the Pi development target are exact-version pinned in
+`package.json` and `package-lock.json`; the provenance unit test verifies those
+pins, upstream revisions, licenses, notices, and vendored hashes offline.

package/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,70 @@
+# Third-party notices
+
+## OpenAI Codex
+
+Portions of the automatic-review policy and command-safety behavior are adapted
+from [OpenAI Codex](https://github.com/openai/codex) at revision
+`0fb559f0f6e231a88ac02ea002d3ecd248e2b515`.
+
+Copyright 2025 OpenAI.
+
+Licensed under the Apache License, Version 2.0. The repository root `LICENSE`
+contains the license text. Adapted files carry a modification notice and retain
+their exact upstream source path and revision.
+
+This project changes Codex's denial recovery behavior: it removes human override
+and user-approval paths, returning a terminal model-directed denial instead.
+
+## Pi
+
+The extension API integration follows examples and public interfaces from
+[Pi](https://github.com/earendil-works/pi) at revision
+`3da591ab74ab9ab407e72ed882600b2c851fae21`.
+
+Copyright (c) 2025 Mario Zechner.
+
+Pi is licensed under the MIT License:
+
+> Permission is hereby granted, free of charge, to any person obtaining a copy
+> of this software and associated documentation files (the "Software"), to deal
+> in the Software without restriction, including without limitation the rights
+> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+> copies of the Software, and to permit persons to whom the Software is
+> furnished to do so, subject to the following conditions:
+>
+> The above copyright notice and this permission notice shall be included in all
+> copies or substantial portions of the Software.
+>
+> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+> SOFTWARE.
+
+## Anthropic Sandbox Runtime
+
+Shell containment uses
+[`@anthropic-ai/sandbox-runtime`](https://github.com/anthropic-experimental/sandbox-runtime)
+`0.0.65`, licensed under the Apache License, Version 2.0. It is an exact-version
+pinned external dependency and is not copied into this repository.
+
+## Tree-sitter and Tree-sitter Bash
+
+Codex-compatible shell parsing uses `web-tree-sitter` `0.25.10` and the
+`tree-sitter-bash` `0.25.1` WebAssembly grammar. Both are distributed under the
+MIT License. The grammar is from the same Tree-sitter Bash 0.25 series used by
+the referenced Codex revision; native install scripts are not required or
+executed.
+
+`tree-sitter-bash` is Copyright (c) 2017 Max Brunsfeld.
+
+`web-tree-sitter` is Copyright (c) 2018-2024 Max Brunsfeld.
+
+## proper-lockfile
+
+Atomic cross-process configuration locking uses `proper-lockfile` `4.1.2`,
+Copyright (c) 2018 Made With MOXY Lda <hello@moxy.studio>, distributed under
+the MIT License. It is an exact-version pinned external dependency and is not
+copied into this repository.