Dosu learns from the tools your organization already uses. You connect those tools as Sources, and Dosu indexes their activity into a Library so it can serve that knowledge back to people and to coding agents. This page explains what connecting knowledge means, how Sources differ from Agents, and which connectors are available today.
What connecting knowledge means#
A Source is a connected tool that Dosu reads from, such as a GitHub repository, a Slack workspace, or a documentation space. When you add a Source to a Library, Dosu indexes the content and conversations there, so it can ground its answers and generated Documents in your real engineering activity.
You add and manage Sources inside a Library. A Library is a knowledge base for a project, team, or product area, and its Sources, Documents, Topics, Templates, and settings all live together. Open or create one from Libraries, and connect Sources while you set it up, or create a Library and connect Sources.
When you attach a Source to a Library, two independent toggles control how Dosu uses it:
- Read. Dosu references the Source when answering questions and writing Documents.
- Monitor. Dosu watches the Source for changes worth documenting and flags knowledge that has gone stale. See Monitors.
Sources versus Agents#
Connecting knowledge is separate from where Dosu takes action.
- Sources are the inputs. They determine what Dosu knows. Sources are configured inside a Library.
- Agents are the outputs. An Agent is how Dosu appears on platforms such as GitHub, Slack, or Microsoft Teams to answer questions and take action. When you create an Agent, you choose which Sources to ground it in. Agents are managed from Agents.
A growing engineering organization usually connects many Sources across repositories and channels into one or more Libraries, then points Agents to the right knowledge so that answers stay consistent wherever people ask. See Agents and Sources for the full concepts.
Available connectors#
Generally available and selectable today:
- GitHub. Repositories, issues, pull requests, discussions, and wikis. You can use include and ignore file patterns to control which files are indexed.
- Slack. Channel messages and threads. Requires the Teams plan.
- Notion. Workspaces and pages. Requires the Teams plan.
- Web Search. Real-time web access at query time. Dosu does not crawl, index, or store website content. It reaches the web only when a question needs it.
You can also bring existing documentation directly into a Library. See Import Docs to import pages from supported platforms, so Dosu can keep them up to date as your code changes.
The following connectors are built but not yet generally available in the app. Mark them as Beta or upcoming when you plan around them, and confirm current status with Dosu before relying on one:
- GitLab. Projects, issues, and merge requests, with include and ignore file patterns.
- Confluence. Spaces and pages.
- Microsoft Teams. Channel messages. Requires the Teams plan.
- Coda. Docs and pages.
What Dosu does with a Source#
Once a Source is connected and indexed, Dosu puts that knowledge to work in several places:
- Grounded answers in Chat and from Agents on GitHub and Slack.
- Generated and maintained Documents inside the Library, which you approve on the Review page before they post or publish.
- Context for coding agents through the Dosu MCP Server and the Dosu CLI.