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
OpenShell needs a supported way for operators and external integrators to customize gateway behavior without forking the gateway or adding organization-specific logic to compute drivers.
Examples include enforcing naming conventions, limiting sandbox creation per user, rejecting custom sandbox policies in managed deployments, constraining driver config payloads, and verifying policy writes against external authorities before accepting them.
Today these controls would need to be hardcoded into gateway handlers or pushed into drivers, which mixes responsibilities and makes deployment-specific policy difficult to maintain.
Proposed Design
We will put together RFC 0010 for Gateway Interceptors.
The RFC should explore operation interceptors for gateway API workflows. Interceptors add business logic around gateway operations while drivers remain responsible for replacing or providing platform functionality. The gateway database should remain the system of record; external systems should reconcile desired state through existing OpenShell APIs rather than participating in live gateway lookup paths.
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.
Activity
[-]feat: add gateway hook extension points[/-][+]feat: add gateway interceptors[/+]github-actions commentedon Jul 8, 2026
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.