Codex Meter Agent 2.2.1

Fix OpenCodex Hub quota reset dates when the Hub returns Unix seconds. Millisecond reset values remain supported; missing/zero resets remain unavailable. Applies to weekly, monthly, short and custom quota windows. Observation timestamps, usage/coverage, account selection and Native collection are unchanged. Agent-only hotfix; no Server redeployment or database migration required.

Codex Meter Agent 2.2.0

Codex Meter V2.2.0

• Adds OpenCodex Hub as a measurement source, tracking only the account explicitly selected for a Meter Profile.
• Shows Hub-observed Today / 7D / 30D / All usage snapshots and coverage, with quota reporting for the limits provided by the Hub.
• Adds the interactive codex-meter-agent opencodex setup wizard for Hub connection and account selection.
• Simplifies existing CODEX_HOME onboarding: profile attach-existing now opens the local discovery/selection flow; --discover remains supported.
• Codex CLI and IDE extensions using the same selected CODEX_HOME continue to feed the same Native Profile.
• Retains Native V2.1.x compatibility and existing usage history. Upgrade the Meter Server before using the new Hub functionality.

Measurement and privacy

Hub credentials and selected Hub account identifiers remain Agent-local; Meter receives selected-Profile summaries, not credentials or other Hub accounts' data. Hub aggregate snapshots are not converted into fake Native usage events and do not claim end-user device attribution. Coverage is reported as observed, not assumed complete.

No breaking Native protocol changes. Existing default, adopted, and managed isolated Codex environments remain supported.

Codex Meter V2.1.3

What’s new

• Connect an existing Codex environment with explicit local selection.
• Use multiple Account Profiles with selected-environment-only tracking.
• Keep usage and provider quota isolated per Account Profile.
• Display 5H and Weekly windows with distinct provider limit identifiers.
• Protect adopted environment contents, configuration, authentication and sessions.
• Correct deleted-device visibility and account device counts while preserving history.

No breaking protocol changes; current-login and managed-isolated flows are preserved. Existing-environment quota requires supported Linux/WSL isolation with Bubblewrap; no unsafe fallback is used.

기존 Codex 환경의 명시적 선택, 계정별 사용량·쿼터 분리, 5H/Weekly 표시 및 삭제된 기기 표시를 개선했습니다. 기존 사용 이력과 기본 로그인·분리 환경 흐름을 유지합니다.

Codex Meter Agent 2.1.1

Codex Meter V2.1.1

This maintenance release fixes Account Profile creation during Device onboarding.

• Device Add account now remains available when every existing profile is already assigned.
• A new Account Profile can be created directly from Device onboarding and the Add account dialog.
• The newly created profile is selected automatically.
• Device name, Group, and current/separate login choice are preserved through profile creation.
• Profile saves block duplicate submission and Cancel/Escape races while the request is pending.
• Existing declarative configuration, usage attribution, quota behavior, and selective tracking semantics are unchanged.

Codex Meter still tracks only Codex environments explicitly assigned to a Meter Account Profile. It does not discover or identify unrelated provider accounts.

Validation

• Node 24 full suite: 222/222
• V1: 68/68
• V2: 154/154
• Luna max review: Critical 0, High 0, Medium 0
• Linux x64, Windows x64, and macOS arm64 native build/SEA smoke: PASS
• Isolated Server/UI Canary: PASS

Codex Meter Agent 2.1.0

Codex Meter V2.1

V2.1 introduces Account Profiles and declarative Device-to-Agent configuration. Device onboarding now follows the product flow: create a Device, select the Account Profile to track, run the generated bootstrap command, and sign in to Codex only when requested. Manual agent.json editing and manual service restarts are not required.

Highlights

• One-account onboarding that safely adopts the Device's current Codex login.
• Isolated multi-account profiles with automatic private CODEX_HOME and launcher creation.
• Explicit opt-in tracking: only Codex environments the user assigns to Meter Account Profiles are collected.
• Zero-touch migration of profiles already managed by Codex Meter, preserving launchers, homes, cursors, outbox records, and history.
• Live declarative configuration apply without an Agent restart, with last-known-good behavior on apply failure.
• Stop tracking without deleting the Codex login, local data, sessions, launcher, or historical Meter data.
• Per-Account quota status, quota-cycle attribution, tracking coverage, and estimated quota contribution.
• Account, Device, and Group usage breakdowns with offline replay and restart preservation.

Privacy and identity

Codex Meter does not automatically identify provider accounts. Users explicitly assign Codex environments to Meter Account Profiles. Unregistered Codex environments are not discovered, inspected, watched, collected, modified, or reported to the Server.

The Server does not receive local CODEX_HOME paths or authentication material. Codex Meter does not read or copy provider credentials and does not sign in on the user's behalf.

Estimated quota contribution is an estimate that allocates provider-reported Account usage in proportion to locally tracked token usage. It is not exact provider-attributed usage.

Validation

• Linux live onboarding: validated.
• Windows x64 native build and SEA smoke: validated; Windows live onboarding: NOT TESTED.
• macOS arm64 native build and SEA smoke: validated; macOS live onboarding: NOT TESTED.
• Natural provider reset: NOT TESTED. Reset and cycle-boundary behavior is covered by automated boundary tests.
• Node.js 24.15 full suite: 218/218 passed; V1: 68/68; V2: 150/150; 0 failed; 0 skipped.
• Independent gpt-5.6-luna review at max reasoning: Critical 0, High 0, Medium 0.

v2-agent-2.0.1

fix: verify release checksums from artifact directory