Add support for custom cookie banner registration

[nolannbiron]

This PR introduces support for custom cookie banner handling. This is a v1 and is subject to change once we start using it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 8819aab

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@gitbook/browser-types	Patch
gitbook	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Summary of the deployments:

Version	URL	Status
Vercel	https://gitbook-v2-5ws4vdu33-gitbook.vercel.app	✅
Cloudflare	https://62f68f3d-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	2v	2c
GitBook	https://gitbook-v2-5ws4vdu33-gitbook.vercel.app/url/gitbook.com/docs	https://62f68f3d-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://gitbook-v2-5ws4vdu33-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://62f68f3d-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.gitbook.io/test-gitbook-open

[Copilot]

Pull request overview

This PR introduces support for custom cookie banner handling by allowing integrations to register their own cookie banner implementations. When a custom banner is registered, the built-in GitBook cookie banner will not be displayed.

Changes:

• Added new API method registerCookieBanner to the GitBook global object for integrations to register custom cookie banner handlers
• Created Zustand stores to track integration loading status and custom cookie banner registration
• Modified CookiesToast component to conditionally hide the built-in banner when a custom banner is registered
• Added e2e tests to verify built-in banner behavior with and without custom banner registration

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 6 comments.

File	Description
packages/browser-types/src/index.ts	Added type definitions for cookie banner handler and registerCookieBanner API method
packages/gitbook/src/components/Integrations/LoadIntegrations.tsx	Implemented cookie banner registration logic, added stores for tracking integration load state and custom banner registration, created hooks for accessing these states
packages/gitbook/src/components/Cookies/CookiesToast.tsx	Modified to wait for integrations to load and hide built-in banner when custom banner is registered
packages/gitbook/e2e/cookie-banner.spec.ts	Added e2e tests for cookie banner behavior with and without custom banner registration

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v2 (Inspect)	👍 Changes approved	17 changed	Feb 10, 2026, 10:23 AM
v2-cloudflare (Inspect)	👍 Changes approved	105 changed, 8 added	Feb 10, 2026, 10:27 AM
v2-vercel (Inspect)	👍 Changes approved	109 changed, 8 added	Feb 10, 2026, 10:26 AM

[SamyPesse]

Good start!

I think we'll probably also need to think about providing an API for integrations to create footer button or something as Onetrust will need to add a link to edit permissions.

[nolannbiron]

@SamyPesse for the footer button, I guess we could do something like this :

window.GitBook.registerFooterItem({
    label: 'Cookie Preferences',
    onClick: () => {
        OneTrust.ToggleInfoDisplay();
    }
});

the only issue I see is what happens if the footer is disabled, and where should we put the button? Under the copyright section ? Inside a dedicated “Policies” group ? I’m not sure what the best approach is