Shortcuts
Shortcuts are custom commands that appear in the task detail dialog. Click a shortcut to launch an editor, open a git tool, run a script, or anything else you can do from the command line.
Global Keyboard Shortcuts
Section titled “Global Keyboard Shortcuts”These shortcuts work anywhere in the application:
| Shortcut | Action |
|---|---|
| Ctrl+Shift+P / Cmd+Shift+P | Toggle the Command Terminal overlay |
| Ctrl+F / Cmd+F | Toggle the board search bar (or focus it if already visible) |
| Escape | Close any open dialog, or clear the search query if the search bar is focused |
Standard OS shortcuts (copy, paste, select all, etc.) work as expected in the terminal.
Adding Shortcuts
Section titled “Adding Shortcuts”Open Settings > Shortcuts (per-project). You have two options:
- Presets — click the Presets dropdown to pick from built-in shortcuts for popular tools
- Add Shortcut — create a blank shortcut and fill in the label, command, and icon
Built-in Presets
Section titled “Built-in Presets”Presets are filtered by your operating system. Available categories:
- VS Code —
code "{{cwd}}" - Cursor —
cursor "{{cwd}}" - Zed (macOS/Linux) —
zed "{{cwd}}" - Sublime Text —
subl "{{cwd}}" - WebStorm —
webstorm "{{cwd}}" - IntelliJ IDEA —
idea "{{cwd}}" - Visual Studio (Windows) — auto-detects via
vswhere
- GitHub Desktop (Windows/macOS) —
github "{{cwd}}" - Fork (Windows) —
fork open "{{cwd}}" - Fork (macOS) —
open -a Fork "{{cwd}}" - GitKraken —
gitkraken -p "{{cwd}}" - TortoiseGit Log (Windows) —
TortoiseGitProc /command:log /path:"{{cwd}}" - TortoiseGit Commit (Windows) —
TortoiseGitProc /command:commit /path:"{{cwd}}"
- File Explorer (Windows) —
explorer "{{cwd}}" - Finder (macOS) —
open "{{cwd}}" - File Manager (Linux) —
xdg-open "{{cwd}}" - Windows Terminal —
wt -d "{{cwd}}" - Terminal (macOS) —
open -a Terminal "{{cwd}}" - iTerm2 (macOS) —
open -a iTerm "{{cwd}}" - Alacritty —
alacritty --working-directory "{{cwd}}"
Template Variables
Section titled “Template Variables”Shortcut commands can use these placeholders, which are replaced at runtime:
| Variable | Replaced with |
|---|---|
{{cwd}} | Task’s working directory (worktree path or project root) |
{{branchName}} | Git branch name |
{{taskTitle}} | Task title (sanitized for shell safety) |
{{projectPath}} | Root project path |
Display Options
Section titled “Display Options”Each shortcut has a display setting that controls where it appears in the task detail dialog:
| Option | Where it appears |
|---|---|
| Header | As a pill button in the dialog title bar |
| Menu | In the three-dot kebab menu |
| Both | In both locations (default) |
Use Header for shortcuts you use constantly, and Menu for less frequent ones to keep the title bar clean.
Custom Shortcuts
Section titled “Custom Shortcuts”Click Add Shortcut to create your own. Fill in:
- Label — display name (e.g., “Deploy to Staging”)
- Command — any shell command with
{{}}variables - Icon — pick from the icon palette
- Display — where it appears (header, menu, or both)
Shortcuts can be reordered by dragging.
Display Location
Section titled “Display Location”The Display setting controls where each shortcut appears in the task detail dialog:
- Header — shows as a pill button in the dialog title bar, visible at all times. Best for shortcuts you use frequently (e.g., “Open in VS Code”).
- Menu — appears only in the three-dot kebab menu. Best for less frequent shortcuts to keep the title bar clean.
- Both (default) — appears in both locations.
Team vs Personal Shortcuts
Section titled “Team vs Personal Shortcuts”Shortcuts have two scopes:
| Scope | Stored in | Shared via Git |
|---|---|---|
| Team | kangentic.json | Yes — everyone on the project sees them |
| Personal | kangentic.local.json | No — local to your machine |
Use team shortcuts for shared tools (editors, git workflows) and personal shortcuts for your own utilities.