Gengchou v2.3.4

Gengchou v2.3.4

v2.3.4 is a focused first-run consent-window hotfix for v2.3.3.

Changes

• Initialize the taskbar and tray surfaces before asking for provider
  credential access, so a first-run permission prompt cannot be stranded
  behind an app that has not shown any visible UI.
• Use a foreground, minimizable Windows task dialog for provider permission.
  The default remains No, and minimizing or closing the dialog does not
  grant access.
• Preserve the v2.3.3 privacy boundary: before authorization, Gengchou does
  not read or watch that provider's credential source and does not send quota
  requests for it.

Updating

No settings or cache migration is required. Users who already made a provider
permission decision are not prompted again.

Do not update an installation older than v2.2.4 directly to this release. The
v2.2.4 release remains available as the required bridge.

Gengchou v2.3.3

Gengchou v2.3.3

v2.3.3 adds explicit, provider-specific permission before Gengchou reads any
local provider credential or starts provider polling.

Changes

• Ask before accessing Claude Code, Codex, or Antigravity credentials. Each
  prompt identifies the credential source, defaults to No, and records the
  user's decision.
• Add a Provider access submenu for granting or revoking each permission at
  any time. Revocation stops credential watches and future polls, invalidates
  in-flight results, and removes that provider's cached usage.
• Keep dynamic authentication refresh working after permission is granted by
  re-reading the original credential file or Windows Credential Manager entry.
  Gengchou does not copy or store provider tokens.
• Keep the detail popup open across focus changes when it is pinned.

Updating

Existing users are asked once for each visible provider because older settings
do not contain a permission decision. Choosing No is remembered and no
credential-backed operation runs for that provider. Permission can be changed
later from the context menu.

No settings or cache migration is otherwise required. Do not update an
installation older than v2.2.4 directly to this release; v2.2.4 remains the
required bridge.

Gengchou v2.3.2

Gengchou v2.3.2

v2.3.2 finalizes the publisher namespace before Gengchou's first WinGet
publication. It does not change settings, cached usage data, or provider
authentication.

Changes

• Move the official repository and release links to ynjmxn/gengchou.
• Adopt ynjmxn.Gengchou as the WinGet package identifier.
• Align the Windows publisher metadata, documentation, and release checklist
  with the new namespace.
• Add a CI and release check that prevents the retired publisher identity from
  returning to the current source tree.

Updating

No settings or cache migration is required. Users of v2.3.1 can update
normally or replace the existing executable with gengchou.exe and start it
again.

Do not update an installation older than v2.2.4 directly to this release. The
v2.2.4 release remains available as the required bridge.

Gengchou v2.3.1

Gengchou v2.3.1

v2.3.1 fixes startup on clean Windows installations for both portable and
WinGet deployments.

Changes

• Statically link the MSVC C runtime so no separate Visual C++ Redistributable
  installation is required.
• Add CI and release checks that reject unexpected external MSVC/UCRT runtime
  dependencies in the portable executable.

Updating

No settings or cache migration is required. Users of v2.3.0 can replace the
existing executable with gengchou.exe and start it normally.

Do not update an installation older than v2.2.4 directly to this release. The
v2.2.4 release remains available as the required bridge.

Gengchou v2.3.0

Gengchou v2.3.0

v2.3.0 completes the internal identity transition begun on the 2.2.x line.
It is intentionally limited to removing the one-time bridge and publishing a
single, unambiguous Gengchou package surface.

Changes

• Remove the completed settings, cache, startup-entry, and runtime-identity
  migration state machine.
• Use only the Gengchou mutex, window classes, data directories, relaunch
  variables, and updater readiness protocol.
• Publish only gengchou.exe and gengchou-windows-x64.zip; compatibility
  asset aliases and the bridge verifier are no longer part of new releases.
• Add a CI and release gate that rejects retired identity strings outside the
  acknowledgements, provenance record, and historical release notes.

Updating

Users who completed the v2.2.4 bridge can replace the existing executable with
gengchou.exe and start it normally. Settings, cache, startup preference, and
window positions remain under the Gengchou data directories.

