You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built a Sentry gatekeeper for Cloudflare OS and I'd like to gauge whether there's appetite for it upstream — or whether it's a useful test case for the "gatekeepers maintained independently from OS instances" future the README mentions.
What it unlocks: "What's crashing in prod, and why?" becomes a chat question. Agents search issues, read stack traces, and queue triage (resolve / archive / assign) that users batch-approve later — issue triage is almost the ideal fit for the async-approval + simulation model: high volume, low individual stakes, tedious for humans, fully revertible.
Why it's low-friction: it's token-based (instance URL + user auth token, works for SaaS and self-hosted), so unlike most gatekeepers there's no OAuth app for deployment admins to provision. Two granularities: whole org, or a single project.
Working implementation (built with your write-gatekeeper skill, follows the linear/homeassistant patterns, lint/build/tests/golden green): sergical#1.
(Disclosure: I work at Sentry on the DevEx team, some of this text was ai generated)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I built a Sentry gatekeeper for Cloudflare OS and I'd like to gauge whether there's appetite for it upstream — or whether it's a useful test case for the "gatekeepers maintained independently from OS instances" future the README mentions.
What it unlocks: "What's crashing in prod, and why?" becomes a chat question. Agents search issues, read stack traces, and queue triage (resolve / archive / assign) that users batch-approve later — issue triage is almost the ideal fit for the async-approval + simulation model: high volume, low individual stakes, tedious for humans, fully revertible.
Why it's low-friction: it's token-based (instance URL + user auth token, works for SaaS and self-hosted), so unlike most gatekeepers there's no OAuth app for deployment admins to provision. Two granularities: whole org, or a single project.
Working implementation (built with your
write-gatekeeperskill, follows the linear/homeassistant patterns, lint/build/tests/golden green): sergical#1.(Disclosure: I work at Sentry on the DevEx team, some of this text was ai generated)
All reactions