Does the GitHub Copilot integration require a new backend?

No backend change is required for the hosted widget path. Add the Chirps embed to the generated app's global layout; use the documented API path only when you intentionally build a custom native interface.

What does Chirps train on for GitHub Copilot?

Chirps uses the public URLs and files you provide during assistant setup. Review the knowledge source and test answers before publishing; do not treat an unverified crawl as a substitute for your own content review.

Developer workflow

GitHub Copilot and VS Code developers

Add an AI customer-support assistant to GitHub Copilot

Use GitHub Copilot to place the Chirps embed in your app's real layout file, while you remain in control of the review, test, and deploy steps.

10–15 min

Typical first install

Preview first

Review before publishing

Installation path

Reviewable code change

Context-aware placement in a checked-out repository

Human review remains part of the workflow

Works with the same Chirps snippet used by any website

Step-by-step

Install Chirps on GitHub Copilot

Follow the path that matches your project. Keep the generated snippet private to your workspace and verify the result on a preview URL.

Prepare the assistant knowledge

Add your public website URL or approved files in the Chirps dashboard and wait for training to finish. Chirps uses the sources you provide; it does not inspect your private repository automatically.

Copy the generated installation snippet

Open the assistant's Installation tab and copy the exact snippet for that assistant. Keep the assistant ID and configuration intact when you pass it to Copilot.

Ask Copilot to place and review it

Ask Copilot to add the snippet to the app's real global layout or HTML entry point. Review the proposed diff, run the app locally or on preview, and publish only after the widget and consent behavior look correct.

Keep the installation maintainable

The embed only mounts the widget. Your content, privacy settings, bookings, leads, and handoff rules stay editable in Chirps, so a content change does not require another deployment.

Questions

GitHub Copilot integration FAQ

How do I add Chirps AI to GitHub Copilot?

Create or select an assistant in Chirps, train it on the public pages or files you choose, copy the generated installation snippet, and place it in the global layout or code-injection area for GitHub Copilot. Test the preview before publishing.

What can the GitHub Copilot assistant help with?

It can answer questions grounded in your approved knowledge, collect enquiries, offer booking or lead forms when those artifacts are enabled, and hand conversations to your configured human-support channel.

Can I change the assistant after installation?

Yes. Widget appearance, knowledge, instructions, language, and enabled artifacts are managed in Chirps. You normally do not need to edit the site code again unless you move the widget to a different layout.