BasicShell 0.4.6

Download: one of two, each with BasicShell.app inside: unzip, move it to Applications.

• BasicShell-0.4.6.zip: BasicShell with what is new below under "In both builds".
• BasicShell-0.4.6-claude.zip: the same with Claude's tools. The plain one has no part of them.

It is self-signed, not an Apple Developer ID, so the first time macOS refuses to open it: open it once, then System Settings › Privacy & Security › Open Anyway.

Requires: macOS 27 on Apple silicon.

In both builds

• Site information: the lock at the left of the address (an "i" where the page isn't secure) brings up how the page was fetched and by whose certificate (with the system's own viewer), what the site was allowed (location, notifications; each can be taken back), what it keeps on this Mac (its cookies and stored data, which can be removed), and its zoom.
• Zoom is kept by site: ⌘+, ⌘− and the panel's buttons set it, and it comes back whenever a tab goes to the site. It is never remembered from a private tab. Settings › Tabs lists the sites that have one.
• A Develop menu in the menu bar, as in Safari, out of sight until Settings › General turns it on: the Web Inspector, its console, a page's source and resources, picking an element on it, recording its timeline; the inspector of an extension's background page; the user agent a tab introduces itself with (an iPhone, an iPad, Chrome, Firefox, or one typed in, which is remembered), a phone's, a tablet's or a typed-in size, a light or dark look; a tab without JavaScript, images or styles, without the same-origin policy, or without the limits on what a file may read; emptying the caches; WebKit's experimental features.
• A Debug menu beside it, likewise: WebKit's internal debugging features (compositing borders, repaint counters, the resource usage overlay…), the web process's number and crashing it, the page as a web archive. What is switched in either is kept and put on the pages opened after; "Reset All WebKit Features to Defaults" takes it back. Safari's own Debug menu has more (iCloud, CloudKit, AutoFill); that is Safari's, not WebKit's.
• View › Debug Log is now Develop › Debug Log (Settings › General still opens it).

In the build with Claude's tools (4 tools were added to the 38 of 0.4.5, 42 in all)

• site_info: whether the connection is secure, the certificate's holder, issuer and expiry, what the person allowed the site, its cookie count, the zoom, how the tab is set. Needs your "read" for the site.
• Behind Developer tools: render (a tab without its JavaScript, images or styles; put back when Claude lets the tab go), source (the page as the site sent it, before its scripts ran; values of password and card fields replaced by [hidden]) and features (WebKit's experimental and debugging features, the same as the menus'; a change lasts while Claude is connected, and whatever touches privacy or security stays yours).
• extensions can also say the problems WebKit reports for an extension, and, with Developer tools on, what its background page writes to the console. It can't run a script in one.
• resize takes any user agent, not only a phone's or a tablet's.
• Settings › Claude has a new switch, "WebKit features", under Developer tools. "Bypass permissions" turns it on with the rest; privacy and security features and the same-origin and file restrictions are not Claude's even then.

After updating, quit and reopen BasicShell, and start a new chat in Claude if you use the build with its tools: a chat reads the tools when it starts. Adding BasicShell to Claude Code or the Claude app once is enough. The Develop and Debug menus are off until Settings › General turns them on.

SHA-256: BasicShell-0.4.6.zip b382d1fb372dd538dc068a9b92e91857a69e33604858dc9f21fe2d673818c0f2, BasicShell-0.4.6-claude.zip abddff1b64ecf4d2462d3ca505e021d99bcc6557917cd30a36a465aa67a41610