[open-swe] feat: Add Supabase-backed rate limiting to auth middleware #298
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.
Fixes #297
Implements a minimalistic rate limiting system for the Open SWE agent using Supabase as the backend storage.
Key Features:
threads:create
andthreads:create_run
eventsuser.identity
to track request counts in Supabase databaseRATE_LIMIT_EXEMPT_USERS
)Implementation:
.env.example
Database Requirements:
A
rate_limits
table needs to be created in Supabase with columns matching theRateLimitRecord
interface (user_identity, request_count, created_at, updated_at).