Integrate Pubb in your project

Build with your coding assistant.

Start with your existing project. Give your coding assistant a prompt and let it choose the integration that fits your languages, frameworks and package managers.

From a prompt to your first event

Open your project in your coding tool so it can inspect the code, dependencies and project instructions.
Copy the prompt below. Keep “Detect My Stack” selected, or choose a language, then describe the feature you want to build.
Review the changes, add your credentials locally and verify an event from your backend to your client.

The prompt asks your assistant to choose SDKs separately for the client and trusted backend, reuse your authentication and follow the documented installation steps.

A prompt for your stack

Use this as a starting point for notifications, live dashboards or another realtime feature. It includes links to Pubb’s integration context and SDK guides.

Your Stack

Your integration prompt

Add realtime notifications to this existing project using Pubb.

Read the integration guide first:
https://pubb.io/AGENTS.md
SDK installation directory: https://pubb.io/docs#sdk
Shared protocol and dependency selection: https://pubb.io/AGENTS.md

Inspect the project's instructions, languages, runtimes, manifests, lockfiles and code structure. Choose dependencies separately for its client and trusted backend. Select the official Pubb SDK matching each part and follow its documented Git or local package installation. Verify package names and runtime support; a public GitHub repository does not imply a package registry release. Reuse the project's package manager and authentication. Do not add Node.js or a new backend just to integrate Pubb into another stack.

Connect a client to the public channel "notifications" and publish a sample event from the trusted server. If the project has no backend, implement the subscriber and document the required server publisher. Keep personal or restricted data on authorized private channels.

Use placeholders for the app ID, public app key and app secret, following the guide's environment configuration for this framework. Only the public app key belongs in the client. Keep the app secret server-side; I will add credentials locally.

Add connection cleanup, error handling, reconnect backoff and resubscription. Explain the files you changed, the environment setup and how to verify end-to-end delivery. Only report checks you actually ran.

Read the protocol reference

After pasting, change the first line to describe your feature. If your tool cannot open links, attach the Markdown guide instead.

Download guide for AI (.md)

Add your application credentials

Create an application in the Pubb dashboard to get your app ID, public app key and app secret. Ask your assistant to use placeholders, then fill them in locally.

Clients use the public app key to subscribe. Your trusted backend uses the app secret to publish and authorize restricted channels. Keep secrets out of client code and use authorized private channels for personal or restricted data.

If your project has no backend, start with the subscriber. Choose a trusted backend before adding publishing or private channel authorization.

Verify your first event

Connect your client and wait for its subscription to notifications to succeed.
Publish a sample message.sent event from your backend to the same application and channel.
Confirm the client receives the payload. HTTP 202 means the publication was accepted for processing; check delivery in the client too.
Check connection cleanup, reconnect and resubscription. For private channels, test both allowed and denied access.

Ask your assistant to explain the files it changed and the checks it ran. Refresh durable state from your backend after reconnecting; missed events are not replayed.

Explore SDK guides Read the protocol reference