qclaw-asar-hotfix

Patch QClaw.app app.asar bundles to enable DEV_MODE-gated invites on localhost.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/tangchunwu/skill-hub --skill qclaw-asar-hotfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qclaw-asar-hotfix
Source: https://github.com/tangchunwu/skill-hub/tree/main/skills/custom/app/qclaw-asar-hotfix
Command: npx skills add https://github.com/tangchunwu/skill-hub --skill qclaw-asar-hotfix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Patch packaged QClaw.app frontends by injecting safe fixes to enable DEV_MODE-gated invites only on localhost and to bypass in production for testing older versions.

Core Features & Use Cases

  • Deterministic patching script patches the front-end bundles inside app.asar
  • Restores visibility of 'other' and 'system-config' model providers in UI for older releases
  • Backups originals and validates patches before re-pack and optional install

Quick Start

Patch the QClaw app by running the patch_qclaw_asar.py script on your target app to generate a patched app.asar.

Frequently Asked Questions about qclaw-asar-hotfix

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

FAQPage Schema
How do I enable DEV_MODE in a packaged QClaw app?

To enable DEV_MODE in a packaged QClaw app, you patch the front-end bundles inside the app.asar file. A deterministic patching script injects safe fixes that gate invites specifically for localhost testing.

How do I restore missing model providers in an older QClaw frontend?

To restore missing model providers in a QClaw frontend, you apply a patch to the app.asar. This update makes the 'other' and 'system-config' options visible again in the vendor dropdown for older app versions.

What is the safest way to modify an app.asar file for frontend testing?

The safest way to modify an app.asar file is to use a patching script that automatically backs up the original file and validates all changes before re-packaging and applying updates.

Does patching the QClaw app.asar permanently change my application?

Patching the QClaw app.asar does not permanently destroy your original application because the script creates backups of the original app.asar before applying updates, allowing for reversion.

Why are 'other' and 'system-config' model providers hidden in my QClaw vendor dropdown?

The 'other' and 'system-config' model providers are hidden in your QClaw vendor dropdown due to version-specific UI gating. Applying a targeted app.asar patch restores visibility of these options for older releases.