Certainly! Here’s a summary you can use to submit a support ticket to Pipedream: — Subject: CLI OAuth Authentication Callback Issue – Unable to Complete Auth Flow Description: Hi Pipedream Support, I’m experiencing an issue with the CLI authentication flow. After authenticating in the browser, I see a message that authentication was successful, but the CLI tool never receives the final callback or token. It seems like the CLI is unable to receive the OAuth callback, possibly due to running in a headless environment or network restrictions. I’ve tried to look for a way to manually provide the token or final URL to the CLI, but I haven’t found clear documentation on the expected format or process. Claude suggested this might be a known limitation with CLI-based OAuth flows, and that a “developer version” or manual setup might be required. Questions: - Is there a way to manually complete the authentication process for the CLI, such as by pasting a token or URL? - What is the expected format of the final URL or token the CLI needs? - Is there an alternative authentication method (e.g., developer setup or API key) recommended for headless or restricted environments? Any guidance or documentation you can provide would be appreciated. Thank you! — If you’d like more help or want to submit this directly, please visit Support - Pipedream.
okey, seems like it was a CC extension issue (when running claude code extension in VS code). got it working when running it natively in terminal. Just FYI
Thank you for the update and for sharing your troubleshooting results! It sounds like the issue was related to the Claude code extension in VS Code, and running the CLI natively in the terminal resolved it. If you run into any more issues or have additional questions, please feel free to ask. If you need further support, you can always visit Support - Pipedream for more help.