Home / Resources / GitHub and Notion in team chat
BLOG

GitHub and Notion in team chat without the add-on sprawl

How to keep code and docs context inside your chat with read-only connections instead of a pile of apps.

The short answer

Most teams bolt on one app for GitHub and another for Notion and end up with bot noise. A simpler pattern is read-only connections with mentions: tag a Notion page with @notionpage_ and a repo with @github_, so the context is a link and a preview inside the conversation, not a stream of notifications.

Why read-only matters

Safe

The connection can never edit a page or push code.

Quiet

Context on demand, not alerts.

Controlled

Choose who can use each connection.

What makes Dock different: it connects to your tools

Dock connects the places your team already works. Notion: connect your Notion pages, then type @notionpage_ in any chat to tag a page; everyone gets a preview card and your AI agents can read it. GitHub: link GitHub read-only, pin repositories to a chat, tag them with @github_ and ask the AI about them. Claude and Codex: use your own Claude or Codex plan inside Dock chats, or connect any MCP agent to your workspace with a token.

All of this sits next to chat, video meetings (with recording, transcripts and AI summaries), docs, tables, calendar, tasks and a drive, in a self-hosted app with no per-seat licence. You run the server yourself, and some integrations are young, so check the setup guides for what each one covers.

Questions

Is this a replacement for GitHub notifications?

No. It gives context when you ask or mention, not a feed of events.

Does it work with private repos?

With a token that can read them, shared only with the people you choose.

Try read-only connections in Dock

Free to self-host, no per-seat fee.

Download for Mac