Skip to content

v3.2.1 — Camofox stuck recovery, partial results in smart-extract

Latest

Choose a tag to compare

@Johell1NS Johell1NS released this 22 Oct 08:28
81c4025

Highlights

Camofox stuck recovery

  • When Camofox gets stuck after a session destroy (every POST /tabs fails with a masked 500 while /health still reports the browser as running), camofox.mjs now probes the browser with a short-timeout tab. If the probe fails, the browser is stopped and restarted, and the tab creation is retried once. If the probe works, the problem is the URL (dead domain, slow site) and nothing is restarted.
  • smart-extract skips Camofox for the remaining URLs when the restart fails (the existing escalation to CloakBrowser applies).

smart-extract

  • When interrupted (SIGTERM/SIGINT, e.g. by an outer timeout) it now prints the results already collected as mode: "partial" instead of exiting silently.

Docs

  • SKILL.md: what to do after a timeout or a partial result.

Known limits

  • Partial output works on SIGTERM/SIGINT, not SIGKILL; POSIX signal support is limited on Windows.
  • The docker restart fallback assumes the container is named camofox-browser.

How to update

npx skills update            # or: git pull

No npm install needed: dependencies are unchanged since v3.2.0.

Pull request: #38 — closes #37.