Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
|
c'mon mintlify |
|
@mintlify deploy |
|
=/ |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| <Info> | ||
| If you're running with `dangerouslyDisableDeviceAuth` it should work now! | ||
| If device pairing is required, open the URL in your browser. With the insecure Control UI settings above, device pairing is disabled. | ||
| </Info> |
There was a problem hiding this comment.
I would change:
- Info -> warning callout. Just about color https://www.mintlify.com/docs/components/callouts
- Put the callout before the codegroup. I feel like we mostly have it that way, but I could be wrong.
There was a problem hiding this comment.
taking a look at the color - this is before the codegroup to run if the warning applies though so not sure it would make sense above the first one
There was a problem hiding this comment.
Okay, good point, and we apparently have this in the docs in many places, just checked. Let's keep it.
There was a problem hiding this comment.
moved that guy to the bottom to be with the instructions for turning on the pairing requirement so 2 birds 1 stone
|
Do you know why this doesn't load? |
beran-t
left a comment
beran-t
left a comment
There was a problem hiding this comment.
Nothing else to add, lgtm. Let's 🚢 it and add more things later if needed, or based on feedback.
mintlify issue im guessing, works for me on the preview site |
|
issue with the icon once deployed to prod |
2 participants
add ezdeploy guides for openclaw - not quite as ezdeploy as they should be
openclaw-gateway: deploys openclaw to a e2b sandbox, disables device pairing for the gateway to get started immediatelyopenclaw-telegram: deploys openclaw to a e2b sandbox, pairs a telegram bot to the accountwill be adding more guides as go thru
Note
Low Risk
Documentation-only changes; no runtime code paths are modified. The main risk is users copying insecure gateway flags from the examples without later re-enabling device auth.
Overview
Adds an OpenClaw section to the
Agents in sandboxdocs navigation, linking to two new guides.Introduces
openclaw-gatewayandopenclaw-telegramMDX pages with end-to-end E2B sandbox recipes (JS/Python) for starting the OpenClaw gateway with token auth, optionally handling device pairing/approvals, and configuring Telegram channel setup including pairing approval and basic troubleshooting.Written by Cursor Bugbot for commit e3f9e4c. This will update automatically on new commits. Configure here.