GitHub · Task agent
Qubot
GitHub's internal data-analytics agent, powered by GitHub Copilot. Any GitHub employee can ask a question about the company data warehouse in plain language and get an answer within seconds.
- Approach type
- Task agent
- Work
- Data
- Human involvement
- Assistive
- Invocation
- Interactive
- Deployment stage
- Scaled
- Evidence strength
- Detailed primary
- Entry reviewed
Where people stay involved
- data question → warehouse answerUnknown · Level unknown
Unclassified for data question → warehouse answer; human attention boundary: unknown.
- Observation date
- 2026-06
Implementation details
Powered by GitHub Copilot
Queries GitHub's data warehouse
Reported results and limitations
The catalog records what the sources report, with the scope and the denominator of every figure. A qualification below limits the figure it sits under.
Reported metrics
Hundreds of users run thousands of queries; data questions in internal Slack channels dropped
The source does not report the denominator of this figure.
- Reported by
- GitHub
- Scope
- Internal GitHub Qubot users and queries; no exact count or measurement window
- Observation date
- 2026-06
Hundreds of users run thousands of queries
The source does not report the denominator of this figure.
- Reported by
- GitHub
- Scope
- Internal GitHub Qubot users and queries; no exact count or measurement window
Reported outcomes and statements
Volume of data questions in internal data and analytics Slack channels dropped
- Scope
- Questions in GitHub internal data and analytics Slack channels
Sources and research details
Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.
- How we built an internal data analytics agenthttps://github.blog/ai-and-ml/github-copilot/how-we-built-an-internal-data-analytics-agent/
Research details for every claim on this page
- Summary
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Headline claim
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- Medium
- Confidence reason
- GitHub reported the adoption figures in its own engineering blog without independent verification.
- Reported by
- GitHub
- Scope
- Internal GitHub Qubot users and queries; no exact count or measurement window
- Denominator
- Not reported
- Method
- Not reported
- Observation date
- 2026-06
- SupportsHow we built an internal data analytics agentPreserved content.md, lines 70
- Model
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Tool access
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- Key observation
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- Medium
- Confidence reason
- GitHub reported the adoption figures in its own engineering blog.
- Reported by
- GitHub
- Scope
- Internal GitHub Qubot users and queries; no exact count or measurement window
- Denominator
- Not reported
- Method
- Not reported
- Observation date
- Not reported
- SupportsHow we built an internal data analytics agentPreserved content.md, lines 70
- Key observation
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- Medium
- Confidence reason
- Company reports a qualitative decrease without before-and-after counts.
- Scope
- Questions in GitHub internal data and analytics Slack channels
- SupportsHow we built an internal data analytics agentPreserved content.md, lines 70
- Operating model assessment
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Unverified
- Confidence reason
- The public evidence does not document where human attention returns in the question-and-answer flow.
- Observation date
- 2026-06