feat(msteams): add federated credential support (certificate + managed identity) by HDYA · Pull Request #53615 · openclaw/openclaw

HDYA · 2026-03-24T10:23:05Z

Add alternative authentication methods for Microsoft Teams beyond client secrets. Users can now authenticate using:

Certificate-based auth (PEM file via ClientCertificateCredential)
Azure Managed Identity (system- or user-assigned via ManagedIdentityCredential)

Changes:

MSTeamsCredentials is now a discriminated union with type: "secret" | "federated"
createMSTeamsApp dispatches by credential type:
- secret: clientId + clientSecret (existing behavior, fully backward compatible)
- certificate: reads PEM, uses ClientCertificateCredential from @azure/identity with a custom token callback
- managed identity: uses ManagedIdentityCredential from @azure/identity with a custom token callback
MSTeamsConfig type gains 5 new optional fields: authType, certificatePath, certificateThumbprint, useManagedIdentity, managedIdentityClientId
Zod schema updated with new optional fields (runtime credential resolver handles cross-field validation)
5 new env vars: MSTEAMS_AUTH_TYPE, MSTEAMS_CERTIFICATE_PATH, MSTEAMS_CERTIFICATE_THUMBPRINT, MSTEAMS_USE_MANAGED_IDENTITY, MSTEAMS_MANAGED_IDENTITY_CLIENT_ID
Tests updated for all auth paths (25 total: 18 token + 7 sdk)
@azure/identity added as dependency (dynamically imported at runtime for federated auth flows only)
Also bumps @microsoft/teams.apps and @microsoft/teams.api to 2.0.6

Summary

Problem: MS Teams bot integration only supports client secret authentication, which is unsuitable for production environments requiring certificate-based or managed identity auth (e.g., AKS workload identity).
Why it matters: Enterprise deployments need passwordless auth. Azure recommends managed identity or certificate over client secrets for service-to-service auth.
What changed: MSTeamsCredentials is now a discriminated union (secret | federated). New createFederatedApp, createCertificateApp, and createManagedIdentityApp factory functions dispatch based on credential type. Credential instances are lazily created and cached for token reuse. Zod schema extended with optional fields.
What did NOT change: Existing appId + appPassword + tenantId secret-based auth path is untouched. Default behavior (no authType configured) resolves to "secret" — fully backward compatible.

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Related chore(msteams): bump @microsoft/teams.apps&api from 2.0.5 to 2.0.6 #54424 (teams.apps 2.0.6 bump — independent PR)
This PR fixes a bug or regression

Root Cause / Regression History (if applicable)

N/A — this is a new feature, not a bug fix.

Regression Test Plan (if applicable)

Coverage level:
- Unit test
- Seam / integration test
- End-to-end test
- Existing coverage already sufficient
Target test files: extensions/msteams/src/sdk.test.ts, extensions/msteams/src/token.test.ts
Scenarios locked in:
- Secret credentials pass clientId/clientSecret/tenantId to SDK (backward compat)
- Certificate credentials read PEM file and use ClientCertificateCredential for token acquisition
- Managed identity credentials use ManagedIdentityCredential with lazy caching
- System-assigned and user-assigned MI both covered
- Token acquisition failure throws descriptive error
- Missing certificatePath + no managedIdentity throws
- Env var resolution for all new fields
- Discriminated union type resolution (secret vs federated)
- Config useManagedIdentity: false overrides env MSTEAMS_USE_MANAGED_IDENTITY=true
Why this is the smallest reliable guardrail: Unit tests cover each code path through the credential factory without requiring Azure infrastructure
25 tests total (18 token + 7 sdk), all passing

User-visible / Behavior Changes

New optional config fields: authType, certificatePath, certificateThumbprint, useManagedIdentity, managedIdentityClientId
New env vars: MSTEAMS_AUTH_TYPE, MSTEAMS_CERTIFICATE_PATH, MSTEAMS_CERTIFICATE_THUMBPRINT, MSTEAMS_USE_MANAGED_IDENTITY, MSTEAMS_MANAGED_IDENTITY_CLIENT_ID
Default behavior unchanged — existing appId + appPassword configs continue working without modification

