Cache OpenCode usage sessions - #18
Conversation
🤖 CodeAnt AI — Review Status
|
Thanks for using CodeAnt! 🎉We're free for open-source projects. if you're enjoying it, help us grow by sharing. Share on X · |
|
Warning Review limit reached
Next review available in: 30 seconds You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
codeant-ai
Bot
added
the
size:L
![codeant-ai[bot]](https://avatars.githubusercontent.com/in/646884?s=60&v=4){kind=small}
| @@ -136,7 +136,8 @@ func chromiumSession(product chromiumProduct, profile string, database string, n | |||
| scan.invalidCookies++ | |||
| continue | |||
| } | |||
| if chromeCookieExpired(fields[3], now) { | |||
| expiresAt, persistent := chromeCookieExpiresAt(fields[3]) | |||
| if persistent && !expiresAt.After(now) { | |||
| scan.expiredCookies++ | |||
| continue | |||
| } | |||
| @@ -154,7 +155,7 @@ func chromiumSession(product chromiumProduct, profile string, database string, n | |||
| scan.invalidCookies++ | |||
| continue | |||
| } | |||
| cookies[fields[0]] = value | |||
| cookies[fields[0]] = browserCookie{name: fields[0], value: value, expiresAt: expiresAt} | |||
There was a problem hiding this comment.
Suggestion: Cookies are keyed only by name, so rows for the host-only and domain cookies (or multiple cookies during rotation) overwrite one another. Because the SQL query has no ordering, the selected value is nondeterministic and may be the invalid or stale credential even when another valid cookie exists. Preserve the relevant cookie variants or choose the valid cookie deterministically before constructing the request. [logic error]
Severity Level: Major ⚠️
- ❌ OpenCode usage retrieval can select an invalid cookie.
- ⚠️ Users may see login failures despite valid browser sessions.
Prompt for AI Agent 🤖
This is a comment left during a code review.
**Path:** internal/opencodego/session_darwin.go
**Line:** 129:158
**Comment:**
*Logic Error: Cookies are keyed only by name, so rows for the host-only and domain cookies (or multiple cookies during rotation) overwrite one another. Because the SQL query has no ordering, the selected value is nondeterministic and may be the invalid or stale credential even when another valid cookie exists. Preserve the relevant cookie variants or choose the valid cookie deterministically before constructing the request.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix| sessionRejected := false | ||
| for _, session := range sessions { | ||
| body, err := fetchPage(ctx, client, baseURL+"/zen", session) | ||
| if err != nil { | ||
| if errors.Is(err, errOpenCodeSessionRejected) { | ||
| sessionRejected = true | ||
| } |
There was a problem hiding this comment.
Suggestion: The rejection flag is updated only for /zen requests, while workspace /go requests can also return the newly classified errOpenCodeSessionRejected. If /zen succeeds but /go returns 401 or 403, this function returns a nil top-level error with an account-level usage error, so Fetch treats the cached session as successful and does not rescan browsers. Track session rejection during workspace requests and return errOpenCodeSessionInvalid when the cached login is rejected. [api mismatch]
Severity Level: Major ⚠️
- ❌ OpenCode usage displays unavailable account data.
- ⚠️ Rejected sessions remain cached instead of refreshing.
- ⚠️ Browser rescanning is skipped on subsequent usage commands.
Prompt for AI Agent 🤖
This is a comment left during a code review.
**Path:** internal/opencodego/usage.go
**Line:** 97:103
**Comment:**
*Api Mismatch: The rejection flag is updated only for `/zen` requests, while workspace `/go` requests can also return the newly classified `errOpenCodeSessionRejected`. If `/zen` succeeds but `/go` returns 401 or 403, this function returns a nil top-level error with an account-level usage error, so `Fetch` treats the cached session as successful and does not rescan browsers. Track session rejection during workspace requests and return `errOpenCodeSessionInvalid` when the cached login is rejected.
Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix1 participant
User description
Changes
Testing
go test -mod=vendor -race ./...go vet -mod=vendor ./...Notes
${XDG_CACHE_HOME:-$HOME/.cache}/prism/opencode-go/sessions.jsonCodeAnt-AI Description
Reuse valid OpenCode sessions and refresh them when authentication expires
What Changed
Impact
✅ Faster OpenCode usage checks✅ Fewer browser scans✅ Automatic recovery from expired logins💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.