PR Custody

PRPR Custody

fix(breezy_hr): expose auth scheme for creation

@AgentWrapperchecks n/achecks…fix/PLEN-2463-breezyhr-auth → master1 files · +0 −1updated 1mo ago

GitHub

▸Description· 1 comment · 1 noise

Summary

Remove is_experimental: true from BreezyHR's only auth scheme so it is visible in normal auth-config creation flows.
This mirrors the GageList class of issue found by the new NO_CREATABLE_AUTH_SCHEME guard: a toolkit with only deprecated/experimental schemes has no creatable auth scheme in the dashboard.

Context

BREEZY is a stale registry entry with 0 tools and no current apps/breezy source folder.
BREEZY_HR is the current Mercury toolkit (apps/breezy_hr) with 48 tools, and its only auth scheme was marked experimental.

Validation

git diff --check

Could not run the requested npm scripts locally because this repository does not define typecheck, lint, or test scripts in package.json. Could not run bun run auth-config/src/configToJson.ts apps/breezy_hr/config.ts locally because the private @composiohq/auth-config package is unavailable in this environment (401 from GitHub Packages during install / module resolution).

Refs PLEN-2463.

@AgentWrapper1mo ago

Testing checklist before merging:

Verify an auth config can be created for BreezyHR on staging.
Verify a BreezyHR connection/login can be created successfully with valid credentials.
Verify at least one BreezyHR tool works after connection creation.

Context:

Staging deploy for this PR: https://github.com/ComposioHQ/mercury/actions/runs/25736232269
Linear tracking ticket: https://linear.app/composio/issue/PLEN-2473/breezy-hr-login-is-broken

▸ 1 bot/status comment hidden

@linear-code[bot]1mo ago

Summary

Creating an auth config for gagelist on staging fails with a generic platform-style error before the auth-config form is rendered:

Organization Error There was an issue accessing this organization. You might not have access or the organization might be temporarily unavailable.

Go Back Home

Retry

The error message is misleading — it's worded like a platform/org-access failure, but it only reproduces for the gagelist toolkit. Other apps load their auth-config forms normally on the same staging environment.

Reproduction

Log into staging dashboard.
Pick gagelist as the toolkit and try to create a new auth config.
Observe the "Organization Error" screen instead of the auth-config form.

Other apps on the same session work fine — confirmed.

Scope

Gagelist-specific. Does not reproduce for unrelated toolkits.
Reproduces on at least two accounts (Prateek + Manas), so it's not session- or user-specific.

Investigation starter checklist

Reproduce in browser dev tools — Network tab → identify the failing request when you select gagelist. Capture status code + response body. The endpoint that returns the failure tells you which service is unhappy.
Check Hermes / Apollo staging logs for errors mentioning gagelist or the gagelist unique_key around the time the error appears.
File a secondary bug on the error UX — the "Organization Error" screen is a misleading catch-all that hides the real failure for a per-toolkit load problem. Even if this specific case is resolved, the next toolkit-shaped issue will present with the same opaque message.

Severity

High. Blocks staging validation for the gagelist toolkit.

loading diff…

@linear-code[bot]1mo ago

Summary

Creating an auth config for gagelist on staging fails with a generic platform-style error before the auth-config form is rendered:

Organization Error There was an issue accessing this organization. You might not have access or the organization might be temporarily unavailable.

Go Back Home

Retry

Reproduction

Log into staging dashboard.
Pick gagelist as the toolkit and try to create a new auth config.
Observe the "Organization Error" screen instead of the auth-config form.

Other apps on the same session work fine — confirmed.

Scope

Gagelist-specific. Does not reproduce for unrelated toolkits.
Reproduces on at least two accounts (Prateek + Manas), so it's not session- or user-specific.

Investigation starter checklist

Reproduce in browser dev tools — Network tab → identify the failing request when you select gagelist. Capture status code + response body. The endpoint that returns the failure tells you which service is unhappy.
Check Hermes / Apollo staging logs for errors mentioning gagelist or the gagelist unique_key around the time the error appears.
File a secondary bug on the error UX — the "Organization Error" screen is a misleading catch-all that hides the real failure for a per-toolkit load problem. Even if this specific case is resolved, the next toolkit-shaped issue will present with the same opaque message.

Severity

High. Blocks staging validation for the gagelist toolkit.