DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to edit ZCode, DSH or WorkBuddy config files with backups with Uni Switch

View the real config file for another client, edit it inside the app, and keep a backup before saving.

Credentials. Config files for these clients can contain API keys, so do not paste the file contents into shared chats or tickets.

Who it is forA user of ZCode, DSH (DeepSeek Harness) or WorkBuddy who wants to set up the client from its own config file and revert safely if something breaks.

The problemHand-editing a client config risks overwriting changes made elsewhere or breaking the file with no easy way back.

The outcomeThe client config is updated after validation and backup, and the user knows to restart the client.

What you need first

  • A desktop computer running Windows, Linux or macOS
  • An API address and API Key from your provider
  • Codex or Claude Code installed on the same machine
  • For building from source: Node.js 20 or newer, Rust 1.89 or newer, and the platform build tools listed in the README

Steps

  1. Open Uni Switch and select ZCode, DSH or WorkBuddy.
  2. Use the one-click setup to write the native config, or open the config file to edit it manually.
  3. Edit the file in the app and save. The app validates the file and makes a backup first.
  4. If the file was changed outside the app, review the conflict warning before you confirm an overwrite.
  5. Restart the client as the app prompts, then check the new settings.

Prompt for your agent

Using the uni-switch project at github.com/dieqiyun/uni-switch, show the current config path for the client <client-name> and the backup location created before any edit. Expected output: the config path and a backup file name. Verify that the backup exists before saving any change.

Caveat. Automatic client restart is available only on Windows, so on macOS and Linux you must restart the client yourself after saving.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page