Embed Giscus comments on my site
Giscus puts a comment thread under a page. The comments live in a GitHub discussion you own, so you keep them and you moderate them. There is nothing extra to pay for.
The prompt
“Add comments to the blog post pages using Giscus, pointed at my GitHub repository.”
Signed in, Get my prompt fills in your site for you. Otherwise press Copy and fill in the [bracketed] parts. First time? Connect your AI to bernard once: Use your own AI (opens in a new tab).
Ask your AI
Add comments to the blog post pages using Giscus, pointed at my GitHub repository.
What you need first
A public GitHub repository with Discussions turned on, and the four ids the giscus.app configurator gives you.
What bernard checks
The Giscus comments tool is on bernard’s permitted list. Someone read the maker’s own instructions (https://giscus.app) on 2026-09-14 and decided it was safe to run on a customer’s site: data-theme also accepts a CSS URL that applies inside the Giscus iframe, so the pattern is narrowed to the built-in theme names only. Loads a third-party iframe, so the row is consent functional. Your site loads it from the maker’s own address. Giscus comments comes from the maker’s own address, always at whatever version they currently publish, so there is no pinned version here for bernard to check each week. Keeping it current is the maker’s job. What bernard controls is the address: nothing else may be loaded in its place.
Your AI writes the exact tag bernard permits, on a private preview. You look at it and approve it before anything goes live.
People search for this as: comments, discussion, giscus, blog comments, feedback.
What your visitors see
Giscus comments sets its own cookies, so on your live site it does not load straight away. In its place a visitor sees a “Show Giscus comments” button with a short note under it saying that showing it lets Giscus comments use cookies. One press and it loads. Nothing is stored about that press, so the button is there again on their next visit. No cookie banner is added for it. If Giscus comments was already on your site when it moved to bernard, it keeps working exactly as before.
For the full list of libraries, what is waiting, and how to ask for one that is not there, see Embed a calendar, a diagram, a chart or another tool on my site.
Questions people ask
- Do I need to write any code to use the Giscus comments tool?
- No. Your AI writes the exact tag bernard permits and puts it on a preview. You approve it before it goes live, and pasted code is removed for safety every time.
- Is the Giscus comments tool safe on my site?
- bernard admits it only from its own published address, with its settings written as plain data rather than code. Giscus comments comes from the maker’s own address, always at whatever version they currently publish, so there is no pinned version here for bernard to check each week. Keeping it current is the maker’s job. What bernard controls is the address: nothing else may be loaded in its place. Nothing else about it can be changed from a page.
- What do I need from the Giscus comments maker first?
- A public GitHub repository with Discussions turned on, and the four ids the giscus.app configurator gives you.
- Can I change it later?
- Yes. Say what you want different and your AI redoes it on a preview for you to approve. Nothing about it is baked in.