Update Teams CLI install command by heyitsaamir · Pull Request #88103 · openclaw/openclaw

heyitsaamir · 2026-05-29T18:41:48Z

Summary

Updates the Microsoft Teams setup docs to install @microsoft/teams.cli without the old @preview tag.

Why

Teams CLI is out of preview now, so the docs should point folks at the current stable package. Less vintage npm incantation, more happy setup.

Interesting bits

Also removed the note warning that Teams CLI is currently in preview, since that is no longer true.

Real behavior proof

Behavior addressed: Microsoft Teams setup docs now install the GA @microsoft/teams.cli package instead of the old @preview tag.

Real environment tested: Local OpenClaw docs source checkout, plus the public npm registry state for @microsoft/teams.cli.

Exact steps or command run after this patch:

pnpm docs:list | rg -i 'msteams|teams|channels' || true
npm view @microsoft/teams.cli dist-tags version --json
rg -n "@microsoft/teams\\.cli@preview|Teams CLI is currently in preview|teams\\.cli@preview" docs/channels/msteams.md || true
git diff --check

Evidence after fix:

channels/msteams.md - Microsoft Teams bot support status, capabilities, and configuration
{
  "dist-tags": {
    "$(npmtag)": "2.0.6-preview.1",
    "next": "2.0.11-preview.8",
    "latest": "3.0.0",
    "preview": "3.0.0-preview.9"
  },
  "version": "3.0.0"
}

The stale-preview rg command produced no matches, and git diff --check produced no output.

Supporting screenshots:

Observed result after fix: No stale @microsoft/teams.cli@preview install command remains, and the docs now show npm install -g @microsoft/teams.cli.

What was not tested: Docs site rendering was not built; this is a docs-only command update.

clawsweeper · 2026-05-29T18:44:16Z

Codex review: needs maintainer review before merge. Reviewed June 29, 2026, 5:18 PM ET / 21:18 UTC.

Summary
The PR updates docs/channels/msteams.md to install @microsoft/teams.cli without @preview and removes the Teams CLI preview warning.

PR surface: Docs -4. Total -4 across 1 file.

Reproducibility: not applicable. as a runtime bug; source inspection shows current main and the latest release still contain the stale preview command, while the PR removes it.

Review metrics: none identified.

Merge readiness
Overall: 🦞 diamond lobster
Proof: 🌊 off-meta tidepool
Patch quality: 🦞 diamond lobster
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Next step before merge

No repair lane is needed; the remaining action is normal maintainer review or merge of the already-focused docs patch.

Security
Cleared: The diff only changes Markdown documentation and does not modify scripts, workflows, dependencies, package resolution, or secrets handling.

Review details

Best possible solution:

Land the focused docs update after normal maintainer review so the public Teams setup page follows the stable Teams CLI install path.

Do we have a high-confidence way to reproduce the issue?

Not applicable as a runtime bug; source inspection shows current main and the latest release still contain the stale preview command, while the PR removes it.

Is this the best way to solve the issue?

Yes. The stale wording is isolated to the Microsoft Teams docs page, and replacing the preview-tag install command with the bare package matches the current npm registry state without touching runtime, config, or plugin behavior.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 15de9d881a84.

Label changes

Label justifications:

P3: This is a low-risk documentation correction to one Microsoft Teams setup command.
rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Real behavior proof is not required because this PR only changes files under docs/.

Evidence reviewed

PR surface:

Docs -4. Total -4 across 1 file.

View PR surface stats

Area	Files	Added	Removed	Net
Source	0	0	0	0
Tests	0	0	0	0
Docs	1	1	5	-4
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	1	1	5	-4

What I checked:

Repository policy read: Root and docs-scoped AGENTS.md were read fully; their docs review, dependency-backed proof, and docs navigation guidance shaped this review. (AGENTS.md:28, 15de9d881a84)
Current main still has stale docs: Current main still tells readers to install @microsoft/teams.cli@preview and still includes the preview warning. Public docs: docs/channels/msteams.md. (docs/channels/msteams.md:40, 15de9d881a84)
PR patch removes stale command: The PR diff changes the install command to npm install -g @microsoft/teams.cli and removes the preview note from the Microsoft Teams docs page. Public docs: docs/channels/msteams.md. (docs/channels/msteams.md:40, 9857c50a8c43)
Latest release still has stale docs: The latest release tag v2026.6.10 still contains the preview-tag install command and preview warning, so this docs correction has not shipped yet. Public docs: docs/channels/msteams.md. (docs/channels/msteams.md:40, aa69b12d0086)
Dependency contract checked: The npm registry currently reports @microsoft/teams.cli latest as 3.0.1 and preview as 3.0.0-preview.9, which supports documenting the bare package install.
Docs navigation checked: The Microsoft Teams page is in the visible Channels navigation, so the command is on a user-facing docs path. Public docs: docs/docs.json. (docs/docs.json:1116, 15de9d881a84)

Likely related people:

heyitsaamir: Authored the merged Teams CLI setup documentation PR that introduced this section and authored this focused follow-up on the same command. (role: introduced related docs behavior; confidence: high; commits: 41da3ecf541d, fc120ff969d4, 969f8bfd9f2f; files: docs/channels/msteams.md)
SidU: Approved and merged the prior Teams CLI setup docs PR that created the affected setup section. (role: reviewer and merger of related docs feature; confidence: medium; commits: 969f8bfd9f2f; files: docs/channels/msteams.md)
Dallin Romney: Current blame for the affected lines points to a recent full-page docs re-add commit that preserved the Teams CLI setup text. (role: recent adjacent contributor; confidence: low; commits: 18f0eeab20e9; files: docs/channels/msteams.md)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Review history (1 earlier review cycle)