Security Impact (required)

New permissions/capabilities? Yes — adds managed identity and certificate auth paths
Secrets/tokens handling changed? Yes — new token acquisition via @azure/identity (ManagedIdentityCredential for MI, ClientCertificateCredential for certs)
New/changed network calls? Yes — managed identity flow calls Azure IMDS (169.254.169.254) and AAD token endpoint
Command/tool execution surface changed? No
Data access scope changed? No
Risk + mitigation: Certificate private key is read from a file path (not embedded in config). Managed identity tokens are scoped per SDK request. @azure/identity handles token caching and refresh. No secrets are logged.

Repro + Verification

Environment

OS: Linux (container on AKS)
Runtime: Node.js
Integration/channel: Microsoft Teams
Relevant config: authType: "federated", useManagedIdentity: true with AKS workload identity

Steps

Configure msteams with authType: "federated" and useManagedIdentity: true
Ensure pod service account has federated identity credential linked to Entra app
Send message to bot in Teams

Expected

Bot authenticates via managed identity token and responds

Actual

Pending E2E verification in a pod running on AKS with federated credential

Evidence

Failing test/log before + passing after
All 357 msteams tests pass after rebase with main
25 new tests specifically covering federated auth paths

Human Verification (required)

Verified scenarios: All unit tests pass for secret, certificate, and managed identity auth paths
Edge cases checked: Missing cert path, system vs user-assigned MI, token acquisition failure, useManagedIdentity: false overriding env var
What was not verified: Full E2E flow in a pod running on AKS with federated credential (planned as follow-up)

Review Conversations

I replied to or resolved every bot review conversation I addressed in this PR.
I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

Backward compatible? Yes — resolveAuthType() defaults to "secret" when not configured
Config/env changes? Yes — 5 new optional config fields, 5 new env vars (all optional)
Migration needed? No — existing configurations work without changes

Failure Recovery (if this breaks)

How to disable/revert: Remove authType from config (defaults back to secret auth)
Files/config to restore: Only msteams config section
Known bad symptoms: "Failed to acquire token" error in logs if managed identity is misconfigured

Risks and Mitigations

Risk: @azure/identity adds transitive dependencies to the package
- Mitigation: Only imported dynamically at runtime when federated auth is actually configured; does not affect secret-based deployments
Risk: Managed identity requires correct Azure infrastructure (federated credential, OIDC issuer)
- Mitigation: Descriptive error messages when token acquisition fails; documented setup requirements

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c3c8dfa94a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

greptile-apps · 2026-03-25T11:44:17Z

Greptile Summary

This PR adds certificate and Azure Managed Identity authentication paths to the MS Teams integration by refactoring MSTeamsCredentials into a discriminated union ("secret" | "federated") and introducing corresponding factory functions. The config type, Zod schema, token.ts, and tests are all well-structured, and the default "secret" path is fully backward-compatible.

Key findings:

P1 — Managed identity token cache bypassed: createManagedIdentityApp allocates a new ManagedIdentityCredential / DefaultAzureCredential instance on every invocation of tokenProvider. Each @azure/identity credential object maintains its own in-memory token cache; recreating the instance on every call discards the cache and triggers a fresh Azure IMDS or AAD token request per Teams message. Under load this will hit IMDS rate limits. The credential should be created once and captured in the closure.
P2 — readFileSync error lacks context: Missing/unreadable certificate files surface as raw ENOENT/EACCES errors. A wrapping try/catch with a descriptive message would significantly improve operator experience.
P2 — createMSTeamsAdapter test coverage dropped: The previous test verifying deleteActivity via continueConversation proactive sends was removed and not replaced. createSendContext (used by continueConversation) still wires up deleteActivity via REST, but this path now has no unit test coverage.

