PR #74163: WORKING: All Microsoft Issues and PRs (refresh)

• Repository: openclaw/openclaw
• Author: BradGroux
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/74163

Description (problem / solution / changelog)

Microsoft Ecosystem Issues & PRs Tracker

Purpose: Living checklist for maintainers to track all open Microsoft-related issues and PRs (Teams, Windows, WSL, Azure, M365/SharePoint).

How to use:

• Mark items resolved by editing this PR body and changing [ ] to [x]
• Claim items by adding your GitHub handle to the Assignee column
• Priority guide: P0 = crash/blocker/security, P1 = significant bug/regression, P2 = minor bug/enhancement, P3 = nice-to-have/stale
• Items marked (stale) have been flagged by the stale bot due to inactivity

Last updated: 2026-05-20 (closed #82873 as superseded; refreshed Microsoft tracker scope)

Summary

1. MS Teams Channel Plugin — Issues

Bugs / Crashes

Feature Requests

2. MS Teams Channel Plugin — PRs

3. Windows Platform — Issues

Bugs / Crashes

Feature Requests

4. Windows Platform — PRs

5. WSL (Windows Subsystem for Linux) — Issues

Bugs / Crashes

Feature Requests

No currently open items found.

6. WSL (Windows Subsystem for Linux) — PRs

7. Azure (Provider / Infrastructure) — Issues

Bugs / Crashes

Feature Requests

8. Azure (Provider / Infrastructure) — PRs

9. Microsoft 365 / SharePoint — Issues

Bugs / Crashes

No currently open items found.

Feature Requests

No currently open items found.

10. Microsoft 365 / SharePoint — PRs

No currently open items found.

Appendix: P0 Blockers (Start Here)

Appendix: High-Priority Bugs / Regressions

Appendix: Stale Items (Consider Closing)

No matching items found.

Audit Notes

• Rebuilt from the format of PR #49126 after the issue/PR purge.
• Source set is current open GitHub issues and PRs from openclaw/openclaw, plus cumulative closed/merged tracker rows recorded in maintainer update comments through 2026-05-20 and verified closed live.
• Closed counts exclude rows explicitly removed as non-Microsoft false positives by the Microsoft-scope scrub comments.
• Included title/label matches for msteams, Microsoft Teams, Windows, WSL, Azure, Entra/AAD, MSAL, managed identity, DefaultAzureCredential, Microsoft Graph, SharePoint, OneDrive, and Microsoft 365.
• Scope note: broad multi-channel PRs stay in this tracker only when the Microsoft surface is primary or independently reviewable. #83348 remains open outside this tracker queue; #82873 was closed as superseded by #83348.
• Generated with node scripts/generate-microsoft-tracker.mjs so the tracker and PR body can be refreshed after future triage passes.

Changed files

• CHANGELOG.md (modified, +1/-0)
• MICROSOFT_TRACKER.md (added, +361/-0)
• scripts/generate-microsoft-tracker.mjs (added, +428/-0)

PR #84170: fix(openai): add responses message item types

• Repository: openclaw/openclaw
• Author: hclsys
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/84170

Description (problem / solution / changelog)

Fixes #84109.

Summary

• add explicit type: "message" to system/developer/user Responses input items
• normalize system/developer prompt content to input_text content arrays
• keep Codex Responses empty-input fallback on the same explicit message item shape

Real behavior proof

• Behavior or issue addressed: Azure AI Foundry Responses endpoints reject shared Responses input items when system/developer/user entries omit the explicit type: "message" discriminator. This patch makes the exported Responses payload builder emit that stricter message-item shape for system/developer/user inputs.
• Real environment tested: Local OpenClaw checkout on commit 0a54691b3d after rebasing onto current main (d0f7c8fa28), Node.js runtime with the repo source loaded through tsx, using a Foundry-shaped openai-responses model config (https://example.services.ai.azure.com/api/projects/demo/openai/v1).
• Exact steps or command run after this patch: node --import tsx -e ... was run from the repo root to import buildOpenAIResponsesParams, build a Foundry-shaped Responses payload, and print params.input.
• Evidence after fix: Console output from the post-patch runtime command showed both input items include type: "message" and input_text content.

[
  {
    "type": "message",
    "role": "system",
    "content": [
      {
        "type": "input_text",
        "text": "system"
      }
    ]
  },
  {
    "type": "message",
    "role": "user",
    "content": [
      {
        "type": "input_text",
        "text": "Hello"
      }
    ]
  }
]

• Observed result after fix: The shared Responses payload builder now emits explicit type: "message" entries for the system and user input items and wraps the system prompt as input_text, matching the stricter Azure AI Foundry payload shape reported in #84109.
• What was not tested: No live Azure AI Foundry request was sent because no Azure credentials/project endpoint are available in this environment.

Validation

• node scripts/run-vitest.mjs src/agents/openai-transport-stream.test.ts -t "Responses" -> 2 files passed, 50 tests passed, 288 skipped
• node scripts/run-vitest.mjs src/agents/openai-transport-stream.test.ts src/agents/openai-responses-payload-policy.test.ts extensions/microsoft-foundry/index.test.ts -> 4 files passed, 374 tests passed
• pnpm lint -- src/agents/openai-transport-stream.ts src/agents/openai-transport-stream.test.ts CHANGELOG.md -> 0 warnings, 0 errors
• git diff --check main...HEAD -> clean

Note: NODE_OPTIONS=--max-old-space-size=8192 pnpm exec tsc --noEmit --pretty false hit Node OOM after ~115s before diagnostics, so no typecheck diagnostics were produced locally.

Changed files

• CHANGELOG.md (modified, +1/-0)
• src/agents/openai-transport-stream.test.ts (modified, +49/-4)
• src/agents/openai-transport-stream.ts (modified, +10/-2)