mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-28 20:21:50 +01:00
nickyleachandPaperclip
27bdb45fae
The paperclip-api helper dropped any path prefix from PAPERCLIP_API_URL by taking only the URL origin, so a reverse-proxied deployment sent every request to the wrong path. It now keeps the normalized base, including its prefix, and rejects a path that resolves outside that prefix. A generated property test with 200 cases and a named table cover this. A host-credentials run now stages the token-free paperclip-api helper, but it also picked up a forced PATH/ZDOTDIR/BASH_ENV and six shell profile files meant for a managed Git credential run. That silently narrowed the host's own shell setup. The launcher now applies the profile redirection only when it also stages git or gh, and a host-credentials run keeps only its PATH entry and the launcher directory. A login shell can still reorder PATH ahead of the launcher directory on a host-credentials run; nothing here restores it, since doing so would again override the host's own profile. This is a known, accepted residual. The API access note rendered from a launcher directory alone, so a future caller that stages only git and gh, without paperclip-api, could still make the note teach a command that is not on PATH. The launcher now reports its staged program list, and the note reads that list instead of the directory. Co-Authored-By: Paperclip <noreply@paperclip.ing>