Integrations

Integrations connect the tools your team already uses to the chat agent, so your copilot can act on them from inside the editor. You connect a service once in the panel; the agent then uses it directly through the Bash tool, with the credentials handed to it automatically — you never paste a token into the chat.

Discord, GitHub, and Notion ship today. More integrations are in development (see the roadmap).

Opening the panel

The Integrations view is reached from the panel’s settings menu (the same /-style menu that holds account and terminal actions) → Integrations. It shows a tile for each available service. Each tile carries its brand logo and a status chip — Not connected, Connected as …, or an error you can retry.

+----------------------------------------+
|  ‹ Integrations                        |
|                                        |
|   +------------+   +------------+      |
|   |  Discord   |   |   GitHub   |      |
|   |  ● Connect |   |  ● Connect |      |
|   +------------+   +------------+      |
|                                        |
+----------------------------------------+

Connecting Discord

Click the Discord tile’s Connect button:

1. Sign in opens Discord in your browser. You pick a server and channel, Discord creates an incoming webhook for that channel, and the panel captures it. The chip flips to Connected.
2. Add more channels anytime — each sign-in appends another channel webhook, so the agent can post to several channels and pick the right one by name.
3. Advanced (optional) reveals a bot token field and a default-server id. A bot token unlocks the things a webhook can’t: posting to any channel, resolving and @-mentioning teammates by name, and reading messages.

What the agent can do depends on which credentials are present — it always uses the most capable one available:

Capability	Channel webhook	Bot token
Post to a connected channel	✅	✅
Post to any channel	—	✅
@-mention a teammate by name	—	✅
Read / summarize a channel	—	✅

So with just the one-click webhook your copilot can “post a ‘new build is live’ note to #playtest”; add a bot token and it can also ”@ the person who reported the crash” or “summarize this morning’s feedback in #bug-reports”.

Reading message text needs one extra toggle

A bot can list and read messages, but Discord gates message text behind the privileged Message Content intent. If summaries come back empty, enable that intent for your bot in the Discord Developer Portal — the agent will tell you when this is the cause rather than retrying blindly.

Connecting GitHub

GitHub connects through the official gh CLI. Click the GitHub tile’s Connect button:

1. Sign in kicks off gh auth login, the standard GitHub browser sign-in. Once gh is authenticated the agent reuses that session — nothing to paste.
2. Personal access token (optional, under Advanced) — paste a token instead, for a headless / CI machine or to skip the interactive login. It’s stored as $GH_TOKEN and gh picks it up automatically.

With GitHub connected, the assistant drives gh through the Bash tool. It can read repo metadata, issues, pull requests and their diffs, GitHub Actions runs and logs, releases, code search, and any gh api call — and file or comment on issues. The default target is the repo of your project’s working directory; the agent passes --repo owner/name to act on another.

So you can ask things like “list the open issues labeled bug”, “show me the diff for PR #142”, “why did the last CI run fail?”, or “file an issue summarizing this crash” — without leaving the editor.

Connecting Notion

Notion connects with a per-workspace internal integration token — the API has no browser sign-in that would work without a hosted secret, so a paste-once token is both the simplest and the most robust path (it never expires and works on a headless / CI machine). Click the Notion tile’s Connect button:

1. Get a token opens notion.so/my-integrations. Create a New integration (Internal), pick your workspace, and copy the Internal Integration Secret (it starts ntn_). Paste it into the field — the chip flips to Connected as your integration.
2. Already have NOTION_TOKEN exported? The tile detects it and connects with no paste at all — the same zero-click “you’re already signed in” convenience as the gh sign-in, for a service that ships no CLI of its own.
3. Share your pages. A fresh integration can see nothing until you share pages with it: in Notion, open each page or database → ••• → Add connections → pick your integration. Access cascades to sub-pages. (If a search comes back empty, this is almost always why — the agent will tell you to share the page rather than reporting it missing.)

With Notion connected, the assistant reads and writes your workspace through the REST API: search pages and databases, read a design doc or GDD into context, query a task/bug database, create a page (e.g. file a task), update properties, and comment. So you can ask “what’s the spec for the dash ability?”, “list open tasks tagged combat”, or “file a task summarizing this crash in the Bugs database” — without leaving the editor.

Where credentials live

Connecting stores your credentials in a local locker under your home directory (~/.blueprintai/integrations/), readable only by your OS user. They never travel with the project, are never written into chat or logs, and are handed to the agent only as environment variables at launch — the agent is instructed never to print, echo, or log them.

Connecting, disconnecting, enabling, or disabling a service automatically reconciles the agent’s skill, so the assistant always knows exactly which tools it currently has and how to use them — no restart required.

• Disable keeps the credential in the locker but stops injecting it, so you can pause a service without re-authenticating.
• Disconnect wipes the locker entry entirely.

More integrations

Discord, GitHub, and Notion ship today. Others — Obsidian among them — are in active development and surface only in developer builds until each is production-ready. Track progress and request the ones you need on the roadmap.

This is about tools, not the AI

Integrations are external tools the agent acts on, separate from which AI powers the panel. The assistant itself runs on Claude; integrations are the services it reaches out to on your behalf.