Do not update an installation older than v2.2.4 directly to this release. The
v2.2.4 release remains available as the required bridge.

Gengchou v2.2.4

Gengchou v2.2.4

v2.2.4 is the one-time bridge from the former internal identity to Gengchou.
It is not a WinGet release.

What changes

• Move settings and a valid, fresh usage cache to %APPDATA%\Gengchou.
• Start a new diagnostic log and updater workspace under
  %LOCALAPPDATA%\Gengchou.
• Move the Start with Windows value to Gengchou after verifying that it
  belongs to the running executable.
• Use Gengchou window classes and relaunch variables. During this bridge only,
  the app holds both the old and new mutexes so v2.2.3 and v2.2.4 cannot run
  together.
• Accept the v2.2.3 updater's old ready-marker protocol on entry. Updates
  started by v2.2.4 use only the new Gengchou protocol.
• Pause all later update checks until the migration reaches complete, so a
  future v2.3.0 cannot be installed before the required second start.

Required one-time restart

1. Update to v2.2.4 and confirm that the app is running normally.
2. Exit Gengchou, then start gengchou.exe once more.
3. Place verify-v2.2.4-migration.ps1 beside this release's SHA256SUMS, then
   run it with -RequireMigratedSource -RequireOfficialHash. Continue to
   v2.3.0 only after it reports PASS.

A clean v2.2.4 installation with no earlier settings should omit
-RequireMigratedSource and still require the official hash.

The first launch copies and verifies user data but does not delete its source.
The second launch removes only known old files owned by this project. Data from
the original CodeZeno application is never deleted. If an owned old directory
contains an unknown file or a reparse point, monitoring remains available, but
cleanup stays pending and updates remain disabled. The old diagnostic log is
not copied.

Keep this release available as the supported bridge for installations on
v2.2.3 or earlier. Keeping it downloadable is not enough: v2.3.0 must not be
published until every supported pre-v2.2.4 installation has run v2.2.4 twice
and passed the verifier. A clean installation without old settings is the only
exception.

Gengchou v2.2.3

Gengchou v2.2.3

This maintenance release notices completed sign-ins sooner, keeps quota
windows aligned with provider data, and offers a more useful set of refresh
intervals.

Fixes

• Watch local credentials whenever a visible provider requires sign-in and
  refresh within seconds after the credentials change, without making usage
  requests on every watch tick. Credential checks now run off the UI thread,
  and WSL distribution discovery is cached to avoid repeated slow probes.
• Recheck immediately when credentials change during an in-flight poll, so a
  result based on an expired session cannot leave the sign-in warning visible
  until the next scheduled refresh.
• Preserve Codex quota-window durations reported by the provider instead of
  inferring them from the account plan.
• Prefer Antigravity's quota summary when it identifies the five-hour and
  weekly windows, and reject a per-model reset that cannot plausibly belong to
  a five-hour window. This prevents the same weekly quota from appearing as
  identical five-hour and seven-day rows.
• Replace the sparse 1, 5, 15, and 60-minute refresh choices with 1, 2, 5, 10,
  15, and 30 minutes. New and repaired settings default to five minutes; an
  existing one-hour setting is normalized to that default.

No settings or cache migration is required. Existing v2.2.2 installations can
update in place through Gengchou's built-in updater.

Gengchou v2.2.2

Gengchou v2.2.2

This patch makes multi-provider refreshes complete sooner and keeps Claude
quota data aligned with the provider's real cooldown and reset boundaries.

Fixes

• Poll enabled providers concurrently so one slow endpoint no longer delays
  fresh data from every other provider in the same refresh pass.
• Expire a cached Claude quota snapshot as soon as one of its reported reset
  times passes instead of retaining pre-reset usage until the next cooldown.
• Align the one-minute refresh timer with Claude's 180-second normal and
  120-second fast cooldown deadlines, avoiding an extra scheduler interval
  when a deadline falls between fixed ticks.
