Repository navigation
Releases
Proteus 0.1.0 — preview 6
The next public preview after preview 5. An iPhone profile now shakes hands as Safari does, new identities take their graphics card and screen from readings of real computers, and a phone profile offers a page what a real phone's browser was read to offer.
New since preview 5
- An iPhone profile shakes hands as Safari. The TLS hello, the opening of an HTTP/2 connection and the headers of a page load are the ones recorded from Safari 27.2 on an iPhone 17 Pro Max (JA4
t13d2013h2_a09f3c656075_7f0f34a4126d).GET /api/profiles/<id>/transportnow reports such a profile as agreeing. It stays off HTTP/3, where the kernel would be Chrome again. - Graphics cards read from real computers. A new Windows or Mac identity takes a card as Chrome reported it on a real computer, with that card's own WebGL limits, extensions, shader precision and WebGPU names, and a processor it was seen with: 178 cards on Windows, 16 Apple chips. Before, an identity named a card and answered with the limits of the machine it ran on. The readings are from the model Scrapfly publishes with fingerprint-generator (Apache License 2.0).
- Screens read the same way, at their pixel ratio. A screen comes with the ratio it was read at (1536 by 864 is a 1920 by 1080 panel at 125%; a Mac's is 2), and the browser is started at that ratio. Before, every profile reported the ratio of the machine it ran on. On your monitor this makes a profile's window look larger or smaller than your other programs.
- What a phone profile has is read from a phone. What the kernel offers a page was compared, name by name, with Safari on an iPhone and with Chrome on a Galaxy. An iPhone profile hides the 291 members of the global object that Safari lacks (
EyeDropper,Notification, WebUSB, WebXR, …) and the members of the interfaces pages look at first. An Android profile's global object has the same names as the phone's Chrome 158, and it hasnavigator.contacts,NDEFReaderandBarcodeDetector. - One screen, whatever the machine has.
screen.isExtendedwas true in every profile on a computer with two monitors, phones included. - A camera picture from a file. Set
cameraFileto a.y4mor.mjpegvideo and pages that are allowed the camera get it instead of this machine's camera, with a silent microphone. - Puppeteer and Playwright, checked. Connected to a running profile, neither leaves anything a page can tell it by on this kernel; the README says how to connect and what to avoid, and the check is in the repository.
- An installer for Windows.
Install Proteus.cmdputs a copy under your own programs folder with shortcuts in the Start menu and on the desktop, and an entry under "Installed apps" to remove it. No administrator rights. Proteus still runs from the unpacked folder as it is. - "Is there a newer version?" A button in the settings asks GitHub, only when pressed. Nothing is downloaded.
What it is
One folder per platform with everything needed:
- the kernel — Chromium 157.0.8103.79 with the 29 Proteus patches (and one for BoringSSL)
- the manager — stores profiles and starts the kernel
- Node.js 24 — the runtime the manager needs, so nothing has to be installed
Run it
- Download the file for your system and unpack it.
- Windows: double-click
Start Proteus.cmd(orInstall Proteus.cmdfirst). Linux:./start-proteus.sh. - Create a profile and press Start.
Then see how the profile looks to a website: https://sheekovic.github.io/Proteus-Browser/test.html
| File | For |
|---|---|
Proteus-0.1.0-preview.6-win-x64.zip |
Windows 10 and 11, 64-bit |
Proteus-0.1.0-preview.6-linux-x64.tar.xz |
Linux, 64-bit |
SHA256SUMS.txt |
checksums of the two files |
Know before you run it
- Not code-signed. Windows shows an "unknown publisher" warning: choose More info, then Run anyway.
- Not an optimised "official" build. It is somewhat slower than a retail browser.
- Profiles made with an earlier preview keep what they had. The new cards, screens and pixel ratio are for new identities; give an existing profile a new identity to get them. An iPhone profile made before keeps the Safari 18.5 or 18.6 it claimed.
- A generated identity is a plausible computer, not a record of one. Card and screen are each read from a real computer but drawn separately, and memory and fonts are chosen from what is common. Linux identities still name a card without its capabilities.
- An iPhone profile is still Chromium underneath. 248 members of less looked-at interfaces are not hidden (the kernel's configuration has no room), the 99 names Safari has and the kernel lacks cannot be added, and
navigator.gpuis hidden although Safari has it. - The installer's entry under "Installed apps" was not run on the machine this was made on; installing, updating over an install and removing were tried with the places redirected to a test folder.
- Tested on few machines: one Windows 11 PC and one Linux server.
- The kernel is built with the same video and audio formats as retail Chrome, including H.264 and AAC.
The limits of what Proteus does are listed in the README.
Checked before publishing
- Kernel tests on the Linux build: all 18 suites pass (314 checks).
- Windows kernel: the end-to-end test against the real kernel passes (87 checks), with the hidden interfaces, the single screen and both handshakes among them. Manager tests: 126 passing.
- Detection sites (sannysoft, browserscan, pixelscan, iphey, areyouabot) for Windows, Android and iPhone profiles on the Windows kernel: no verdict worse than expected. pixelscan gave no verdict for the iPhone profile. sannysoft's "Permissions" row fails for the iPhone profile because it needs
Notification, which Safari on an iPhone was read not to have in a page; whether a real iPhone shows the same row was not looked at. - Windows bundle, unpacked to a fresh folder and run with its own Node.js: found its kernel, read its version as 157.0.8103.79, answered the update check, and started a Windows, an iPhone and an Android profile, each reporting an agreeing handshake.
- Not run for this preview: the Linux bundle as unpacked (its kernel is the one the tests ran on), and the public test page score.
Use it for identities you are entitled to have: several accounts of your own, testing, research, privacy.
Proteus 0.1.0 — preview 5
The next public preview after preview 3 (preview 4 was built but not published). The kernel is now the Chrome release nearly everyone runs, and a profile's network handshake matches the browser it claims to be.
New since preview 3
- The kernel is Chrome 157.0.8103.79. Earlier previews were built from 158.0.8127.37, which was only at the start of its stable rollout: 157.0.8103.79 was what 99% of Chrome users had. A browser on a version almost nobody has yet stands out by that alone.
- The handshake is stock Chrome's. Earlier kernels sent one TLS extension more than Chrome does (an experiment that non-Google builds have on). It is off now: a profile's TLS hello (JA4
t13d1517h2_8daaf6152771_cb7bf5808d99) and HTTP/2 opening are the same as stock Chrome 157.0.8103.79 measured on the same machine. - A report of it.
GET /api/profiles/<id>/transport(and thetransport_reportMCP tool) returns what the profile claims, what the kernel produced just now, and whether the two agree. - The version follows the kernel. The manager reads the version from the kernel itself. A Chrome profile made with an earlier preview is moved to 157 the next time it starts: only the version changes, the device stays the same.
- Microphones, cameras and speakers, battery and connection type come from the profile, not from the computer it runs on.
- The proxy exit is shown in the profile list as well as on start, and a running profile's exit is watched for changes.
- Ready-made setups: ten device presets to create a profile from, and
deviceMemoryheld to values the claimed browser can report.
What it is
One folder per platform with everything needed:
- the kernel — Chromium 157.0.8103.79 with the 27 Proteus patches
- the manager — stores profiles and starts the kernel
- Node.js 24 — the runtime the manager needs, so nothing has to be installed
Run it
- Download the file for your system and unpack it.
- Windows: double-click
Start Proteus.cmd. Linux:./start-proteus.sh. - Create a profile and press Start.
Then see how the profile looks to a website: https://sheekovic.github.io/Proteus-Browser/test.html
| File | For |
|---|---|
Proteus-0.1.0-preview.5-win-x64.zip |
Windows 10 and 11, 64-bit |
Proteus-0.1.0-preview.5-linux-x64.tar.xz |
Linux, 64-bit |
SHA256SUMS.txt |
checksums of the two files |
Know before you run it
- Not code-signed. Windows shows an "unknown publisher" warning: choose More info, then Run anyway.
- Not an optimised "official" build. It is somewhat slower than a retail browser.
- An iPhone profile still shakes hands as Chrome does, not as Safari: the report says so (
agrees: false). Changing that needs work in the kernel's network code. - Tested on few machines: one Windows 11 PC and one Linux server.
- The kernel is built with the same video and audio formats as retail Chrome, including H.264 and AAC.
The limits of what Proteus does are listed in the README.
Checked before publishing
- Kernel tests on the Linux build: all 16 suites pass (272 checks), as they did on the 158 kernel.
- Windows kernel: the end-to-end test against the real kernel passes; the nine Chrome presets each claim 157.0.8103.79 and produce stock Chrome's handshake. Manager tests: 110 passing.
- Windows bundle, unpacked to a fresh folder and run with its own Node.js: found its kernel, read its version as 157.0.8103.79, created a profile, reported an agreeing handshake, started and stopped it (headless).
- Not run for this preview: the Linux bundle as unpacked (its kernel is the one the tests ran on), and the public test page score.
Use it for identities you are entitled to have: several accounts of your own, testing, research, privacy.
Proteus 0.1.0 — preview 3
The third preview. The browser is now called Proteus, and three of the limits listed with the earlier previews are gone.
New since preview 2
- It is called Proteus. The window title, the menus, the settings and "about" pages, and the name Windows shows for the program, in every language the interface has. What websites are told is unchanged: like every Chromium-based browser, the brand list names Chromium.
- Windows: the network sandbox is back on. Earlier previews started the kernel with its network service sandbox off, because with it on the first page never loaded. The cause is found: that sandbox could not read a kernel unpacked from an archive. Proteus now grants it access to the kernel folder before a start (no administrator rights needed).
- Phone profiles have a phone's fonts. An Android profile shows Roboto and Noto and an iPhone profile shows Helvetica Neue and Menlo, instead of the fonts of the computer it runs on.
- Linux: a way through the sandbox restriction. On systems that restrict unprivileged user namespaces (Ubuntu 23.10 and later) the start script says so and names the one command that fixes it:
sudo ./linux-sandbox.sh --install.
What it is
One folder per platform with everything needed:
- the kernel — Chromium 158.0.8127.37 with the 25 Proteus patches
- the manager — stores profiles and starts the kernel
- Node.js 24 — the runtime the manager needs, so nothing has to be installed
Run it
- Download the file for your system and unpack it.
- Windows: double-click
Start Proteus.cmd. Linux:./start-proteus.sh. - A page opens in your usual browser. Create a profile and press Start.
Then see how the profile looks to a website: https://sheekovic.github.io/Proteus-Browser/test.html
| File | For |
|---|---|
Proteus-0.1.0-preview.3-win-x64.zip |
Windows 10 and 11, 64-bit |
Proteus-0.1.0-preview.3-linux-x64.tar.xz |
Linux, 64-bit |
SHA256SUMS.txt |
checksums of the two files |
Know before you run it
- Not code-signed. Windows shows an "unknown publisher" warning: choose More info, then Run anyway. Antivirus software may scan the browser for a minute on first start.
- Not an optimised "official" build. It is somewhat slower than a retail browser.
- Linux: the
--installstep oflinux-sandbox.shadds an AppArmor profile in the form Ubuntu uses for Chrome. Its detection was tested on Ubuntu 24.04; the install step itself was not run before release. Please report how it goes. - Tested on few machines: one Windows 11 PC and one Linux server.
- The kernel is built with the same video and audio formats as retail Chrome, including H.264 and AAC.
The limits of what Proteus does are listed in the README.
Checked before publishing
- Windows bundle, unpacked to a fresh folder: found its kernel, set up the sandbox access by itself, started a profile with the network sandbox on, window titled "… - Proteus", 28/28 on the public test page.
- Linux bundle: unpacked on a clean path, a profile started and answered with its own identity; the sandbox helper detected the restriction on Ubuntu 24.04.
- Kernel tests on Windows: 208 passing; end-to-end test: 57 of 57. Manager tests: 52 passing.
Use it for identities you are entitled to have: several accounts of your own, testing, research, privacy.