reviewed 2026-06-21T05:47:08.000Z sha 9857c50 :: needs maintainer review before merge. :: none

BradGroux · 2026-05-29T18:55:39Z

The docs change itself looks right. The current npm package state supports using the stable install command: @microsoft/teams.cli has latest on 3.0.0, while preview is still a preview tag.

The blocker is the failing Real behavior proof gate. The PR has the required field-style proof under ## Verification, but the checker only reads fields inside a ## Real behavior proof section. The current # Real Behavior Proof section is also level 1 and only contains the npm link/screenshot, so CI treats the proof as missing.

Please reshape the PR body so the required fields live under the real proof section. For this docs-only change, something like this should be enough if it includes actual terminal output or a terminal screenshot from the patched checkout:

## Real behavior proof

Behavior addressed: Microsoft Teams docs no longer tell users to install `@microsoft/teams.cli@preview` now that the stable package is available.
Real environment tested: local OpenClaw docs source checkout.
Exact steps or command run after this patch:

```bash
npm view @microsoft/teams.cli dist-tags version --json
rg -n "@microsoft/teams\\.cli@preview|Teams CLI is currently in preview|teams\\.cli@preview" docs/channels/msteams.md || true
git diff --check
```

Evidence after fix: terminal output or screenshot showing the npm `latest` tag, no remaining deprecated preview command in `docs/channels/msteams.md`, and a clean whitespace check.
Observed result after fix: docs now show `npm install -g @microsoft/teams.cli` and no longer show the preview warning.
What was not tested: docs site rendering was not built.

The npm screenshot is useful supporting evidence, but the gate is asking for after-fix evidence from the patched OpenClaw setup as well.

heyitsaamir · 2026-05-29T19:01:57Z

@BradGroux

Updated and included the screenshot from my terminal.

BradGroux · 2026-05-29T19:04:59Z

Re-reviewed after the update. The terminal screenshot helps, and the docs diff still looks correct.

The remaining blocker is still structural in the PR body, not the patch. The latest Real behavior proof run still fails with:

Real behavior proof is missing required field content: behavior, environment, steps, evidence, observedResult, notTested.

Those fields are still under ## Verification, while the parser only reads them inside ## Real behavior proof. The current proof section has the npm link and screenshots, but not the six required field labels.

No code change is needed. Move or copy the required fields into the proof section, and put the screenshot/link in Evidence after fix, for example:

## Real behavior proof

Behavior addressed: Microsoft Teams docs no longer mention `@microsoft/teams.cli@preview`.
Real environment tested: local docs source checkout.
Exact steps or command run after this patch: `rg -n "@microsoft/teams\\.cli@preview|Teams CLI is currently in preview|teams\\.cli@preview" || true`; `git diff --check`.
Evidence after fix: terminal screenshot showing no deprecated preview install command found and whitespace check passed; npm screenshot showing `latest` is stable `3.0.0`.
Observed result after fix: docs now show `npm install -g @microsoft/teams.cli`.
What was not tested: docs site rendering was not built; this is a one-line docs command update.

Once that is in ## Real behavior proof, the proof gate should have the fields it is currently missing.

heyitsaamir · 2026-05-29T21:51:50Z

@BradGroux good now 👍🏽

openclaw-barnacle · 2026-07-20T04:37:44Z

This pull request has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.

docs: update Teams CLI install command

9857c50

BradGroux mentioned this pull request May 29, 2026

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

Draft

openclaw-barnacle Bot added proof: supplied External PR includes structured after-fix real behavior proof. and removed triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. labels May 29, 2026

clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels May 30, 2026

clawsweeper Bot added the status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. label Jun 15, 2026

openclaw-barnacle Bot added the stale Marked as stale due to inactivity label Jul 20, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Update Teams CLI install command#88103

Update Teams CLI install command#88103
heyitsaamir wants to merge 1 commit into
openclaw:mainfrom
heyitsaamir:chore/teams-cli-ga-docs

heyitsaamir commented May 29, 2026 •

edited by vincentkoc

Loading

Uh oh!

clawsweeper Bot commented May 29, 2026 •

edited

Loading

Uh oh!

BradGroux commented May 29, 2026 •

edited

Loading

Uh oh!

heyitsaamir commented May 29, 2026

Uh oh!

BradGroux commented May 29, 2026

Uh oh!

heyitsaamir commented May 29, 2026

Uh oh!

openclaw-barnacle Bot commented Jul 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

heyitsaamir commented May 29, 2026 • edited by vincentkoc Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Why

Interesting bits

Real behavior proof

Uh oh!

clawsweeper Bot commented May 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

BradGroux commented May 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

heyitsaamir commented May 29, 2026

Uh oh!

BradGroux commented May 29, 2026

Uh oh!

heyitsaamir commented May 29, 2026

Uh oh!

openclaw-barnacle Bot commented Jul 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

heyitsaamir commented May 29, 2026 •

edited by vincentkoc

Loading

clawsweeper Bot commented May 29, 2026 •

edited

Loading

BradGroux commented May 29, 2026 •

edited

Loading