nb-corp/gpt-with-taste can now be plugged into the coding agent harness Pi via native git package installation. The commit merged on 2026-10-17 (PR #6, xz-dev/ci/pi-release) added a pi.extensions entry (./dist/pi/index.js) to package.json so that Pi would find the adapter entry point through the repository root manifest. The change touched 3 files, with 30 lines added and 6 lines deleted.
This repository is a project that adds system instructions and source-aware steering to GPT. The Pi adapter registers two handlers, context_with_system and before_provider_request, and provides the /taste command. The tests check whether this adapter puts the source body and the user's steering together into the system message. According to the documentation, there are no runtime dependencies and no additional model calls.
The center of this change is the installation path. The documentation was rewritten from the manual-copy instructions into a procedure of running pi install git:github.com/NB-Corp/gpt-with-taste, checking /taste status after /reload, and using pi update --extensions and pi remove as management commands. The required environment is Pi 1.2.0 or later (@earendil-works/pi-coding-agent) and Node.js 22.19 or later, and the license is MIT.
However, the scope touched by this commit is limited to the Pi installation path. The added tests verify the pi.extensions value in the manifest, the registration of the two handlers, the existence of the /taste command, and that the source and the steering go into the message, but they do not measure the quality of model responses. The provided materials contain no performance figures or adoption cases, and the documentation also restricts activation to only one of package installation, local build, or the copy directory. It would be premature to assert without a separate evaluation how much the judgment actually improves.