Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-2504GitHub issuePublicReceived

Recommend `visual-studio-code-bin` in docs instead of `vscodium-electron-bin` for better extension compatibility

Reported by aelhady03 · filed Aug 13, 2025Closed upstream on 2025-08-14 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Recommend `visual-studio-code-bin` in docs instead of `vscodium-electron-bin` for better extension compatibilityrevision 1 · captured 2026-10-04 11:27 UTC via poll

Hi,

I noticed the documentation currently suggests installing vscodium-electron-bin. While this works fine for general use, there are important differences between the available Visual Studio Code flavors on Arch that may affect the developer experience:

`code` (Code - OSS)

  • Source: Arch Linux build from Microsoft’s OSS repo
  • Marketplace: Open VSX (limited extension availability)
  • Telemetry: Disabled
  • Branding: No Microsoft branding
  • Limitations: Popular extensions like Live Share, Remote SSH, and Copilot are missing

`visual-studio-code-bin`

  • Source: Official Microsoft binary (AUR)
  • Marketplace: Microsoft Marketplace (full extension compatibility)
  • Telemetry: Enabled by default (can be disabled)
  • Branding: Microsoft branded
  • Benefits: All popular extensions work out of the box

`vscodium`

  • Source: Community OSS build
  • Marketplace: Open VSX (same limitations as code)
  • Telemetry: Removed at source
  • Branding: No Microsoft branding

Why recommend `visual-studio-code-bin` in docs?

  • Full extension support, including official Microsoft extensions
  • No need for manual sideloading of missing extensions
  • Closer experience to what most developers expect from VS Code

Proposed doc change:

Replace:

yay -S vscodium-electron-bin

with

yay -S visual-studio-code-bin
View raw text
Hi,

I noticed the [documentation](https://manuals.omamix.org/2/the-omarchy-manual/62/development-tool) currently suggests installing `vscodium-electron-bin`. While this works fine for general use, there are important differences between the available **Visual Studio Code** flavors on [Arch](https://wiki.archlinux.org/title/Visual_Studio_Code) that may affect the developer experience:

---

### **`code` (Code - OSS)**
- **Source:** Arch Linux build from Microsoft’s OSS repo  
- **Marketplace:** Open VSX (limited extension availability)  
- **Telemetry:** Disabled  
- **Branding:** No Microsoft branding  
- **Limitations:** Popular extensions like Live Share, Remote SSH, and Copilot are missing  

---

### **`visual-studio-code-bin`**
- **Source:** Official Microsoft binary (AUR)  
- **Marketplace:** Microsoft Marketplace (full extension compatibility)  
- **Telemetry:** Enabled by default (can be disabled)  
- **Branding:** Microsoft branded  
- **Benefits:** All popular extensions work out of the box  

---

### **`vscodium`**
- **Source:** Community OSS build  
- **Marketplace:** Open VSX (same limitations as `code`)  
- **Telemetry:** Removed at source  
- **Branding:** No Microsoft branding  

---

### **Why recommend `visual-studio-code-bin` in docs?**
- Full extension support, including official Microsoft extensions  
- No need for manual sideloading of missing extensions  
- Closer experience to what most developers expect from VS Code  

---

### **Proposed doc change:**
Replace:
```bash
yay -S vscodium-electron-bin

with

yay -S visual-studio-code-bin
```

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.