Skip to content

update agy desktop and agy cli items - #15

Merged
barramee27 merged 3 commits into
barramee27:feat/linux-windows-native-supportfrom
idkwhodatis:feat/linux-windows-native-support
Jul 19, 2026
Merged

update agy desktop and agy cli items#15
barramee27 merged 3 commits into
barramee27:feat/linux-windows-native-supportfrom
idkwhodatis:feat/linux-windows-native-support

Conversation

@idkwhodatis

Copy link
Copy Markdown

Description

fix agy desktop and agy cli token retrieval on windows
update agy endpoint
update usage display items

Related Issue

Type of Change

  • Bug fix
  • New feature
  • New provider plugin
  • Documentation
  • Performance improvement
  • Other (describe below)

Testing

  • I ran bun run build and it succeeded
  • I ran bun run test and all tests pass
  • I tested the change locally with bun tauri dev

Screenshots

image

Checklist

  • I read CONTRIBUTING.md
  • My PR targets the main branch
  • I did not introduce new dependencies without justification

@barramee27

Copy link
Copy Markdown
Owner

Looks good, merging. One follow-up: renaming lines from Gemini Pro/Flash/Claude → Session/Weekly/… may break existing trayLines / Modern pins for people who customized them. A small migration mapping old → new labels would help. Not blocking.

@idkwhodatis

Copy link
Copy Markdown
Author

Looks good, merging. One follow-up: renaming lines from Gemini Pro/Flash/Claude → Session/Weekly/… may break existing trayLines / Modern pins for people who customized them. A small migration mapping old → new labels would help. Not blocking.

Thanks for reviewing, yea just fyi gemini pro/flash/claude is the legacy usage display, and it's been replaced with session/weekly.
I'll try to add the migration thing, and I might also update the color for agy to blue for better consistency.

@barramee27

Copy link
Copy Markdown
Owner

Looks good, merging. One follow-up: renaming lines from Gemini Pro/Flash/Claude → Session/Weekly/… may break existing trayLines / Modern pins for people who customized them. A small migration mapping old → new labels would help. Not blocking.

Thanks for reviewing, yea just fyi gemini pro/flash/claude is the legacy usage display, and it's been replaced with session/weekly. I'll try to add the migration thing, and I might also update the color for agy to blue for better consistency.

Thanks for the context, Session/Weekly makes sense. Feel free to add the migration here or in a follow-up; I’ll take another look once you push updates. I’ll merge when CI is green and the changes still look good.

@barramee27

Copy link
Copy Markdown
Owner

I'll merge the current commit within 2 days unless you push updates to this branch. Tray label migration can land in a follow-up PR.

@github-actions github-actions Bot added the core label Jul 14, 2026
@barramee27

Copy link
Copy Markdown
Owner

Thanks for the migration looks good overall, and CI is green.

Before merge: ANTIGRAVITY_PLUGIN_IDS includes antigravity-ide, but that plugin still uses Gemini Pro / Flash / Claude. Migrating those tray lines to Session / Weekly would break IDE customizations. Please drop antigravity-ide from the set (keep only antigravity + antigravity-cli).

Also prefer in this PR (Windows CLI): in read_windows_keyring_password, for the go-keyring target (service:username), after get_secret + UTF-8 decode fails, fall back to get_password() on that same entry before trying the default username.service target.

Why: agy writes raw UTF-8 (get_secret works), but antigravity-cli token refresh writes via set_password (UTF-16). Without the fallback, the next probe can fail to read the credential we just wrote.

Optional nits: map "Claude Weekly" → "Weekly — Claude and GPT Models", plus a small settings test for the migration.

Happy to merge once the antigravity-ide fix is in; the keyring fallback would be great in the same commit if you have time.

@idkwhodatis

Copy link
Copy Markdown
Author

Thanks for the migration looks good overall, and CI is green.

Before merge: ANTIGRAVITY_PLUGIN_IDS includes antigravity-ide, but that plugin still uses Gemini Pro / Flash / Claude. Migrating those tray lines to Session / Weekly would break IDE customizations. Please drop antigravity-ide from the set (keep only antigravity + antigravity-cli).

Also prefer in this PR (Windows CLI): in read_windows_keyring_password, for the go-keyring target (service:username), after get_secret + UTF-8 decode fails, fall back to get_password() on that same entry before trying the default username.service target.

Why: agy writes raw UTF-8 (get_secret works), but antigravity-cli token refresh writes via set_password (UTF-16). Without the fallback, the next probe can fail to read the credential we just wrote.

Optional nits: map "Claude Weekly" → "Weekly — Claude and GPT Models", plus a small settings test for the migration.

Happy to merge once the antigravity-ide fix is in; the keyring fallback would be great in the same commit if you have time.

yea mb got the wrong migration lol, I'll add your review items later

@barramee27

Copy link
Copy Markdown
Owner

Thanks again for the migration/color fix in 1ae663f that part looks good.

I’m going to ship 1.3.2 from #16 (OpenUsage port) without waiting on this PR, so #15 will target the next release (likely 1.3.3), not 1.3.2.

Still happy to merge this once the Windows go-keyring fallback is in (get_password on the same service:username entry when UTF-8 get_secret fails). No deadline push when you can and I’ll review.

@idkwhodatis

Copy link
Copy Markdown
Author

Hi the Windows go-keyring is actually in place, sry forgot to split into a different commit, should be safe to merge!

@barramee27

Copy link
Copy Markdown
Owner

Thanks confirmed the Windows go-keyring fix is in place (get_secret + UTF-8 decode for go-keyring targets). That’s what we needed.

The merge conflicts aren’t from your logic fighting ours the branch is based before #16 and #17 landed on feat/linux-windows-native-support (1.3.2 + 1.3.3), so GitHub can’t auto-merge.

Since maintainer edits are enabled, I’ll rebase/resolve conflicts on my side and merge for the next patch (likely 1.3.4). No action needed from you unless I ping with a question.

Appreciate the work on agy desktop/cli + the migration bits.

@barramee27
barramee27 force-pushed the feat/linux-windows-native-support branch from 1ae663f to 0a99392 Compare July 19, 2026 03:52
@idkwhodatis

Copy link
Copy Markdown
Author

Thanks confirmed the Windows go-keyring fix is in place (get_secret + UTF-8 decode for go-keyring targets). That’s what we needed.

The merge conflicts aren’t from your logic fighting ours the branch is based before #16 and #17 landed on feat/linux-windows-native-support (1.3.2 + 1.3.3), so GitHub can’t auto-merge.

Since maintainer edits are enabled, I’ll rebase/resolve conflicts on my side and merge for the next patch (likely 1.3.4). No action needed from you unless I ping with a question.

Appreciate the work on agy desktop/cli + the migration bits.

thanks for your work too, been looking for this app on windows!

@barramee27 barramee27 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good Windows go-keyring get_secret + UTF-8 decode is the right fix, quota summary/migration/color changes check out, and CI is green after the rebase onto #16/#17. Thanks!

@barramee27
barramee27 merged commit 4029c9f into barramee27:feat/linux-windows-native-support Jul 19, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants