Open source (MIT) by zhengkanghua. · MIT · Tauri + Vue

ZapCmd

Desktop command launcher for speed, safety baseline, and repeatable workflows.

Search → Param → Staging → Execute. Keep behavior explicit and testable.

Download GitHub Repo Docs

Search → Param → Staging → Execute Guardrails i18n Session restore

0 Stars 0 Forks

Author: zhengkanghua / Report issues

In-browser preview

Interactive demo (simulation)

Explore search, params, staging queue, and guardrails — nothing is executed.

Token AND · Ranking · Highlight

Guardrails

Risk confirm · Injection guard

Staging queue

Batch run as a queue

User commands

JSON files · Override by id

# Example templates
git log --oneline --max-count {count}
docker stop {container}
docker system prune -f  # RISKY

Open demo View source

Use cases

Built for fast, repeatable work — without turning your terminal into a guessing game.

Daily dev ops

Launch repeatable commands with clarity: search, fill params, and run with guardrails.

Safer production actions

Stage a small queue, review what will happen, then run — reduce “oops” moments.

Command libraries

Maintain builtin + user commands with explicit sources, overrides, and schema-backed structure.

How it works

A clear, repeatable flow designed for daily developer operations.

Search

Type keywords and filter by tags.

Param

Fill required arguments before execution.

Staging

Stage multiple commands as a queue.

Execute

Run in your system terminal with guardrails.

Feature highlights

High information density, without turning into a giant settings panel.

Safety baseline

Risky command confirmation + argument injection guard.

• Confirmation for risky commands
• Argument injection guard: newline / pipe / && / ;
• Risk reason + source badge

Staging queue

Stage multiple commands and run as a batch.

• Up to 3 staged items (stable UI)
• Move up/down/remove items
• Run all in a batch (simulated)

Runtime command loading

Builtin + user command files, explicit and traceable.

• Builtin + user JSON files
• User overrides builtin on id conflict
• Schema-driven, traceable behavior

Command management

Enable/disable, filter by source file, override markers.

• Filter by source + override markers
• Enable/disable & organize
• Built for long-term command libraries

i18n (runtime switch)

zh-CN + en-US, with persistence.

• Runtime zh/en switch
• Persisted preference
• Consistent, engineering-friendly copy

Session restore

Staged queue restored after restart.

• Restore staging queue on restart
• Restore last selection + params
• Less rework, continuous flow

Interactive demo

Play with the full flow in your browser. Execution is simulated.

Command schema →

Interactive demo (simulation)

Search → Param → Staging → Execute

Type keywords to filter commands. Fill params, stage as a queue, then run.

Results · 0

Space = token AND

Selected command

Template

Params

Preview

This is a simulation. Nothing will be executed.

Staging queue

Stage multiple commands and run as a batch.

Output

Execution is simulated for presentation.

User commands (JSON files)

Drop JSON files into ~/.zapcmd/commands. If id conflicts, user command overrides builtin.

{
  "commands": [
    {
      "id": "custom-hello-win",
      "name": "Custom Hello",
      "tags": ["custom", "hello"],
      "category": "custom",
      "platform": "win",
      "template": "Write-Output \"hello from user commands\"",
      "shell": "powershell",
      "adminRequired": false
    }
  ]
}

Schema docs →

Search & safety baseline

Designed for speed in daily operations, with explicit guardrails.

1. Case-insensitive contains matching (title/description/preview).
2. Space-separated query uses token-AND (all tokens must match).
3. Risky command confirmation + argument injection guard.
4. Stage multiple commands and run them as a queue in system terminal.

# Guardrail examples
rm -rf /           # confirm
docker system prune -f  # confirm
echo hi && whoami  # blocked (injection)

Install & run

Download from GitHub Releases, verify integrity, then start launching.

GitHub Releases Issues

Windows

Download and install from GitHub Releases. If you see a system prompt on first launch, allow once.

macOS

Download from Releases. Packages are currently unsigned / not notarized — you may need manual allow on first launch.

Linux

Download from Releases and follow your distro/desktop install flow. Check release notes for supported builds.

1. Pick your platform build from the release assets.
2. Verify with SHA256SUMS from the release.
3. Check release notes for supported OS/arch and known caveats.

Run from source (dev)

Requires Node.js + Rust toolchain + Tauri prerequisites.

npm install
npm run tauri:dev

# quality gate
npm run check:all

Contributing → License → Docs →

FAQ

Short answers for the most common questions before you download.

Is ZapCmd open source?

Yes — MIT licensed. Source code lives on GitHub .

Does the website demo execute commands?

No. The interactive demo is a browser-only simulation for presentation. Nothing will be executed.

Where do user commands live?

Drop JSON files into ~/.zapcmd/commands. Schemas are available in repo docs .

What platforms are supported?

Check the available builds and release notes on GitHub Releases .

How can I contribute or report issues?

Open an issue or send a PR. See contributing guide .

Ship faster. Break less.

ZapCmd is free and open source. Star the repo, open an issue, or send a PR — small steps, real impact.

Star on GitHub Get ZapCmd