@modelprofile.com/authswitch 9.1.0 → 10.0.0

package/openai-codex-license.txt

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1.  Definitions.
+
+    "License" shall mean the terms and conditions for use, reproduction,
+    and distribution as defined by Sections 1 through 9 of this document.
+
+    "Licensor" shall mean the copyright owner or entity authorized by
+    the copyright owner that is granting the License.
+
+    "Legal Entity" shall mean the union of the acting entity and all
+    other entities that control, are controlled by, or are under common
+    control with that entity. For the purposes of this definition,
+    "control" means (i) the power, direct or indirect, to cause the
+    direction or management of such entity, whether by contract or
+    otherwise, or (ii) ownership of fifty percent (50%) or more of the
+    outstanding shares, or (iii) beneficial ownership of such entity.
+
+    "You" (or "Your") shall mean an individual or Legal Entity
+    exercising permissions granted by this License.
+
+    "Source" form shall mean the preferred form for making modifications,
+    including but not limited to software source code, documentation
+    source, and configuration files.
+
+    "Object" form shall mean any form resulting from mechanical
+    transformation or translation of a Source form, including but
+    not limited to compiled object code, generated documentation,
+    and conversions to other media types.
+
+    "Work" shall mean the work of authorship, whether in Source or
+    Object form, made available under the License, as indicated by a
+    copyright notice that is included in or attached to the work
+    (an example is provided in the Appendix below).
+
+    "Derivative Works" shall mean any work, whether in Source or Object
+    form, that is based on (or derived from) the Work and for which the
+    editorial revisions, annotations, elaborations, or other modifications
+    represent, as a whole, an original work of authorship. For the purposes
+    of this License, Derivative Works shall not include works that remain
+    separable from, or merely link (or bind by name) to the interfaces of,
+    the Work and Derivative Works thereof.
+
+    "Contribution" shall mean any work of authorship, including
+    the original version of the Work and any modifications or additions
+    to that Work or Derivative Works thereof, that is intentionally
+    submitted to Licensor for inclusion in the Work by the copyright owner
+    or by an individual or Legal Entity authorized to submit on behalf of
+    the copyright owner. For the purposes of this definition, "submitted"
+    means any form of electronic, verbal, or written communication sent
+    to the Licensor or its representatives, including but not limited to
+    communication on electronic mailing lists, source code control systems,
+    and issue tracking systems that are managed by, or on behalf of, the
+    Licensor for the purpose of discussing and improving the Work, but
+    excluding communication that is conspicuously marked or otherwise
+    designated in writing by the copyright owner as "Not a Contribution."
+
+    "Contributor" shall mean Licensor and any individual or Legal Entity
+    on behalf of whom a Contribution has been received by Licensor and
+    subsequently incorporated within the Work.
+
+2.  Grant of Copyright License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    copyright license to reproduce, prepare Derivative Works of,
+    publicly display, publicly perform, sublicense, and distribute the
+    Work and such Derivative Works in Source or Object form.
+
+3.  Grant of Patent License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    (except as stated in this section) patent license to make, have made,
+    use, offer to sell, sell, import, and otherwise transfer the Work,
+    where such license applies only to those patent claims licensable
+    by such Contributor that are necessarily infringed by their
+    Contribution(s) alone or by combination of their Contribution(s)
+    with the Work to which such Contribution(s) was submitted. If You
+    institute patent litigation against any entity (including a
+    cross-claim or counterclaim in a lawsuit) alleging that the Work
+    or a Contribution incorporated within the Work constitutes direct
+    or contributory patent infringement, then any patent licenses
+    granted to You under this License for that Work shall terminate
+    as of the date such litigation is filed.
+
+4.  Redistribution. You may reproduce and distribute copies of the
+    Work or Derivative Works thereof in any medium, with or without
+    modifications, and in Source or Object form, provided that You
+    meet the following conditions:
+
+    (a) You must give any other recipients of the Work or
+    Derivative Works a copy of this License; and
+
+    (b) You must cause any modified files to carry prominent notices
+    stating that You changed the files; and
+
+    (c) You must retain, in the Source form of any Derivative Works
+    that You distribute, all copyright, patent, trademark, and
+    attribution notices from the Source form of the Work,
+    excluding those notices that do not pertain to any part of
+    the Derivative Works; and
+
+    (d) If the Work includes a "NOTICE" text file as part of its
+    distribution, then any Derivative Works that You distribute must
+    include a readable copy of the attribution notices contained
+    within such NOTICE file, excluding those notices that do not
+    pertain to any part of the Derivative Works, in at least one
+    of the following places: within a NOTICE text file distributed
+    as part of the Derivative Works; within the Source form or
+    documentation, if provided along with the Derivative Works; or,
+    within a display generated by the Derivative Works, if and
+    wherever such third-party notices normally appear. The contents
+    of the NOTICE file are for informational purposes only and
+    do not modify the License. You may add Your own attribution
+    notices within Derivative Works that You distribute, alongside
+    or as an addendum to the NOTICE text from the Work, provided
+    that such additional attribution notices cannot be construed
+    as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and
+    may provide additional or different license terms and conditions
+    for use, reproduction, or distribution of Your modifications, or
+    for any such Derivative Works as a whole, provided Your use,
+    reproduction, and distribution of the Work otherwise complies with
+    the conditions stated in this License.
+
+5.  Submission of Contributions. Unless You explicitly state otherwise,
+    any Contribution intentionally submitted for inclusion in the Work
+    by You to the Licensor shall be under the terms and conditions of
+    this License, without any additional terms or conditions.
+    Notwithstanding the above, nothing herein shall supersede or modify
+    the terms of any separate license agreement you may have executed
+    with Licensor regarding such Contributions.
+
+6.  Trademarks. This License does not grant permission to use the trade
+    names, trademarks, service marks, or product names of the Licensor,
+    except as required for reasonable and customary use in describing the
+    origin of the Work and reproducing the content of the NOTICE file.
+
+7.  Disclaimer of Warranty. Unless required by applicable law or
+    agreed to in writing, Licensor provides the Work (and each
+    Contributor provides its Contributions) on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+    implied, including, without limitation, any warranties or conditions
+    of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+    PARTICULAR PURPOSE. You are solely responsible for determining the
+    appropriateness of using or redistributing the Work and assume any
+    risks associated with Your exercise of permissions under this License.
+
+8.  Limitation of Liability. In no event and under no legal theory,
+    whether in tort (including negligence), contract, or otherwise,
+    unless required by applicable law (such as deliberate and grossly
+    negligent acts) or agreed to in writing, shall any Contributor be
+    liable to You for damages, including any direct, indirect, special,
+    incidental, or consequential damages of any character arising as a
+    result of this License or out of the use or inability to use the
+    Work (including but not limited to damages for loss of goodwill,
+    work stoppage, computer failure or malfunction, or any and all
+    other commercial damages or losses), even if such Contributor
+    has been advised of the possibility of such damages.
+
+9.  Accepting Warranty or Additional Liability. While redistributing
+    the Work or Derivative Works thereof, You may choose to offer,
+    and charge a fee for, acceptance of support, warranty, indemnity,
+    or other liability obligations and/or rights consistent with this
+    License. However, in accepting such obligations, You may act only
+    on Your own behalf and on Your sole responsibility, not on behalf
+    of any other Contributor, and only if You agree to indemnify,
+    defend, and hold each Contributor harmless for any liability
+    incurred by, or claims asserted against, such Contributor by reason
+    of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+Copyright 2025 OpenAI
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@modelprofile.com/authswitch",
-  "version": "9.1.0",
+  "version": "10.0.0",
   "private": false,
   "description": "Manage Codex, OpenCode and Claude Code accounts with guided switching and live usage status",
   "main": "dist_ts/index.js",