• Preserve existing partial-success behavior, provider-specific error badges,
  and Claude rate-limit backoff while applying the new scheduling logic.
• Retry one transient Codex TLS, transport, or 502/503/504 failure after a
  short delay, with a Codex-specific 10-second request timeout so a stalled
  usage endpoint cannot hold the refresh pass for the previous 30 seconds.
• Keep the last known number visible with a subtle ~ marker for transient
  provider failures and rate limiting, regardless of outage duration or cache
  availability. Reserve the red ! for states that require user action, such
  as missing, expired, or rejected credentials.
• Require consistent authentication rejection across Antigravity's fallback
  endpoints, and avoid applying one provider's authentication error to every
  provider when an all-provider refresh fails for mixed reasons.
• Reuse Antigravity connections with a 10-second per-request timeout, and
  suppress repeated Codex or Antigravity network calls for credentials already
  rejected by the provider. A credential change retries on the next refresh;
  partial failures with unchanged credentials receive a 15-minute safety
  recheck while the other providers continue refreshing.
• Log consecutive transient failures and recovery transitions so short network
  blips can be distinguished from persistent provider outages.
• Detect when the secondary monitor hosting the taskbar widget, floating
  monitor, or an open detail popup is removed (including RDP topology changes)
  and reset the affected surface to its primary-screen default. Ordinary DPI
  changes and Explorer taskbar recreation keep the user's chosen position.

No settings or cache migration is required. Existing v2.2.1 installations can
update in place through Gengchou's built-in updater.

Gengchou v2.2.1

Gengchou v2.2.1

This patch restores Antigravity's 5-hour quota window while preserving the
weekly window introduced by the provider's newer quota-summary response.

Fixes

• Fetch Antigravity's per-model 5-hour quota and weekly quota summary
  independently, then merge them into the existing dynamic-window model.
• Keep either Antigravity window available when the other endpoint is
  temporarily unavailable instead of dropping all usage data.
• Deduplicate legacy responses that still expose a 5-hour bucket through the
  weekly-summary endpoint.
• Accept the nested quotaSummary.groups response shape and infer known
  durations from bucket identifiers when the API omits an explicit window.
• Preserve weekly-only accounts without inventing a misleading 5-hour row.

No settings or cache migration is required. Existing v2.2.0 installations can
update in place through Gengchou's built-in updater.

Gengchou v2.2.0

Gengchou v2.2.0

AI Usage Monitor is now Gengchou. The new name reflects the app's job:
quietly keeping watch over recurring AI quota windows and their reset times.
The Windows UI uses the unlocalized Gengchou brand; Chinese documentation
also introduces the name as “更筹 Gengchou” (gēng chóu).

Rename and compatibility

• Rename the application, executable, release assets, and public package
  identity to Gengchou.
• Keep the existing %APPDATA%\AIUsageMonitor settings/cache directory,
  %LOCALAPPDATA%\AIUsageMonitor diagnostics/update directory, startup value,
  window classes, mutex, and tray GUIDs. Existing users keep their data and
  single-instance behavior without a migration step.
• Preserve the application icon from v2.1.0. A possible icon refinement is
  intentionally deferred rather than bundled into the rename.
• Add a tray registration fallback for users who move the renamed executable
  to a new path: if Windows rejects the existing GUID identity, the app retries
  with its stable per-process uID identity so the tray icons remain visible
  and interactive.

Updating from AI Usage Monitor

The transition release publishes both the new gengchou.exe /
gengchou-windows-x64.zip assets and compatibility copies under the former
ai-usage-monitor names. Older updaters continue to locate and verify the old
asset name; Gengchou selects the new asset name exactly. Both names are covered
by SHA256SUMS and GitHub artifact attestations.

Settings and usage data are not renamed or copied. After the update, Gengchou
opens the same configuration and cache that AI Usage Monitor used.

WinGet

The former yinjianxxx.AIUsageMonitor package was never published. Gengchou
will enter WinGet as a new package, yinjianxxx.Gengchou, after the GitHub
release and upgrade checks pass.