fresh-upstream

Extract a fresh unpatched Claude Desktop bundle from Claude.msix using 7z and asar.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill fresh-upstream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fresh-upstream
Source: https://github.com/patrickjaja/claude-desktop-bin/tree/main/.claude/skills/fresh-upstream
Command: npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill fresh-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a clean, unpatched baseline of the latest upstream Claude Desktop release so patch work and reverse-engineering can compare against the real original bundle instead of a modified build.

Core Features & Use Cases

  • Version awareness: Checks the tracked upstream version against the latest published release.
  • Fresh extraction: Downloads or refreshes the Claude.msix package, wipes stale local extracts, and unpacks the app into a temporary workspace.
  • Patch analysis support: Prepares files for inspection of app.asar contents, renderer bundles, localization assets, and other upstream resources.
  • Use case: A maintainer uses it before writing or auditing patches to confirm exactly what changed in the newest Claude Desktop release.

Quick Start

Ask the skill to fetch the latest Claude Desktop msix, remove any stale extracts, and produce a fresh unpatched bundle in ./tmp for analysis.

Frequently Asked Questions about fresh-upstream

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract a clean Claude Desktop msix bundle for patch analysis?

To extract a clean Claude Desktop msix bundle for patch analysis, the skill downloads the latest Claude.msix, wipes stale local extracts, and unpacks the app into a temporary workspace using 7z and asar without invoking patching build scripts.

Why do I need an unpatched upstream Claude Desktop bundle for reverse engineering?

An unpatched upstream Claude Desktop bundle provides a pristine baseline to compare local modifications against the original release. Maintainers use it to audit version drift and confirm exactly what changed before writing or applying update patches.

How do I prepare a fresh Claude Desktop workspace on Linux without running build scripts?

To prepare a fresh Claude Desktop workspace on Linux without build scripts, request the skill to fetch the latest msix, remove stale local extracts, and unpack the unpatched app contents into ./tmp for direct inspection of renderer bundles and localization assets.

Does this upstream bundle extraction tool check for the latest Claude Desktop release version?

Yes, the extraction tool checks the tracked upstream version against the latest published release before downloading. This version awareness ensures you are analyzing the most recent Claude Desktop msix package available for your patch comparison workflow.

Can I inspect app.asar contents directly from the extracted Claude Desktop package?

Yes, you can inspect app.asar contents directly because the skill unpacks the Claude.msix using 7z and asar. This prepares files for immediate inspection of renderer bundles, localization assets, and other upstream resources in the temporary workspace.

What limitations exist when using 7z and asar to unpack a Claude.msix bundle?

The process strictly extracts files without executing any patching build scripts, meaning it only provides a static unpatched baseline. It focuses on producing a pristine bundle in ./tmp for analysis rather than preparing a runnable or modified application environment.