Wootzapp AI-Enforced Enterprise Browser

hi folks, we are a couple of folks who got a grant (after we wont some opensource competitions). we have been building this for close to a year now - github.com/wootzapp/wootz-browser . If people like this, hopefully we will build a company around it. We want to build the browser capability to secure access, data redaction, copy-paste policies, etc ... all operating via SAML. today we have a lot of that working already. Our relevant pull requests are: - https://github.com/wootzapp/woot... - https://github.com/wootzapp/woot... - https://github.com/wootzapp/woot... - https://github.com/wootzapp/woot... we do this via browser agents (that we plug into device specific background process managers). Running background agents on desktop is trivial. Super hard to do on mobile. here's a quick working demo - Would love feedback & criticism. If this is something you would use (or not use), would love to hear from you. P.S. i get this question frequently - why did we start with a mobile browser and not desktop ? all-platform solution is redundant, overly complex & represents an unnecessary cost... particularly for enterprises with a large workforce that interacts with corporate portals exclusively/primarily via mobile devices.This impacts the product - for e.g. a security agent running in the background on mobile has an eventual consistency issue (because of battery optimisation features). Desktop doesnt have that issue. So your entire security apparatus must be architected to ALLOW for eventual consistency if you are focusing on mobile. Another example of mobile-specific focus: US has 2.2 million heavy truck drivers and the 1.6 million delivery truck drivers. Daily ops of these workers are intrinsically managed through mobile devices (e.g. accessing dispatch systems, interacting with Electronic Logging Device (ELD) portals for Hours of Service (HOS) compliance, customer information &cargo manifests & confirming deliveries). Not everything is API-fied and therefore cant be disrupted by mobile apps (in some ways this is why headless browser markets exists - we are pretty much adjacent to the same market). This whole space is pretty much driven by the ELD mandate of the US Govt. The FMCSA imposes strict regulations on the physical use of mobile devices, mandating hands-free operation and secure mounting to prevent distracted driving. How do you get the mobile browser to operate perfectly hands-free ? Even if you use the best voice LLMs, it still needs a browser built ground up to be driven by voice LLMs. For example, fine grained control at the renderer level (like the work we did here https://github.com/wootzapp/woot... and https://github.com/wootzapp/woot... )