Skip to content

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
user/stloesch/add-office-to-oce
Mar 25, 2026
Merged

fix: Give copilot-oce agent access the Loop integration pipeline, and let it check correct channel for pipeline messages#26833
steffenloesch merged 5 commits intomainfrom
user/stloesch/add-office-to-oce

Conversation

@steffenloesch
Copy link
Copy Markdown
Contributor

Description

Add the ado-office MCP 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 fluidframework org. The Loop-FF integration pipeline (def 29163) lives in office/OC, so it was invisible to the dashboard. This adds:

  • A second ADO MCP server (ado-office) targeting the office org
  • Explicit MCP Server column in the pipeline definitions table
  • A new dashboard agent (Agent 3) that checks the last 5 Loop-FF integration builds and flags failures
  • Pipeline monitoring instructions for the Loop-FF integration pipeline in the OCE task list
  • Corrected Teams channel ID for pipeline alert monitoring (FF Client OCE channel instead of FF Hot)

Reviewer Guidance

  • Changes are limited to two .repoverlay agent/skill markdown files — no production code.
  • To test: select the ff-oce agent and say "generate shift dashboard". Confirm the dashboard now includes a Loop-FF Integration Pipeline section alongside the existing pipeline health table.
  • The ado-office MCP server uses the same agency mcp ado command as the existing ado server, just pointed at a different org.

steffenloesch and others added 4 commits March 25, 2026 19:11
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>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-office MCP server (pointing at the office ADO 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.

@steffenloesch steffenloesch merged commit 51544e1 into main Mar 25, 2026
28 checks passed
@steffenloesch steffenloesch deleted the user/stloesch/add-office-to-oce branch March 25, 2026 20:06
@github-actions
Copy link
Copy Markdown
Contributor

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output


> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  272202 links
    1863 destination URLs
    2108 URLs ignored
       0 warnings
       0 errors


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants