GateFox 1.9.0

• Codex app context items that arrive as a function_call_output with a name but no
  call_id (such as codex_apps_open_page) are rewritten once, before any provider,
  as a user context message <external_NAME>…</external_NAME>. They previously failed
  every gateway turn on Claude and other translated routes with "Responses request
  contains invalid or unsupported data". Request telemetry counts them as contextOutputs.

GateFox 1.8.9

• A provider can set cacheMissLimit (3 to 12, default 3) to allow more measured
  large cache misses in a row before the five-minute cache-safety stop. DeepSeek on
  OpenRouter builds its prefix cache asynchronously, so a fresh Flash worker could be
  paused after three cold requests although its cache was still warming. Unknown usage
  and refusals keep the two-miss limit, and other providers are unchanged.

GateFox 1.8.8

• Chat Completions servers (local Qwen through vLLM) now report every context overflow
  as context_length_exceeded, including vLLM's "max_tokens must be at least 1, got 0"
  for a prompt that fills the window exactly and overflow wording without the usual token
  counts. Codex then compacts instead of ending the turn with an upstream error.
• A conversation that keeps overflowing a Chat Completions provider stops reaching it
  after 25 consecutive refusals within ten minutes. The client gets one non-retryable
  error that asks for a fresh worker with a compact handoff, instead of trimming one
  history item per request for an hour. Any completed request resets the count.

GateFox 1.8.7

• Large chats get one additional request to recover from two measured cache misses.
  If reuse still fails, the five-minute cooldown has a fixed deadline that retries
  cannot extend. After the cooldown, one recovery request can check whether the
  provider cache is working again. Unknown cache usage and provider refusals retain
  their earlier spending limits. The error reports the remaining wait and preserves
  the chat history.

• Linux rollout checks verify external component executables through procfs,
  so minimal hosts without lsof can attest a live tunnel while mismatched
  executables and process start stamps remain pending.

GateFox 1.8.6

• Fixed a rolling-update regression introduced in 1.8.5: changing the gateway auth
  command spelling and deadline made retained native writers reject new desktop and
  SSH connections. New clients can attach using the earlier metadata only after
  proving both command aliases execute identical code for the same managed install.
  Endpoints, credential arguments, client settings and the existing writer stay exact.

GateFox 1.8.5

• Provider token authentication uses a lightweight CLI path instead of importing the
  entire provider/service stack. New auth rows permit a bounded 15-second cold start,
  and new generated command references prefer gatefox. Existing gateway and
  harness-gateway launchers remain compatible. Fresh installs select GateFox config
  and install folders and export the canonical gatefox command from all launchers.

• The sidebar brand is only GateFox. The Harness Gateway subtitle and its spoken
  accessibility label have been removed.

• The macOS app includes a Submit an issue link in the sidebar that opens
  the GateFox feedback board in the default browser.

GateFox 1.8.4

• Home Linux CI now runs successfully with portable platform checks, bounded test
  memory and deterministic asynchronous test waits. Published release versions and
  changelog entries are connected to the landing page.

• Chat-registry caches invalidate when file permissions or ownership change,
  even when the filesystem reports the same modification and change timestamps.

• gatefox chats migrate --apply is blocked only by processes on the same Codex home: an
  engine with another CODEX_HOME (such as Mission Runtime's ~/.codex-primary), a test
  run, or an inference-only gateway serve no longer stops it. A process without
  CODEX_HOME counts as ~/.codex.

GateFox 1.8.3

• The app shows GateFox once in the sidebar, with Harness Gateway beneath it.
  The window title text is hidden and the footer shows only the version.

GateFox 1.8.2

• A cancelled Claude turn whose interrupt times out no longer blocks the chat for
  an hour. Gateway deliberately closes that CLI and permits a new session on the
  next caller request, subject to the cache guard. Genuine crashes still keep
  their replay holds, and the cancelled request is never replayed automatically.

GateFox 1.8.1

• The package is @edihasaj/gatefox. The installer and app builder still accept a backend
  packaged as @edihasaj/harness-gateway or @edihasaj/subscription-gateway. The Claude
  Desktop help and errors, the Grok config marker (an old marker is replaced, never
  duplicated), the native app's type and Swift package, and the README now say GateFox.
  The README links the 1.8.0 GateFox download.

• gatefox chats migrate moves saved gateway chats from the provider id
  subscription_gateway to gatefox. Without --apply it only reports. With --apply
  it needs ChatGPT and the service stopped, rewrites the provider in each rollout's
  first line (including the engine's compressed .zst rollouts), copies
  state_5.sqlite, then moves the chat rows. --revert moves them back. Both ids stay
  registered.

• The app's rename to GateFox.app leaves Harness Gateway.app as a link to it. launchd
  keeps the loaded service's old program path until the next login, and the service plan
  stores the old app's Node path for the Claude components; without the link, a service
  restart failed with exit 78 and the Claude adapter could not start until the next login.