fix: generalize webhook tunnel guidance - #465
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The webhook quickstart currently names and installs ngrok throughout its examples. That vendor-specific guidance caused an agent-readiness scanner to interpret a third-party CLI as an official Magic Hour CLI, while also coupling webhook setup to one tunneling provider.
This makes the instructions provider-neutral while preserving the actual requirement: forward a public HTTPS URL to port 8000 and register its /webhook path. Notebook guidance and troubleshooting now follow the same generic flow, with webhook.site retained for quick testing.