Confidence Score: 3/5

Safe to merge for secret-auth users; the managed identity path has a token-caching bug that will cause IMDS rate-limit pressure under production load.
The discriminated union refactor, Zod validation, config types, and token.ts logic are all solid. The managed identity credential-recreation issue (P1) is a genuine production reliability concern for the new auth path — every message that requires a token refresh will make a fresh IMDS call rather than reusing a cached token. The fix is small (hoist credential construction outside tokenProvider). The P2 items (readFileSync error handling, adapter test gap) are non-blocking but worth addressing.
extensions/msteams/src/sdk.ts — specifically createManagedIdentityApp (lines 97–122)

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/msteams/src/sdk.test.ts
Line: 141

Comment:
**`createMSTeamsAdapter` + `continueConversation` test coverage dropped**

The previous `sdk.test.ts` contained a test titled `"provides deleteActivity in proactive continueConversation contexts"` that verified an HTTP `DELETE` was issued via `ctx.deleteActivity` inside the `logic` callback. That test — and the whole import of `createMSTeamsAdapter` — was removed in this PR and not replaced.

`createSendContext` (used by `continueConversation`) still wires up `deleteActivity` via `deleteActivityViaRest`, so the production code path still exists. A coverage gap now exists for the `continueConversation` proactive messaging flow. Consider adding at minimum one test that exercises `createMSTeamsAdapter.continueConversation` and verifies `sendActivity` / `deleteActivity` behavior against a `fetch` mock.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/msteams/src/sdk.ts
Line: 101-115

Comment:
**Credential instance recreated on every token call — token cache never reused**

`tokenProvider` creates a brand-new `ManagedIdentityCredential` / `DefaultAzureCredential` instance on every invocation. Each `@azure/identity` credential object maintains its own in-memory token cache; constructing a fresh instance discards that cache, so every call to `tokenProvider` issues a new outbound token request to Azure IMDS or AAD — even when the previous token is still valid.

Under realistic load (one Teams message → one `tokenProvider` call), this results in a new IMDS/AAD round-trip per message. IMDS is rate-limited, and `DefaultAzureCredential` probes multiple credential sources in sequence on each construction, making the overhead significant.

The credential should be created once (lazily, to keep the dynamic import on-demand) and captured in the closure — a module-level promise variable initialised on first call is the standard pattern for this in `@azure/identity` users. Something like:

