page-agent

This affects page-agent / @page-agent/llms 1.12.1. The package binds a local logger with var debug = console.debug.bind(...). When esbuild uses drop: ['console'], that expression is rewritten to var debug = void 0, so later debug(...) calls fail in production. Setting globalThis.debug does not work because debug is module-local.

Permanent fix: upgrade page-agent and @page-agent/llms to a release containing the fix for issue #621, where the logger is wrapped in a function instead of storing the bound console.debug directly.

Temporary consumer workaround: disable console dropping for the bundle. In vite.config.ts:

export default defineConfig({
  esbuild: {
    drop: []
  }
})

If the option is injected by VitePress or another preset, force it with a Vite plugin:

function keepConsole() {
  return {
    name: 'keep-console',
    configResolved(config: any) {
      if (config.esbuild && typeof config.esbuild === 'object') {
        config.esbuild.drop = []
      }
    }
  }
}

export default defineConfig({
  plugins: [keepConsole()]
})

Alternatively, patch dist/lib/page-agent-llms.js with a safe wrapper:

var debug = (...args) => {
  if (typeof console !== 'undefined' && typeof console.debug === 'function') {
    console.debug(chalk.gray('[LLM]'), ...args)
  }
}

Verify the built output no longer contains debug=void 0:

grep -n "debug=void 0" dist/assets/*.js

In Page Agent 1.12.2 on Chrome 152/macOS, inputTextElement() forces the input to blur after entering text such as weather tomorrow, so Bing does not display its suggestions. This is fixed by the PR fix(page-controller): preserve input focus. Upgrade Page Agent to a release containing that PR, or build from source with the page-controller focus fix merged. The input should remain focused after inputTextElement() runs, allowing Bing suggestions to appear. As a temporary workaround, explicitly refocus the search box after automated text entry and trigger an input event.

This occurs in v1.7.1 when a Manifest V3 service worker stalls after an extension update; Chrome/Brave can clear registered alarms during updates, preventing the background worker from restarting correctly. As a workaround, open brave://extensions (or chrome://extensions), find the extension, click the Reload button, then reopen the agent chat. If it remains stuck, toggle the extension off/on or restart the browser. The permanent fix upgrades the extension to a release containing the stalled-worker health check and service-worker alarm/update fixes.

Upgrade to a release containing the refactor(llms): rewrite model patching and deprecate temperature fix, or build from the latest main branch. The failure was caused by MiniMax M3 changing its parameter schema; the updated model patch sends parameters matching the current schema. After upgrading, remove any manually configured temperature setting because it is deprecated. If you use M3 through OpenRouter, tool calls may still fail because the model sometimes returns invalid int/string formats; that issue must be fixed by the model/provider, so use a supported model or direct MiniMax access as a workaround.

This is fixed by the core PR fix(core): make wait honor abort during setup, which closes issue #553. Previously, wait could ignore an abort while reading page update timing before its timer started. Upgrade the core package to a release containing this fix; after upgrading, aborting the signal interrupts wait promptly during setup instead of waiting for the timer to start. Verify with an already-aborted AbortController.signal passed to wait.