golemandClaude Opus 5.5
71fa5ddbc8
The five PNGs are generated output, like the build ZIP, so they leave git and docs/amo/screenshots/ is ignored. The README's command produces them, and with squash merges they never reach develop or main, so the repository needs no Git LFS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5.0 KiB
Add-ons listing
Paste-ready text and images for the addons.mozilla.org listing. Edit them in the AMO Developer Hub under the add-on's listing details.
Listing copy follows the copy rule in the options design: ChatGPT opens with the text filled in. Never say the text is sent, searched, or asked. Keep "private", "incognito", and "secure" away from temporary chat, and call temporary chat and web search hints.
Summary
Plain text, 250 characters at most:
Ask ChatGPT from anywhere in Firefox. Type gpt in the address bar, right-click selected text, press <Alt>+<Shift>+G, or click the toolbar button. ChatGPT opens with your text filled in. Tiny, fast, no API key.
Description
AMO accepts a few HTML tags here, such as <b>, <ul>, <li> and <a>.
Anything else, like <Ctrl>, shows as plain text, as <ctrl>-L does on the
1.2 listing. Check the preview after saving.
Ask ChatGPT from anywhere in Firefox.
<b>Four ways to use it</b>
<ul>
<li><b>Address bar:</b> press <Ctrl>+L, type gpt and your question, like "gpt why does my cat knock things over?", and press <Enter>.</li>
<li><b>Right-click:</b> select text on any page and choose Ask ChatGPT.</li>
<li><b>Keyboard:</b> select text and press <Alt>+<Shift>+G. With nothing selected, it opens a blank chat.</li>
<li><b>Toolbar:</b> click the Ask ChatGPT button.</li>
</ul>
ChatGPT opens with your text filled in. You may need to sign in to ChatGPT.
<b>Small on purpose</b>
The whole extension is about 56 KB, with no libraries, no server, no API key and no intermediary, and nothing is reported to us. Firefox opens chatgpt.com directly, and it never makes ChatGPT your default search engine unless you choose to.
<b>Make it yours</b>
<ul>
<li>A simple right-click menu, or an advanced one with Explain, Summarize, Debug code and Translate.</li>
<li>Your own prompt template, like "Explain simply: {query}".</li>
<li>Open ChatGPT in a new tab, a background tab or a new window.</li>
<li>Ask for a temporary chat or a web search. These are hints, and ChatGPT decides whether to honour them.</li>
<li>Add your own search keyword or change the shortcut in Firefox's settings.</li>
</ul>
Search with ChatGPT is an unofficial extension by Zavage Software and isn't affiliated with OpenAI.
<a href="https://git-repos.zavage.net/zavage-software/search-with-chatgpt-powered-by-openai-extension">Source code</a> · <a href="https://zavage-software.com/portfolio/search-with-ChatGPT">Project website</a> · <a href="https://zavage-software.com/contact-us">Feedback or report a bug</a>
Update "about 56 KB" when the package size changes noticeably. npm run build
prints the ZIP's path.
Screenshots
Upload in this order, with these captions. Each image is 1280×800, the size AMO recommends, and carries no added text, as Mozilla's listing guide advises.
The images are not committed. Generate them as described under
Regenerating the images; they land in
docs/amo/screenshots/, which git ignores, so the links below work once you
have.
| Image | Caption |
|---|---|
| 1-address-bar.png | Type gpt and your question in the address bar. ChatGPT opens with it filled in. |
| 2-right-click.png | Select text on any page, right-click, and choose Ask ChatGPT. |
| 3-keyboard.png | Or select text and press ++G. |
| 4-toolbar.png | Or click the Ask ChatGPT button in the toolbar. |
| 5-advanced-menu.png | Switch to the Advanced menu for Explain, Summarize, Debug code and Translate. |
A real screenshot of the options page in about:addons makes a good sixth
image: one genuine screenshot next to the drawings helps people trust them.
Suggested caption: "Every setting on one simple page."
Regenerating the images
The images are the options page's drawings, enlarged by
screenshots.html, which reuses options/options.css. They
are generated rather than committed, like the build ZIP. When a drawing in
options/options.html changes, copy the change into screenshots.html. Then,
to produce the images, run these from the repository root:
python3 -m http.server 8766 --bind 127.0.0.1 &
profile=$(mktemp -d)
echo 'user_pref("layout.css.prefers-color-scheme.content-override", 1);' > "$profile/user.js"
for shot in 1-address-bar 2-right-click 3-keyboard 4-toolbar 5-advanced-menu; do
firefox --headless -no-remote -profile "$profile" --window-size=1280,800 \
--screenshot "$PWD/docs/amo/screenshots/$shot.png" \
"http://127.0.0.1:8766/docs/amo/screenshots.html#$shot"
done
kill %1
The output path must be absolute. The throwaway profile forces the light theme,
and a fresh one avoids Firefox serving an old copy of the page from its cache.
Opening screenshots.html without a #fragment shows every image in order.