Bug type

Crash (process/app exits or hangs)

Summary

OpenClaw 2026.3.11 shipped with a broken bundled msteams extension installation on this macOS/Homebrew deployment. The stock extension directory declared a runtime dependency on @microsoft/agents-hosting, but the dependency was not actually present under the shipped extension's node_modules, causing the Microsoft Teams channel to fail during startup until a local manual hotfix was applied.

Steps to reproduce

1. Install or upgrade OpenClaw to 2026.3.11.
2. Configure Microsoft Teams normally.
3. Start or restart the gateway.
4. Observe Teams channel startup.

Expected behavior

The shipped msteams extension should start without any manual dependency repair. If the package declares @microsoft/agents-hosting as a runtime dependency, the distributed installation should include it or otherwise make it resolvable at runtime.

Actual behavior

The Teams provider fails during startup because the shipped extension cannot resolve @microsoft/agents-hosting.

Representative log evidence from the affected machine:

2026-03-08T14:17:06.104-07:00 [msteams] resolve failed; using config entries. Error: Cannot find module '@microsoft/agents-hosting'

• /opt/homebrew/lib/node_modules/openclaw/extensions/msteams/src/sdk.ts
  2026-03-08T14:17:06.115-07:00 [msteams] [default] auto-restart attempt 1/10 in 5s
  The same missing-module error repeated across multiple restarts and health-monitor retries.

OpenClaw version

2026.3.11

Operating system

MacOS 26.3.1

Install method

No response

Model

GPT 5.4

Provider / routing chain

openclaw direct to chatgpt

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Diagnosis
The bundled extension's package.json for 2026.3.11 declares:

"dependencies": {
  "@microsoft/agents-hosting": "^1.3.1",
  "express": "^5.2.1"
}
But on the affected machine, the shipped extension was unhealthy until @microsoft/agents-hosting was installed manually into:

/opt/homebrew/lib/node_modules/openclaw/extensions/msteams/node_modules/@microsoft/agents-hosting
That indicates a packaging/install artifact problem, not a tenant/app credential problem.

Temporary local hotfix used to restore service
The following command restored service on the affected machine:

cd /opt/homebrew/lib/node_modules/openclaw/extensions/msteams
npm install --no-save @microsoft/[email protected]
openclaw gateway stop
openclaw gateway start
Equivalent local service recycle also worked via launchctl bootout/bootstrap/kickstart.

Additional evidence
Affected logs also showed a duplicate local plugin warning due to an older separately installed user plugin at ~/.openclaw/extensions/msteams, but that warning was not the decisive breakage. The decisive fault was the stock shipped extension failing to resolve @microsoft/agents-hosting from:

/opt/homebrew/lib/node_modules/openclaw/extensions/msteams/src/sdk.ts

Impact and severity

Affected the MS Teams channel and so I had to fallback to an alternate in order to get the system working again.

Additional information

Suggested upstream fix

Ensure the release/install packaging for the bundled msteams extension includes @microsoft/agents-hosting
Add a release validation step that executes a runtime import check similar to:
node -e "require('/path/to/openclaw/extensions/msteams/node_modules/@microsoft/agents-hosting')"
Consider adding a post-install or release smoke test that exercises msteams/src/sdk.ts resolution in the installed artifact

Local operator mitigation adopted meanwhile
The local upgrade orchestrator was hardened to:

perform a post-upgrade Teams packaging-health check,
detect this exact missing-@microsoft/agents-hosting fault,
apply the local hotfix only when that exact fault is present,
log one of three explicit outcomes:
no hotfix needed
hotfix applied
still unhealthy