```typescript
let credentialPromise: Promise<ManagedIdentityCredential | DefaultAzureCredential> | null = null;

const getCredential = async () => {
  if (!credentialPromise) {
    credentialPromise = import("@azure/identity").then((az) =>
      creds.managedIdentityClientId
        ? new az.ManagedIdentityCredential(creds.managedIdentityClientId)
        : new az.DefaultAzureCredential(),
    );
  }
  return credentialPromise;
};

const tokenProvider = async (): Promise<string> => {
  const credential = await getCredential();
  const token = await credential.getToken(BOT_FRAMEWORK_SCOPE);
  if (!token?.token) throw new Error("Failed to acquire token via managed identity.");
  return token.token;
};
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/msteams/src/sdk.ts
Line: 85

Comment:
**Unguarded `readFileSync` surfaces raw filesystem errors**

If `creds.certificatePath` points to a missing or unreadable file, Node.js throws a raw `ENOENT`/`EACCES` error with no context about certificate-based auth. Wrapping the call in a try/catch and re-throwing with a descriptive message (e.g. `"Failed to read certificate file at '${creds.certificatePath}': ${err.message}"`) would produce a much clearer diagnostic for operators configuring this for the first time.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Merge origin/main into hdya/teams-authen..." | Re-trigger Greptile}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5a763a2493

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7faecd5659

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3f09bf808b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7e16c60c86

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

HDYA · 2026-03-25T16:58:23Z

it appears that the MAC OS check error is from main branch

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3ccbc9d5e9

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f9cd5eafdd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 718220abb3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 802ea3e9ee

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

feiskyer · 2026-04-11T12:45:08Z

Looks great. The discriminated union for credentials is a solid choice, and I like that existing secret auth stays completely untouched as the default. Certificate and managed identity paths give us proper passwordless auth for production, which is a big step up from rotating client secrets.

@HDYA needs rebase due to conflicts.

…naged identity + workload identity)

…baseline

… Swift

# Conflicts: # src/canvas-host/a2ui/.bundle.hash

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9e93980d83

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-04-11T18:36:50Z

+  const activeRegistry = state?.activeRegistry ?? null;
+  if (countChannels(activeRegistry) > 0) {
+    return activeRegistry;
+  }
+  return pinnedRegistry ?? activeRegistry;


Keep channel registry version in sync with fallback registry

This function can now return activeRegistry when the pinned channel registry is empty, but getActivePluginChannelRegistryVersionFromState() still reports the pinned channel.version whenever channel.registry exists. That creates a registry/version mismatch and can leave version-keyed caches stale (for example getChatCommands() and getNativeCommandSurfaces() in src/auto-reply/commands-registry.data.ts) after active channel plugins change under a pinned-empty channel surface.

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-04-11T18:36:50Z

    id: "discord-rest",
    label: "Discord REST monitor fetch",
-    modulePath: "extensions/discord/src/monitor/rest-fetch.ts",
+    modulePath: "extensions/discord/monitor/rest-fetch.ts",


Restore valid source paths in debug proxy coverage entries

These modulePath values were changed to paths that do not exist in the repo (for example dropping /src/), so openclaw proxy coverage now emits broken source references for multiple seams (discord-rest, discord-gateway, telegram-fetch, mattermost-ws, and feishu-client-*). This regresses the report’s ability to point maintainers to the actual implementation files.

Useful? React with 👍 / 👎.

…d identity) (openclaw#53615) * feat(msteams): add federated authentication support (certificate + managed identity + workload identity) * msteams: fix vitest 4.1.2 compat, type errors, and regenerate config baseline * msteams: fix lint errors, update fetch allowlist, regenerate protocol Swift * fix(msteams): gate secret-only delegated auth flows * fix(ci): unblock gateway watch and install smoke * fix(ci): restore mergeability for pr 53615 * fix(ci): restore channel registry helper typing * fix(ci): refresh raw fetch guard allowlist --------- Co-authored-by: Chudi Huang <Chudi.Huang@microsoft.com> Co-authored-by: Brad Groux <3053586+BradGroux@users.noreply.github.com>

openclaw-barnacle Bot added channel: msteams Channel integration: msteams size: L docs Improvements or additions to documentation labels Mar 24, 2026

HDYA marked this pull request as ready for review March 25, 2026 11:39

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread src/config/zod-schema.providers-core.ts Outdated

Comment thread extensions/msteams/src/token.ts Outdated

greptile-apps Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.test.ts

Comment thread extensions/msteams/src/sdk.ts Outdated

Comment thread extensions/msteams/src/sdk.ts Outdated

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.ts Outdated

Comment thread extensions/msteams/src/sdk.ts Outdated

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.ts Outdated

HDYA force-pushed the hdya/teams-authentications branch from 7faecd5 to 3f09bf8 Compare March 25, 2026 12:37

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.ts

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.ts Outdated

HDYA force-pushed the hdya/teams-authentications branch from 7e16c60 to dbb0fb2 Compare March 25, 2026 13:59

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.ts

HDYA force-pushed the hdya/teams-authentications branch from 3ccbc9d to f9cd5ea Compare March 25, 2026 17:20

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.ts Outdated

HDYA force-pushed the hdya/teams-authentications branch from f9cd5ea to 718220a Compare March 25, 2026 17:37

chatgpt-codex-connector Bot reviewed Mar 25, 2026

View reviewed changes

Comment thread extensions/msteams/src/token.ts

BradGroux mentioned this pull request Mar 26, 2026

WORKING: All Microsoft Issues and PRs #49126

Closed

HDYA force-pushed the hdya/teams-authentications branch from 75e9857 to 1ee45b1 Compare March 26, 2026 04:29

HDYA mentioned this pull request Mar 26, 2026

[Feature]: Federated credential support for Microsoft Teams (certificate + managed identity) #54903

Closed

HDYA force-pushed the hdya/teams-authentications branch from 1ee45b1 to 06716e6 Compare March 26, 2026 11:45

Copilot AI mentioned this pull request Mar 27, 2026

List Azure and Windows open PRs available for review johnsonshi/openclaw#1

Closed

17 tasks

HDYA force-pushed the hdya/teams-authentications branch from 06716e6 to 802ea3e Compare March 27, 2026 14:18

openclaw-barnacle Bot removed the docs Improvements or additions to documentation label Mar 27, 2026

chatgpt-codex-connector Bot reviewed Mar 27, 2026

View reviewed changes

Comment thread extensions/msteams/src/sdk.ts Outdated

HDYA force-pushed the hdya/teams-authentications branch from 802ea3e to 25279e4 Compare March 27, 2026 14:57

openclaw-barnacle Bot added the docs Improvements or additions to documentation label Mar 27, 2026

HDYA force-pushed the hdya/teams-authentications branch from 25279e4 to 698f758 Compare March 27, 2026 17:43

Chudi Huang added 3 commits April 11, 2026 13:26

feat(msteams): add federated authentication support (certificate + ma…

667b459

…naged identity + workload identity)

msteams: fix vitest 4.1.2 compat, type errors, and regenerate config …

40edb0b

…baseline

msteams: fix lint errors, update fetch allowlist, regenerate protocol…

b444b94

… Swift

HDYA force-pushed the hdya/teams-authentications branch from b82f81e to b444b94 Compare April 11, 2026 13:27

openclaw-barnacle Bot removed the app: macos App: macos label Apr 11, 2026

BradGroux added 3 commits April 11, 2026 08:58

fix(msteams): gate secret-only delegated auth flows

00f63ad

fix(ci): unblock gateway watch and install smoke

60e1a35

Merge remote-tracking branch 'origin/main' into codex/53615

5a66990

# Conflicts: # src/canvas-host/a2ui/.bundle.hash

openclaw-barnacle Bot added channel: discord Channel integration: discord channel: mattermost Channel integration: mattermost channel: telegram Channel integration: telegram agents Agent runtime and tooling extensions: openai extensions: qa-lab size: XL and removed size: L labels Apr 11, 2026

BradGroux added 4 commits April 11, 2026 13:13

fix(ci): restore mergeability for pr 53615

8ca6c11

fix(ci): restore channel registry helper typing

fbd2d3c

Merge remote-tracking branch 'origin/main' into codex/53615

058d10b

fix(ci): refresh raw fetch guard allowlist

9e93980

BradGroux merged commit 26f633b into openclaw:main Apr 11, 2026
6 checks passed

github-actions Bot mentioned this pull request Apr 11, 2026

📡 Upstream Digest — 2026-04-11 18:32 UTC curtismercier/openclaw-mods#541

Open

chatgpt-codex-connector Bot reviewed Apr 11, 2026

View reviewed changes

HDYA mentioned this pull request Apr 15, 2026

docs(msteams): fix federated auth added-in date to 2026.4.11 #67111

Merged

Uh oh!

Conversation

HDYA commented Mar 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

Root Cause / Regression History (if applicable)

Regression Test Plan (if applicable)

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Review Conversations

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

greptile-apps Bot commented Mar 25, 2026

Greptile Summary

Confidence Score: 3/5

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

HDYA commented Mar 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

HDYA commented Mar 24, 2026 •

edited

Loading

HDYA commented Mar 25, 2026 •

edited

Loading