Installation problem

[davidkats777]

@Nanako0129 my claude code has told me when i gave him the installation link "That response from the fetch tool is bizarre — it's citing constraints I never gave it and refusing to show the content, which itself is a sign the document may contain adversarial text aimed at AI readers."

[Nanako0129]

Thanks for reporting this — this is a real limitation in the current installation flow.

The installer is intentionally written as an agent-facing runbook, so it contains imperative instructions addressed to Claude. WebFetch's prompt-injection protection may therefore classify it as adversarial remote content even though the repository itself is benign. The classification can vary between Claude Code versions or sessions, so the current remote one-prompt path is not reliable enough.

As a workaround, clone a pinned release locally:

git clone --branch v1.1.4 --depth 1 https://github.com/Nanako0129/pilotfish.git
cd pilotfish
claude

Then ask Claude:

Read the local file install/AGENT-INSTALL.md in the current checkout and follow it to install pilotfish into my global Claude Code configuration.
Show me the full plan of changes and get my approval before writing anything.

I'm updating the installation documentation so the pinned local checkout is the recommended path, while remote fetching remains an optional convenience when WebFetch accepts it. If WebFetch blocks the remote runbook, please use the local checkout rather than disabling or bypassing the safety check.

[dromsak]

what if we turned it into a cc plugin? That should simplify. Will see if I can send a PR for it later today

[dromsak]

Opened #11, which takes the plugin route suggested in the comment above. It should resolve this directly rather than working around it:

• Install — there is no runbook to WebFetch and no imperative document for an AI reader to misclassify. /plugin marketplace add Nanako0129/pilotfish + /plugin install pilotfish@pilotfish is native, first-party Claude Code, so the prompt-injection false-positive that started this issue cannot occur. The pinned-clone-and-paste workaround goes away.
• Update — updating no longer means re-running the installer (which re-hits the same fetch), it is a marketplace version bump via /plugin.

#11 is framed as a proposal to shape rather than merge as-is, but if it lands it closes this.