fix: Give copilot-oce agent access the Loop integration pipeline, and let it check correct channel for pipeline messages#26833
Merged
steffenloesch merged 5 commits intomainfrom Mar 25, 2026
Conversation
Add ado-office MCP server for the office ADO org so the OCE agent can query the Loop-FF integration pipeline (def 29163 in office/OC). Update the pipeline definitions table with an MCP Server column and key stages. Add Loop-FF integration pipeline health monitoring to Pipeline Health Monitoring section with specific instructions on how to check status. Add integration pipeline as Agent 3 in the dashboard skill so it appears in the shift status dashboard. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the FF Client OCE agent + dashboard documentation to monitor the Loop ↔ Fluid integration pipeline that lives in the office/OC ADO org, including configuring an additional ADO MCP server and updating dashboard output sections.
Changes:
- Add an
ado-officeMCP server (pointing at theofficeADO org) and document which server to use per pipeline. - Extend the shift dashboard skill with a new background agent to fetch the last 5 Loop-FF integration builds and a new dashboard section to display them.
- Update the Teams channel ID used for pipeline alert monitoring to the FF Client OCE channel.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.repoverlay/library/ff-oce/.claude/skills/ff-oce-dashboard/SKILL.md |
Adds Loop-FF integration pipeline monitoring agent + dashboard section; updates Teams channel used for alerts. |
.repoverlay/library/ff-oce/.claude/agents/ff-oce.md |
Adds ado-office MCP server and documents the MCP server to use for the Loop-FF pipeline; adds Loop pipeline monitoring task guidance. |
.repoverlay/library/ff-oce/.claude/skills/ff-oce-dashboard/SKILL.md
Outdated
Show resolved
Hide resolved
noencke
approved these changes
Mar 25, 2026
noencke
approved these changes
Mar 25, 2026
Contributor
|
🔗 No broken links found! ✅ Your attention to detail is admirable. linkcheck output |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add the
ado-officeMCP server and Loop-FF integration pipeline monitoring to the FF Client OCE agent and dashboard.Previously, the agent could only query ADO pipelines in the
fluidframeworkorg. The Loop-FF integration pipeline (def 29163) lives inoffice/OC, so it was invisible to the dashboard. This adds:ado-office) targeting theofficeorgMCP Servercolumn in the pipeline definitions tableReviewer Guidance
.repoverlayagent/skill markdown files — no production code.ff-oceagent and say "generate shift dashboard". Confirm the dashboard now includes a Loop-FF Integration Pipeline section alongside the existing pipeline health table.ado-officeMCP server uses the sameagency mcp adocommand as the existingadoserver, just pointed at a different org.