🚀 QuickFire
Execute VS Code commands and nested workflows instantly with a single keystroke—no Enter required.

QuickFire allows you to create a customized menu of actions that you can trigger instantly. Unlike the default QuickPick, QuickFire executes the command as soon as you press the assigned key—no Enter required.
✨ Features
- 🚀 Single Keystroke Execution: Press a key, and the command fires immediately.
- 📂 Nested Menus: Organize your complex workflows into logical sub-menus.
- ⚙️ Argument Support: Pass strings, objects, or even
vscode:// URIs directly to commands.
- 🔙 Rapid Navigation: Use
Backspace to quickly navigate back up through nested menus.
- ⌨️ Keyboard Centric: Designed for power users who want to keep their hands on the home row.
🚀 Getting Started
- Install the extension from the VS Code Marketplace.
- Configure your actions in
settings.json (see Configuration below).
- Bind the command
QuickFire: Show actions (quickfire.showQuickActions) to a convenient keyboard shortcut like Ctrl+Alt+Q or Cmd+Shift+Space.
⚙️ Configuration
Open your user settings.json and add your custom actions to the quickfire.actions array.
Example Configuration
{
"quickfire.actions": [
{
"key": "f",
"description": "File operations",
"actions": [
{
"key": "n",
"description": "New File",
"command": "explorer.newFile"
},
{
"key": "s",
"description": "Save All",
"command": "workbench.action.files.saveAll"
}
]
},
{
"key": "g",
"description": "Open GitHub",
"command": "vscode.open",
"args": "https://github.com/dani84bs/quickfire"
},
{
"key": "t",
"description": "Terminal",
"command": "workbench.action.terminal.toggleTerminal"
}
]
}
Action Properties
| Property |
Type |
Description |
key |
string |
The single character that triggers the action. |
description |
string |
A brief label shown in the menu. |
command |
string |
The VS Code command ID to execute (e.g., workbench.action.findInFiles). |
args |
any |
(Optional) Arguments to pass to the command. |
actions |
array |
(Optional) A list of sub-actions to create a nested menu. |
🤝 Contributing
Contributions are welcome! Please feel free to submit a Pull Request or open an issue on GitHub.
🚀 Publishing to Open VSX
To publish the extension to the Open VSX registry manually, follow these steps:
- Log in / Link Eclipse Account: Log in to Open VSX Registry and connect your GitHub account to your Eclipse account.
- Accept the Publisher Agreement: Go to your settings page and agree to the publisher agreement.
- Generate an Access Token: Under Settings > Access Tokens, generate a new token.
- Publish: Run the following command from the root directory of the repository (replace
YOUR_TOKEN_HERE with your access token, making sure not to save the token in any configuration files):
OVSX_PAT=YOUR_TOKEN_HERE npm run publish:open-vsx
📄 License
This project is licensed under the MIT License.
Developed with ❤️ by Daniele Trainini