KitchenSink4Web 1.0.4

A security and reliability release.

• Confirmations now need an explicit Allow. Every confirmation prompt asks for a required choice between Don't allow and Allow, and only Allow lets the action go ahead. An answer with nothing chosen, a cancelled or timed-out prompt, or a reply sent by moving on in the chat now refuses. In some clients with automatic approval turned on, high-risk actions such as payments, sign-ins and deletions could previously go ahead without anyone choosing; they are now refused, and a session that answers instantly with nothing chosen is treated as unattended and refuses without asking. Routine actions can still be approved in advance with KS4WEB_PREAUTH, and routine prompts offer an optional Remember box (off by default) that lasts 30 minutes. KS4WEB_REMEMBER=off removes it.
• Prompts that some clients could not display now appear.
• The server keeps working when a client never reads its error output. Log output is drained by the server itself, so it no longer stops answering, hangs at exit or blocks the browser. Log lines are now one short line each.
• Documentation, test fixtures and package metadata were updated; the metadata now lists KitchenSink4AI as the author.

Install or upgrade with pip install -U kitchensink4web, or use uvx kitchensink4web. Claude Desktop users can install the .mcpb file attached below. See the README for every install route.

KitchenSink4Web 1.0.3

• Documentation and listing only. The MCP Registry entry moves to the io.github.KitchenSink4AI namespace and is published from the release workflow. The bundle manifest carries contact details and the product homepage. No change to tools or behaviour.

KitchenSink4Web 1.0.2

• Product page, README, and install buttons now say Community Edition, with a Community Edition badge under the product name.
• LICENSE made byte-exact to the canonical GNU AGPL-3.0 text; NOTICE.md updated to match.
• User-visible strings use US spelling (license). No changes to tool behaviour.

KitchenSink4Web 1.0.1

• The server now says what it is. Its instructions line, the one block of its own prose a connected agent reads, opens by naming KitchenSink4Web, its PyPI package, and the KitchenSink4AI suite, and a new get_server_info tool answers the same question on request: product and package names, version, homepage and repository, the sibling servers, the tool surface registered in this process, and the test figures measured for this release. It is in the lite core, so it is present under the shipped read-only default, and its counts come from the live registry rather than from anything typed by hand.
• survivors() asked a creation time whether a process was alive, and a creation time answers a different question. Windows keeps OpenProcess succeeding on an exited process for as long as any handle to it remains, and the browser driver holds one for every browser it launched, so a killed browser kept counting as a survivor and browser_alive() reported a live browser after every process it owned was dead. The wait object answers liveness now; the creation time keeps its own job, which is defeating PID reuse.
• Published figures restamped from a live measurement: 20 lite tools, 53 with every pack loaded, and 2,066 tests of which 733 drive a real browser. The pack roster in docs/llms.txt was two waves behind and now lists what the server registers.

KitchenSink4Web 1.0.0

• First public release: a browser built for AI agents. Budgeted page reads with an honest account of what went unread, real-browser lanes, a consent ladder that cannot be talked out of payments or credentials, structured extraction with named evidence, monitors, workflows, session transfer, and an accessibility audit. Read-only out of the box.