Few years ago, to implement E2E encryption. I had to do something unconventional. I rewrite part of crypto framework of Apple. Today an AI out of nowhere found out a better way to do it by tricking apple framework. It greatly improve the performance of my updater. Thanks random dude from Github

🚀 Codex CLI 0.141.0 is out! 🔒 E2E-encrypted Noise relay for remote executors 🖥️ Native shells and dirs in cross-platform execution 🔌 Per-thread MCP activation and plugin marketplace Changelog:

# Cursor Features and Practical Usage 🌐 "Just look at the screen and fix it" is now something the AI agent can literally do. Cursor's Browser tool hands the agent control of a browser, covering everything from E2E testing to design-to-code in one loop. 🏷️ Title: Browser Tool 🔗 URL: 📘 Overview The Browser tool lets Cursor's agent directly drive a browser inside the IDE. It can navigate to URLs, click, fill forms, capture screenshots, and inspect console logs and network traffic on its own. The key benefit is closing the loop between visual verification and code changes within a single agent run. ⚙️ How It Works The browser runs as a secure web view controlled via an MCP server extension, and the agent can: ・Navigate: visit URLs, follow links, move through history, reload pages ・Interact: click, double-click, right-click, hover, fill and submit forms ・Inspect visually: capture screenshots as images to verify layout and UI ・Debug: read JavaScript console logs and errors, plus network traffic Logs are written to files and the agent selectively reads only the relevant lines, so it handles huge outputs efficiently. Automatic dev-server detection prevents starting duplicate servers. Authentication cookies, localStorage, sessionStorage, and IndexedDB persist across sessions in the same workspace, so login state survives between verification runs. 🛠️ Practical Usage The design sidebar lets you design and code at the same time. You can visually adjust element positioning, flex direction, alignment, grid layouts, width/height/padding/margin, colors, gradients, shadows, opacity, and border radius with sliders. When the look matches your vision, click `Apply` and an agent translates the visual changes into appropriate code. You can also select multiple elements and apply changes together via hot-reload. Execution safety is governed by approval modes: `Manual approval` (recommended), `Allow-listed actions`, and `Auto-run`. 💡 Use Cases ・E2E testing: fill forms with test data, validate error messages, capture screenshots for visual regression ・Design-to-code: import Figma mockups and convert to pixel-perfect HTML/CSS ・Accessibility audits: check contrast ratios, semantic HTML, ARIA labels, and keyboard navigation against WCAG ⚠️ Caveats The origin allowlist provides best-effort protection only. Link navigation and client-side redirects from allowed domains may still reach non-allowed origins, and manual user navigation bypasses the allowlist entirely. Avoid `Auto-run` with untrusted code, and review allowlist configurations regularly. #Cursor# #AICoding#

At the top of my AGENTS.md: - NEVER write unit tests after you write code. - Highly prefer E2E tests as the sole testing mechanism. Use them to verify complex features work. At the end of E2E tests, produce a verifiable and repeatable artifact. - If you must test a system in isolation, FIRST write all the ways it could fail, THEN write the code.

Muse is quite good. I recognize the complexity of what I am asking for but I'd like it to be on my side of the wall on all e2e encrypted matters. It is too under-permissed otherwise. If I have to move my entire compute into Meta's Secure VM, I will.