Reproduced on prod with 0.2.37 (2026-09-17): after a successful polylane auth login, polylane cloud connect --provider triggerdev --api-key <tr_prod_sk_…> answers Error: Not signed in. Hint: Run polylane auth login.
Cause: src/auth/resolver.ts treats a bare --api-key anywhere in process.argv as the global Polylane API-key flag (precedence flag > POLYLANE_API_KEY > credentials file), so the provider key handed to cloud connect --api-key (Trigger.dev environment key from #101, Render API key before it) is used as the Polylane credential and rejected. Render's connect by key has the same defect.
Fix in progress: the resolver must not consume --api-key as Polylane auth when the invoked command declares its own --api-key option; the user-facing flag keeps its name for now.
Reproduced on prod with 0.2.37 (2026-09-17): after a successful
polylane auth login,polylane cloud connect --provider triggerdev --api-key <tr_prod_sk_…>answersError: Not signed in. Hint: Run polylane auth login.Cause:
src/auth/resolver.tstreats a bare--api-keyanywhere inprocess.argvas the global Polylane API-key flag (precedence flag >POLYLANE_API_KEY> credentials file), so the provider key handed tocloud connect --api-key(Trigger.dev environment key from #101, Render API key before it) is used as the Polylane credential and rejected. Render's connect by key has the same defect.Fix in progress: the resolver must not consume
--api-keyas Polylane auth when the invoked command declares its own--api-keyoption; the user-facing flag keeps its name for now.