MS-365-Electron
Unofficial Microsoft 365 Web Desktop Wrapper made with Electron
Could not verifysource: GitHubhomepageJavaScriptMITcommit d293b8082952
JavaScript, MIT licensed. The project labels itself: electron, microsoft, office and opensource.
Argusic could not get MS-365-Electron running. An Argusic agent installed it in 6.2 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed (563 packages, 387 MiB), Electron 35.0.3 binary present, app launches on Xvfb display :99 with --no-sandbox --in-process-gpu --enable-unsafe-swiftshader flags and stays alive until terminated.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- GPU process crash: GPU process is not usable without --in-process-gpu flag (fatal SIGILL)1 minute
- SUID sandbox helper not configured; electron --version and bare yarn start crash with SIGTRAP0.5 minutes
- dbus not available in container (non-fatal, bus.cc warnings printed to stderr)
- Install time
- 6 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- timeout 15 node node_modules/electron/cli.js --no-sandbox --in-process-gpu --enable-unsafe-swiftshader . exited with code 124 (SIGTERM by timeout) after 15 seconds, confirming the app launched and stayed alive on DISPLAY=:99. Also confirmed via background-launch: Pid was alive for 10s and killed cleanly.
- Model tokens used
- 92,921
- Exact commit tested
- d293b8082952
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
],
'test_depth': 'tier3_none',
'notes': 'No test suite exists in the package.json. The app is an Electron web wrapper for Micr…
'verified_how': 'timeout 15 node node_modules/electron/cli.js --no-sandbox --in-process-gpu --e…
'final_state': 'Dependencies installed (563 packages, 387 MiB), Electron 35.0.3 binary present,…
}
print(json.dumps(result))
\"" in /work/repo
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 6.2, "errors": [{"msg": "S…
tokens used
92,921Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 6.2 minutes, faster than the median of the 5 comparable projects Argusic has measured.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
Of the 6 electron projects Argusic has installed and timed, MS-365-Electron was the 3rd fastest to reach a running state, and 4 of 6 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.02 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.02 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ms-365-electron)Questions
- Does MS-365-Electron run?
- Argusic could not verify that MS-365-Electron runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test MS-365-Electron?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d293b8082952. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test MS-365-Electron?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MS-365-Electron take to install?
- 6.2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does MS-365-Electron need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MS-365-Electron?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does MS-365-Electron compare with the alternatives?
- Of the 6 electron projects Argusic has installed and timed, MS-365-Electron was the 3rd fastest to reach a running state, and 4 of 6 reached one at all.
- Where is the evidence for MS-365-Electron?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.