@@ -66,8 +66,8 @@
     "@api.global/typedrequest-interfaces": "7.1.0",
     "@lossless.org/client": "1.6.0",
     "@lossless.org/nosqldb": "10.6.0",
-    "@modelprofile.com/flexharness-models": "^9.0.0",
-    "@modelprofile.com/flexharness-providers": "^9.0.0",
+    "@modelprofile.com/flexharness-models": "^9.3.1",
+    "@modelprofile.com/flexharness-providers": "^9.3.1",
     "@modelprofile.com/mcp-crossharness": "5.6.0",
     "@push.rocks/smartconsole": "^1.3.0",
     "@push.rocks/smartdaemon": "2.7.2",
@@ -79,7 +79,9 @@
     "ts/**/*",
     "dist_ts/**/*",
     "cli.js",
-    "readme.md"
+    "readme.md",
+    "third-party-notices.md",
+    "openai-codex-license.txt"
   ],
   "browserslist": [
     "last 1 chrome versions"

package/readme.md

@@ -29,8 +29,8 @@ Node.js 24 or newer is required.
 The package also exports a typed client for a per-user authswitch authority daemon. Its
 SmartData registry stores account identity separately from sealed refresh grants, runtime
 bindings, durable device-operation receipts, Codex enrollment records, and native-handoff and migration journals. A daemon
-owns OpenAI device login, targeted reauthentication, and proactive refresh for grants
-added through this API. Management snapshots expose separate account and login rows,
+owns OpenAI device login, targeted reauthentication, proactive refresh, and, on request,
+revocation at removal for grants added through this API. Management snapshots expose separate account and login rows,
 including each login's purpose, owner, health, problem and available actions; neither
 snapshots nor events contain credentials. A login that a native tool refreshes also names
 that tool -- `ownerTool` is `claude_code`, `codex` or `opencode`, and `null` exactly when no
@@ -73,12 +73,13 @@ Browser code can import the credential-free DTOs from
 `@modelprofile.com/authswitch/authority-contract`. The backend-only binding, access and release
 requests are named by `@modelprofile.com/authswitch/authority-runtime-contract`, and the one-time
 import's own DTOs by `@modelprofile.com/authswitch/authority-import-contract`; those capabilities must
-never reach a browser. Two of the three runtime requests are served on the runtime socket -- resolving
-access and releasing a binding -- while `authswitch.authority.bind` is served on the **management** socket
-by design: minting a capability is the act that authorizes a runtime, so only a trusted management caller
-may perform it, and a container that is given the runtime directory can use a binding it was handed but can
-never create one. A backend binds an account to a runtime incarnation by exact account ID, login ID and
-purpose, and keeps the returned capability private. Targeted reauthentication likewise requires the
+never reach a browser. Two of the four runtime requests are served on the runtime socket -- resolving
+access and releasing a binding -- while `authswitch.authority.bind` and its inverse
+`authswitch.authority.unbind` are served on the **management** socket by design: minting a capability is the
+act that authorizes a runtime, so only a trusted management caller may perform it, and a container that is
+given the runtime directory can use and release a binding it was handed but can never create one or
+release one it was not handed. A backend binds an account to a runtime incarnation by exact account ID,
+login ID and purpose, and keeps the returned capability private. Targeted reauthentication likewise requires the
 exact login; an account's presentation default never selects a grant for either action. Completed and
 interrupted operations remain discoverable through `getOperation()` and paged
 `listOperations()`. `watchOperation(id, afterRevision, waitMs = 30000)` is the same read as a long poll,
@@ -91,8 +92,14 @@ callers supply one UUID for the logical start and reuse it after a lost response
 UUID returns the same matching receipt without starting another provider login; using it for a
 different target is rejected. Cancelling a durable `starting` receipt prevents a late provider
 handle from promoting or overwriting it. Aborting a client request only detaches that request and
-does not cancel the daemon-owned login. The runtime-only socket
-resolves that binding to a current access token; its directory can be mounted into a
+does not cancel the daemon-owned login. A client that disconnects before its answer -- a long poll it
+stopped reading, or one the daemon's shutdown settles after the client went away -- ends only its own
+connection: the daemon drops that request's pending work and keeps serving every other client. Each
+request is bounded by its own deadline -- 35 s unless its route states another, 120 s for an import submit,
+the wait plus 5 s for a long poll -- and nothing in the transport ends it sooner: the daemon gives a
+connection 35 s from acceptance to deliver its complete request, however it trickles in, and sets no limit
+once it is admitted.
+The runtime-only socket resolves that binding to a current access token; its directory can be mounted into a
 container without exposing the management socket. A provider that rejects a specific
 access-token generation can request a newer one through `rejectedGrantGeneration`; the
 authority coalesces concurrent rejection callbacks and never replays an uncertain refresh.
@@ -105,20 +112,53 @@ server-side resolution handlers, but handler completion does not prove response
 cannot retract an access token already received or in use; the runtime owner therefore owns that
 drain. Generic release cannot revoke a managed Codex binding, whose daemon-owned stop still closes
 the runtime and clears its durable run before internal revocation. Binding release never transfers
-or changes ownership of the account grant. A holder that crashed and lost its capability recovers
-its binding without a new route: the snapshot (and `getBinding`) publishes each binding's runtime and
-scope, binding that runtime and scope again replaces the capability, and releasing the returned
-capability releases the binding. If binding again is refused because the account needs a new sign-in,
-reauthenticate it first.
+or changes ownership of the account grant.
+
+A holder that lost its capability -- a binding an earlier run of it left behind -- releases it with
+`unbind({ runtime, scopeId, incarnationId, expectedRevision })` (`authswitch.authority.unbind`), naming the
+binding by the identity it bound it under, as the snapshot and `getBinding` publish it. Unbinding needs no
+ready login, so the leftover bindings of an account whose sign-in has ended are released, and the account
+removed, without signing in again. It is authorized exactly as `bind` is: the management socket is the trust
+boundary, and a runtime and scope are the namespace a holder binds under and owns -- AGL, for example, binds
+under its own installation's scopes -- so a holder names only its own. The daemon releases only the binding
+at exactly that runtime and scope, and only while it is still the incarnation and revision the holder read:
+another scope, another runtime, or a successor bound in the meantime is left alone, and the answer is
+`inactive`, as it is for a binding already released. A binding's revision is the authority revision of the
+bind that wrote it, so it never repeats for a runtime and scope, even after a release: a repeated or stale
+unbind never names a successor bound under the same incarnation. Its capability is fenced and released exactly as the
+runtime release would, so admitted access resolutions finish first. Managed Codex bindings are never named
+here. While the login is ready, a holder can instead bind the same runtime and scope again, which replaces
+the capability, and release the returned one.
 
 `getBinding(bindingId)` (`authswitch.authority.binding`) reads one binding by the id `bind` returned,
 credential-free, or `null` once the authority holds none by that id, so a backend checks its binding without
 reading the whole snapshot.
 
 Removing an account that still backs a Flex, OpenCode or Claude binding is refused with `account_busy`, naming
-those runtimes: their holder stops them and releases the bindings first, so a removal never strands a
-runtime whose next access would fail. Managed Codex bindings are the daemon's own; removal drains managed
-Codex as before and then takes them with the account.
+those runtimes: their holder stops them and releases the bindings first -- by capability, or by `unbind` when
+it no longer holds one -- so a removal never strands a runtime whose next access would fail. Managed Codex
+bindings are the daemon's own; removal drains managed Codex as before and then takes them with the account.
+
+Removing an account never reaches the network unless the caller asks. `removeAccount(accountId,
+expectedRevision, { revoke: true })` (`revoke: true` on `authswitch.authority.remove`, `--revoke` on the
+command line) also revokes the ChatGPT sign-in the authority held for that account at OpenAI (`/oauth/revoke`,
+the request Codex sends when it logs out). The revocation runs after the removal committed and is best effort,
+like Codex's: the account is removed either way. The revocations get at most 10 seconds in all, so a revoking
+removal answers within the 35 seconds the client allows any request. The answer carries `revoked`: `yes` when
+OpenAI confirmed it, `failed` when it did not, or not within those 10 seconds (the sign-in may still be valid
+there, and the daemon's log says so without the token), `not_applicable` when the authority held no ChatGPT sign-in of its own for the account (a login a
+native tool refreshes is that tool's), and `not_requested` without `revoke`. A daemon older than this client
+refuses `revoke` as an invalid request before changing anything.
+
+**A revocation is irreversible, and authswitch cannot tell whether another tool still refreshes from the
+same sign-in.** A token is opaque; the import ledger records of each source only its kind, a hash of its
+location, a digest of its bytes and the account and login it resolved to; and a login does not record
+whether its current sign-in came from an import or from a device sign-in the authority ran itself. The same
+ChatGPT identity turning up both as an imported copy and as a native Codex store proves the same account, not
+the same sign-in, so no check can tell a shared sign-in from two independent ones. Revoking an imported
+login can therefore sign out a native Codex, OpenCode or other home that still runs on that sign-in. Ask for
+`revoke` only for a sign-in made through `account add openai` or `account reauth`, or when every other copy
+of it should stop working too.
 
 Every route on either socket answers in one of three ways: a result, a **refusal**, or a fault. A refusal
 is an answer -- the daemon completed its check, nothing was left half-done, and its message says what the
@@ -199,6 +239,7 @@ The authority CLI uses that daemon surface without constructing the legacy nativ
 authswitch account list [--json]
 authswitch account add openai [--json]
 authswitch account reauth <account-id> <login-id> [--json]
+authswitch account remove <account-id> [--revoke] [--json]
 authswitch account operation get <operation-id> [--json]
 authswitch account operation cancel <operation-id> [--json]
 authswitch account operation resume <operation-id> [--json]
@@ -224,6 +265,12 @@ receipts until completion. `account operation resume` polls only the supplied du
 response is lost, the fixed diagnostic reports the caller-generated operation ID and exact resume
 command; the CLI does not replay the start request.
 
+`account remove` removes one authority account by the id `account list` shows, at the revision it
+reads just before, and prints the removal and what happened to its ChatGPT sign-in; `--json` prints the
+daemon's answer, `{ account, revoked }`. `--revoke` asks for the revocation described under removal above,
+with the same caveat: authswitch cannot tell whether another tool still runs on that sign-in. The command
+exits nonzero when OpenAI did not confirm a requested revocation, although the account is removed.
+
 `account preuse` sends one quota-consuming prompt through the exact managed OpenAI account and
 login IDs. The default prompt is `Write 2000 words about strawberries.`; `--prompt` replaces it
 and `--model` requests one exact model. `--all` freezes one consistent authority snapshot, walks
@@ -234,11 +281,15 @@ reported as skipped with the snapshot revision, login revision, stored health, p
 observation time; no request or operation ID is created for that skip.
 
 Preuse operations run sequentially and are never retried automatically. Every terminal receipt
-advances an `--all` run, including `not_sent` and `outcome_unknown`, while any attempted operation
+advances an `--all` run, including `not_sent`, `refused` and `outcome_unknown`, while any attempted operation
 that does not complete makes the final exit status nonzero. Snapshot-ineligible skips alone do not
 make an otherwise successful batch fail. Running `--all` again is a new quota-consuming run with
 new operation IDs. Use `account preuse operation resume` to continue observing an existing receipt.
-Only the explicit `cancel` command asks the daemon to cancel one.
+Only the explicit `cancel` command asks the daemon to cancel one. A receipt stopped by a limit
+carries it as `limit` (`{ kind, window, resetsAt }`); a sent request that failed for another stated
+reason is `outcome_unknown` with problem `request_uncertain` and carries its cause as `failure`
+(`{ kind, status, providerCode }`, for example `{ "kind": "http", "status": 503, "providerCode": null }`),
+never the provider's text. Human output prints both as sentences.
 
 For `account add`, `account reauth` and `account operation resume`, `--json` writes JSON Lines:
 each line is one complete operation receipt, and unchanged revisions are omitted. `account
@@ -382,6 +433,10 @@ model catalog, then commits `request_may_have_started` immediately before FlexHa
 inference with retries disabled. Reusing the UUID with the same request returns its durable receipt; changing
 the target, prompt or requested model is rejected. A crash, cancellation or shutdown after the
 marker remains `outcome_unknown` and is never replayed. Before-marker refusals are `not_sent`.
+A reached usage limit is named in the receipt: `problem` is `usage_limit` or `rate_limit` and `limit`
+carries `{ kind, window, resetsAt }` (null otherwise). The account's usage reading stops the prompt
+before the marker (`not_sent`); a provider that refuses the prompt with a limit before it begins to
+answer settles it `refused`, a terminal state in which nothing was consumed.
 Only the request hash, selected model, timing and safe token counts are stored; the prompt,
 generated prose and credentials are absent from persistence and management responses. Account
 removal and targeted reauthentication refuse while that account has an active preuse request.
@@ -660,6 +715,22 @@ the new account without changing the active native login. Ctrl-C cancels login.
 Select the saved account with `use` when ready to switch. Claude Code and other
 OpenCode providers retain their native login commands.
 
+### The ChatGPT sign-in
+
+authswitch runs the ChatGPT sign-in itself, as the one party that signs in and
+refreshes: the device code and its poll, the authorization-code exchange, the
+refresh-token grant, the revocation, the claims of the tokens, and the account's
+`wham/usage` limits. `AuthSwitchOpenAiProvider` is that provider -- `beginLogin`,
+`refreshCredential` (one shared request per refresh token, so a rotating grant is
+sent once), `revokeCredential`, `inspectCredential` and `getAccountRateLimits` --
+and `interfaces.openai` holds its types. It holds no credential of its own. The
+protocol is the one Codex's own login uses, adapted from OpenAI Codex (Apache-2.0;
+see `third-party-notices.md`), and every failure is a fixed message that carries no
+response body, token or header. Inference with a login's access is not auth:
+FlexHarness's `/openai` module serves it from `{ accessToken, accountId,
+isFedrampAccount }` alone, which is exactly what the authority's `resolveAccess`
+answers.
+
 ### Hosted account management
 
 `AuthSwitchService` exposes credential-free account lists, login capabilities,
@@ -670,9 +741,12 @@ ID and `cancel` cancels a pending login. Operations outlive a disconnected clien
 and completed results remain available for ten minutes. Call `close()` during
 host shutdown. The host must authenticate and authorize every request.
 
-Login requests identify the harness, provider and supported flow explicitly.
-`AuthSwitchLogin` is the backend login owner and accepts additional provider
-adapters. Its credential-bearing completion is for backend storage only.
+Login requests identify the harness, provider and flow explicitly; the one flow is
+`device`, which needs no browser on the machine that signs in. `AuthSwitchLogin` is
+the backend login owner. Its default provider is `AuthSwitchOpenAiProvider`,
+authswitch's own ChatGPT sign-in (see "The ChatGPT sign-in"), and it accepts any
+other provider that implements `IAuthLoginProvider`. Its credential-bearing
+completion is for backend storage only.
 When an enclosing registry owns an injected adapter, construct it with
 `{ disposeProviders: false }` as the second argument and dispose that registry
 after closing the login service.
@@ -924,9 +998,28 @@ prompt, the same window the single-account reset table lists first. An account
 that sent no prompt has no model, token count or deadline of its own, and says so
 rather than showing a zero. `Skipped` is a refusal the adapter stated before any
 request -- an API-key login, a missing or expired credential, a model catalog
-that could not be read -- so nothing was consumed for it. `Failed` and
-`Interrupted` may both have consumed tokens and are never retried; `Not run` is
-an account the interruption never reached.
+that could not be read, a usage limit the account has reached -- so nothing was
+consumed for it. `Failed` and `Interrupted` may both have consumed tokens and are
+never retried; `Not run` is an account the interruption never reached. Every
+account that did not complete prints its reason, and a `Failed` one always names
+its cause without the provider's text: a limit, a rejected token, the 180-second
+deadline, a cancellation, an answer that ended unfinished, an HTTP error status
+(`the provider answered HTTP 503`), an answer that could not be read, an error the answer stream reported with the
+provider's error code, a connection that failed before any answer, or an error
+that names no cause.
+
+Before it sends anything, Codex preuse reads the account's usage (`wham/usage`).
+When the account's limit is reached, the account is `Skipped` with the window and
+its reset in local time, for example `Weekly usage limit reached, resets in 16h
+46min (2026-09-27 05:12). No preuse prompt was sent.` A reading that fails
+decides nothing: the prompt is sent and the provider's own answer counts, except a
+rejected token, which is refused before sending as the catalog read refuses it.
+When the provider still refuses the prompt with a usage or rate limit before it
+begins to answer -- a 429 naming `usage_limit_reached`, or a stream that fails with
+it before its first output -- the reason names that limit and says that no tokens
+were consumed. A limit reported after the answer began is named the same way, with
+its window and reset, and says that tokens may already have been consumed: the
+provider had begun to answer.
 
 The guide (`authswitch`, `authswitch -i`) offers **Preuse an account or all
 accounts (consumes quota)** for a harness that supports it. It asks which account
@@ -1660,6 +1753,8 @@ The test suite builds a fixture `CODEX_HOME` with a real SQLite state database a
 
 This repository contains open-source code licensed under the MIT License. A copy of the license can be found in the repository license file.
 
+The ChatGPT sign-in and usage-limit code is adapted from OpenAI Codex, which is licensed under the Apache License, Version 2.0. Its notices are in `third-party-notices.md` and its license in `openai-codex-license.txt`; both ship with the package.
+
 **Please note:** The MIT License does not grant permission to use the trade names, trademarks, service marks, or product names of the project, except as required for reasonable and customary use in describing the origin of the work and reproducing the content of the NOTICE file.
 
 ### Trademarks

package/third-party-notices.md

@@ -0,0 +1,29 @@
+# Third-Party Notices
+
+## OpenAI Codex
+
+OpenAI Codex
+Copyright 2025 OpenAI
+
+The OpenAI ChatGPT device sign-in, authorization-code exchange, refresh-token and
+revocation protocol, the token claims, and the `wham/usage` account rate-limit
+wire contract in this package are adapted in TypeScript from OpenAI Codex
+(https://github.com/openai/codex). They were first adapted from rust-v0.146.1,
+commit `79b4f03d35962b005b007a015113b38930711665`, and re-verified against
+rust-v0.157.0, commit `00c972ed5d6ff6499317fd41b7f23605b8e6850d`
+(`codex-rs/login/src/device_code_auth.rs`, `codex-rs/login/src/auth/manager.rs`,
+`codex-rs/login/src/auth/revoke.rs`, `codex-rs/login/src/oauth/client.rs`,
+`codex-rs/backend-client/src/client.rs` and the rate-limit models in
+`codex-rs/codex-backend-openapi-models/src/models/`).
+
+The adapted files, and their compiled counterparts in `dist_ts/`, are marked
+with a header and contain modifications and integration work copyright 2026
+Task Venture Capital GmbH:
+
+- `ts/openaiauth.ts`
+- `ts/openaiusage.ts`
+- `ts/classes.openaiprovider.ts`
+- `ts/interfaces.openai.ts`
+
+OpenAI Codex is licensed under the Apache License, Version 2.0. A verbatim copy
+of the upstream license is distributed in [openai-codex-license.txt](./openai-codex-license.txt).

package/ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@modelprofile.com/authswitch',
-  version: '9.1.0',
+  version: '10.0.0',
   description: 'Manage Codex, OpenCode and Claude Code accounts with guided switching and live usage status'
 }

package/ts/authority-contract.ts

@@ -178,6 +178,10 @@ export interface IAuthSwitchBinding {
   runtime: 'flex' | 'codex' | 'opencode' | 'claude';
   scopeId: string;
   incarnationId: string;
+  /**
+   * The authority revision at which this runtime and scope were last bound. It grows with every bind and never
+   * repeats for them, not even after a release and a new bind, so it names exactly one bind.
+   */
   revision: number;
 }
 
@@ -353,9 +357,8 @@ export interface IAuthSwitchAccountEvent {
   accountId: string;
 }
 
-export type TAuthSwitchLoginPrompt =
-  | { flow: 'device'; verificationUrl: string; userCode: string }
-  | { flow: 'browser'; authUrl: string };
+/** What a device sign-in shows the person signing in; the authority signs in with a device code only. */
+export type TAuthSwitchLoginPrompt = { flow: 'device'; verificationUrl: string; userCode: string };
 
 export interface IAuthSwitchOperation {
   id: string;
@@ -373,7 +376,38 @@ export interface IAuthSwitchOperation {
   revision: number;
 }
 
-/** Credential-free receipt for one exact, never-replayed quota-consuming request. */
+/**
+ * A limit that kept a preuse prompt from being answered: `usage_limit` is the account's quota, spent until it
+ * resets, `rate_limit` a short throttle. `window` names the window by its length (`weekly`, `five-hour`) and
+ * `resetsAt` is an ISO time; either is null when neither the usage reading nor the provider stated it.
+ */
+export interface IAuthSwitchPreuseLimit {
+  kind: 'usage_limit' | 'rate_limit';
+  window: string | null;
+  resetsAt: string | null;
+}
+
+/**
+ * Why a sent preuse prompt failed without a limit, never with the provider's text. `http` is an answer with an
+ * HTTP error status; `stream` an error the answer stream reported after it began, with the
+ * machine-readable code the error states and no status, since its answer was a success; `response` an answer that could not be read; `network` a connection
+ * that failed before any answer; `aborted` an abort that was neither a cancellation nor the deadline; `unknown`
+ * anything else. `status` and `providerCode` are null when the failure did not state them.
+ */
+export interface IAuthSwitchPreuseFailure {
+  kind: 'http' | 'stream' | 'response' | 'network' | 'aborted' | 'unknown';
+  status: number | null;
+  providerCode: string | null;
+}
+
+/**
+ * Credential-free receipt for one exact, never-replayed quota-consuming request.
+ *
+ * `not_sent` with `usage_limit` is an account whose own usage reading showed a reached limit, so nothing was
+ * sent; `refused` is a prompt the provider refused with a limit before it began to answer, so nothing was
+ * consumed. `limit` describes the limit whenever `problem` is `usage_limit` or `rate_limit`, and is null otherwise.
+ * `failure` names the cause of a `request_uncertain` request when it failed with one, and is null otherwise.
+ */
 export interface IAuthSwitchPreuseOperation {
   id: string;
   accountId: string;
@@ -381,11 +415,13 @@ export interface IAuthSwitchPreuseOperation {
   purpose: 'openai_managed';
   requestedModel: string | null;
   model: string | null;
-  state: 'preparing' | 'request_may_have_started' | 'complete' | 'not_sent' | 'outcome_unknown';
+  state: 'preparing' | 'request_may_have_started' | 'complete' | 'not_sent' | 'refused' | 'outcome_unknown';
   result: { inputTokens: number | null; outputTokens: number | null; totalTokens: number | null } | null;
   problem: 'none' | 'target_unavailable' | 'access_unavailable' | 'catalog_unavailable'
     | 'account_busy' | 'cancelled' | 'authority_closing' | 'interrupted'
-    | 'request_uncertain';
+    | 'request_uncertain' | 'usage_limit' | 'rate_limit';
+  limit: IAuthSwitchPreuseLimit | null;
+  failure: IAuthSwitchPreuseFailure | null;
   createdAt: string;
   updatedAt: string;
   finishedAt: string | null;
@@ -545,10 +581,26 @@ export interface IReq_AuthSwitchGetBinding extends ITypedRequest {
   response: { binding: IAuthSwitchBinding | null };
 }
 
+/**
+ * What a removal did about the account's ChatGPT sign-in at OpenAI:
+ * - `not_requested`: the caller did not ask; nothing reached the network.
+ * - `yes`: OpenAI confirmed the revocation.
+ * - `failed`: OpenAI did not confirm it, or not within the 10 seconds a removal's revocations are given in all;
+ *   the sign-in may still be valid there. The account is removed anyway.
+ * - `not_applicable`: the authority held no ChatGPT sign-in of its own for the account.
+ */
+export type TAuthSwitchRevocation = 'not_requested' | 'yes' | 'failed' | 'not_applicable';
+
+/**
+ * Removes an account. With `revoke: true` the authority also revokes, after the removal committed, the ChatGPT
+ * sign-in it held for the account, and `revoked` says whether OpenAI confirmed it. The revocations take at most 10
+ * seconds in all, so a revoking removal answers within a request's usual 35 seconds. A revocation is irreversible
+ * and reaches everything that still refreshes from that sign-in, which the authority cannot see: see the readme.
+ */
 export interface IReq_AuthSwitchRemoveAccount extends ITypedRequest {
   method: 'authswitch.authority.remove';
-  request: { accountId: string; expectedRevision: number };
-  response: { account: IAuthSwitchAccount };
+  request: { accountId: string; expectedRevision: number; revoke?: true };
+  response: { account: IAuthSwitchAccount; revoked: TAuthSwitchRevocation };
 }
 
 /** Runtime capability is returned only to trusted backend callers; do not expose this response in a browser API. */