For engineers
Review the risky change first, with the code beside you.
Stett puts the critical changes first and brings the code, the thread and the answers into the review, so you unblock your teammates sooner. In every Team seat, and free on your own repositories.
Guided review
Review what's critical first.
Risk first, in steps, with answers beside the code. Reviews take less time and miss less.
- Closes six permission escalation holes in v2 API endpoints where credentials could reach beyond their granted scopes.
- Search now requires appropriate scopes for private content types, MCP tools that spend platform resources require
USE_TOOLS, and credential deletion blocks platform-managed ones. - Auth caching prevents repeated hash verification, and comprehensive tests pin each fix in place.
Modifies auth middleware to prevent double verification and fix rate limiting.
1.Auth Caching Infrastructure
3/32.Search Content Type Permissions
1/2Mark 2 files reviewedapi/v2/search.pyRisk 8tests/test_search_scopes.pyRisk 33.MCP Tool Permission Requirements
2 files4.Credential Deletion Protection
1 file5.Invoice Sharing Permission Alignment
2 files- and 4 more steps
Ask
Ask about any code. Get an answer that cites its source.
Answers from the repository and the pull request, with the file and line they came from.
Chats are saved for 90 days and are yours alone. Delete a thread any time. Answers count toward your org's daily AI operations.
- Closes six permission escalation holes in v2 API endpoints where credentials could reach beyond their granted scopes.
- Search now requires appropriate scopes for private content types, MCP tools that spend platform resources require
USE_TOOLS, and credential deletion blocks platform-managed ones. - Auth caching prevents repeated hash verification, and comprehensive tests pin each fix in place.
Modifies auth middleware to prevent double verification and fix rate limiting.
Two commits since your approval on Oct 9, both in the auth group.
backend/api/external/middleware.py:4 swaps the Starlette Request import for Scope, so the middleware runs for WebSocket routes too. tests/test_permissions.py:88 adds the case. Nothing touched the schema or the docs.
Read the diff of 2 files and the timeline. Not a review: submit one from the top bar.
One. On middleware.py:4 a reviewer asked whether Scope also covers WebSocket auth. The author pointed at the new test but did not resolve the thread.
Read 1 thread.
Earlier chats
How does the rate limit apply to MCP tools · Yesterday
Where is the API key hashed · Oct 8
31 of 40 answers left today
Code
Read the code behind a review without cloning it.
Every repository gets an Overview and a Code tab. Jump from a diff to the whole file, pinned to the commit you are reviewing.
feat(web): usage page with invoice history #4812
sam-ortizopened 2 hours ago23 files +1,284 -969 commentsAll 7 checks passed
jholliscommented 8m ago
frontend/src/app/settings/usage/UsageChart.tsx:54
@simple-ai/web the chart refetches usage on every hover. Can you check the query key before this merges?
The invoice table looks good to me. One nit on the date filter below.
Inbox
Know what waits on you, and why.
Pull requests, issues and discussions in one inbox. Clear what's done in a click and bookmark what you will come back to.
Issues and discussions
Read the paragraph, not the thread.
Each issue and discussion opens with a short briefing: the problem, where it stands and what blocks it.
Quick win
ci: canary publish job fails after enabling npm provenance
No labels or owner · Needs triage
High priority
verifyWebhook() fails behind proxies that re-encode the body
Bug report, 26 reactions · Triage
Jump back in
Retries resend POST requests without the idempotency key
27 comments so far · pick up the thread