Skip to content

Releases

claude-nonstop 1.16.4

Choose a tag to compare

@umer-jahangier umer-jahangier released this 19 Nov 19:58

Fixes "SSL certificate verification failed (UNSUPPORTED_CONSTRAINT_TYPE)" in Claude Code and the Claude desktop app after 1.16.3. The local HTTPS certificate now lists only DNS names: Claude Code runs on Bun, which refuses a certificate that lists an IP address under an authority with IP name constraints. The gateway replaces a 1.16.3 certificate by itself when it starts (no prompt on macOS or Linux; Windows asks to confirm) and gives each SSH server the new authority.

claude-nonstop 1.16.3

Choose a tag to compare

@umer-jahangier umer-jahangier released this 19 Nov 19:39

Security hardening, with nothing to change in how you use it.

  • Signed updates. Automatic and manual updates now install only releases whose tarball carries an Ed25519 signature, over its version and SHA-256, from the claude-nonstop release key pinned in the app. The key never touches GitHub, so a release published through a hijacked repository or account is refused. The version inside the tarball must match too (no rolling back old code under a new number), and downloads never follow an https-to-http redirect.
  • Name-constrained local certificate authority. The authority behind https://claude.nonstop can now vouch only for claude.nonstop, claude-nonstop, localhost (and *.localhost), 127.0.0.1 and ::1, enforced by browsers, macOS and OpenSSL. Run claude-nonstop setup once to replace an existing authority; macOS asks for your password to trust the new one.
  • README and SECURITY.md: what is signed, how to turn automatic updates off, and when to use Strict sandbox for the desktop app.

This is the last update installed without a signature check; from here on every update is verified.

claude-nonstop 1.16.2

Choose a tag to compare

@umer-jahangier umer-jahangier released this 19 Nov 18:20

Now on npm as @umer-jahangier/claude-nonstop. The command is still claude-nonstop; the one-line installer stays the recommended install and updates itself.

  • CI is green again. Tests pass on Node 18 and on Windows (they had failed there since 1.16.0).
  • Website guides: the Claude Code usage limit, several accounts, Codex on a Claude subscription, the desktop app on API keys, API key failover, and how the projects named claude-nonstop differ: https://umer-jahangier.github.io/claude-nonstop/guides/
  • Repository: CHANGELOG.md, CONTRIBUTING.md and SECURITY.md, Discussions, and private vulnerability reporting.

No change to how the tool behaves.

claude-nonstop 1.16.1

Choose a tag to compare

@umer-jahangier umer-jahangier released this 19 Nov 16:23
  • Codex answers on Claude lines are no longer cut off with "Incomplete response returned, reason: max_output_tokens": when the client sets no output limit, the gateway uses the model's own ceiling instead of 16,384 tokens.
  • Tools whose parameter schema has oneOf, anyOf or allOf at the top level (one of Codex's, with the workspace-write sandbox) no longer make Claude refuse the request.

claude-nonstop 1.16.0

Choose a tag to compare

@umer-jahangier umer-jahangier released this 19 Nov 15:19

One gateway for Claude and ChatGPT, for every app that speaks either.

Any client, any line. Claude Code, the Claude desktop app, Codex and OpenAI-compatible apps such as Cursor all go through the same order of your Claude accounts, ChatGPT accounts, Claude API keys and OpenAI API keys. A request in any format goes out on whichever line is next, translated when it has to be, tools included.

Codex works with its tools on every line. Codex's current request shape (tools in an additional_tools item, grouped in namespaces, with the custom exec tool) is read in full. Tool calls come back under their own name and namespace, custom tools such as exec and apply_patch with their raw text, streaming included, and tool results reach the model. Codex is never presented to the model as Claude Code: on a Claude account it gets only the line the sign-in requires, followed by its own instructions. Requests on OpenAI keys go out exactly as Codex sent them.

Current Claude request shape. Translated requests use adaptive thinking with an effort level (thinking budgets only on older models), leave out sampling settings the API no longer accepts, and drop forced tool choice for models that refuse it. ChatGPT sign-ins drop the sampling settings their backend refuses.

SSH sessions in the desktop app. claude-nonstop ssh add <host> sets a server up so the desktop app's SSH sessions reach the gateway through a reverse tunnel the gateway keeps open.

Setup. claude-nonstop setup also points Codex at the gateway; the web UI has an Apps tab for Codex and OpenAI-compatible tools, and default models for each service in Settings.

Includes 1.15.3 to 1.15.5: Claude.ai sign-ins are kept alive (paused and limited accounts too), and a passing rate limit skips an account for seconds and tells the client to retry, instead of a billing error.

claude-nonstop 1.15.5

Choose a tag to compare

@umer-jahangier umer-jahangier released this 28 Oct 23:12

Fix: Anthropic's "This request would exceed your account's rate limit" is a short refusal on a burst of requests, not the plan running out. The gateway read it as a usage limit and set the account aside for 10 minutes; when that happened to every account, requests failed with a 402 billing error while the plans still had usage. Now such an account is skipped for a few seconds only, and when nothing else is free the gateway answers 429 with Retry-After, so Claude Code waits and retries by itself.

claude-nonstop 1.15.4

Choose a tag to compare

@umer-jahangier umer-jahangier released this 27 Oct 14:29

Every Claude.ai sign-in stays alive, so no account needs signing in again. The gateway renews a sign-in shortly before it expires, paused accounts and accounts at their limit included. A renewal is Claude Code's one-word usage check, run only when a sign-in is about to run out: about one tiny request per account per sign-in lifetime.

claude-nonstop 1.15.3

Choose a tag to compare

@umer-jahangier umer-jahangier released this 27 Oct 14:10

Fix: subscription accounts were passed over once their Claude.ai sign-in expired, so a request could fail with "no subscription account has usage left" while accounts still had usage. Claude.ai sign-ins last a few hours and Claude Code renews them when it runs; on a computer where nothing else runs Claude Code under an account (a server, say) they stayed expired. The gateway now renews an expired sign-in through Claude Code before passing the account over, and renews sign-ins about to expire every few minutes in the background.

claude-nonstop 1.15.2

Choose a tag to compare

@umer-jahangier umer-jahangier released this 26 Oct 16:20

The terminal, VS Code, and Cursor now send requests through the local gateway, and a root server no longer refuses to start Claude Code because bypass-permissions is on.

claude-nonstop 1.15.1

Choose a tag to compare

@umer-jahangier umer-jahangier released this 26 Oct 10:11

Rolls up 1.14.0 to 1.15.1: the desktop app walks your relay order too, subscription accounts first; a subscription sign-in gets requests shaped as Claude Code (OAuth beta, CLI identity, Claude Code system line), which is all it accepts; the desktop app's model list comes from your accounts, or a built-in list when none can answer; and every request on an API key goes out as plain API with no Claude Code identity, in its headers or its system prompt, so keys with plain API credit stop failing with "credit balance is too low".