microsoft / microsoft/sre-agent

[Bug] Live Report authoring tool bundle is missing at runtime

Open
#275 1 comment 0 reactions 1 assignee View on GitHub

@yash-nisar is already working on this.

Since Jul 29, 2026.

Dominant language
PowerShell
Stars
160
Forks
97
Avg merge
2d 5h
Merged PRs (30d)
12

Description

## Issue Description

The enabled `live_report_authoring` system skill advertises `SaveReport`, `ListReports`, `GetReport`, `ListConnectors`, and `ListConnectorTools`, but those tools are unavailable at runtime in a newly created Live Report authoring thread.

## Steps to Reproduce

1. Confirm `live_report_authoring` is enabled and its skill metadata lists the five Live Report tools.
2. Create a new authoring thread through the supported `.../reports/authoring-thread` flow.
3. Ask the agent to load `live_report_authoring` and create or list a report.

## Actual Behavior

Every Live Report tool invocation fails with `Tool '' is not available`. The general tool inventory omits definitions for all five tools, even when explicit enabled overrides are present. Disabling and re-enabling the skill does not restore the tool bundle.

This reproduced with both GitHub Copilot GPT-5.6 Sol and Anthropic Claude Opus 5, so it does not appear model-specific.

## Expected Behavior

Starting a Live Report authoring thread should attach the five tools declared by the enabled system skill so the report can be discovered, authored, and saved.

## Impact

Live Report creation and updates are completely blocked. The agent can author and validate HTML but cannot persist it to Operations Hub.

## Evidence

- Skill catalog: enabled system skill lists all five expected tools.
- Tool catalog: definitions for the five tools are absent.
- Fresh authoring thread created by the official authoring-thread endpoint still cannot invoke them.
- Resetting the individual skill override did not repair registration.

Private diagnostics and identifiers are available through an approved internal channel if needed.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.