Command Palette

Current builds use Textual’s command palette, opened with Ctrl+P. It is the main way to run tab switches, page actions, import/export operations, replay actions, and system commands such as Help.

Examples in this page omit a leading : because the current UI opens a palette. If you paste older :rename-style commands, piespector still parses them.

Palette keys

• Ctrl+P opens the palette
• Tab accepts the highlighted completion
• Enter runs the selected command
• Esc closes the palette

Quoting

Commands accept quoted names and paths:

rename "Books API v2"
import "My Collections.json"
mv "Target / Auth Folder"

Use quotes when names or filesystem paths contain spaces.

Completion

Command completion

Suggestions are context-sensitive. The palette only suggests commands that make sense for the current tab and Home context.

Path completion

Tab completes:

• filesystem paths for import PATH
• filesystem paths for export PATH
• Home move and copy destinations for mv PATH and cp PATH

Commands available on every main page

• home
• env
• history

Home commands

Home with no selected collection, folder, or request action

• new
• new collection NAME
• import PATH
• export PATH
• history
• env

With a request selected in the sidebar

• new
• new collection NAME
• new folder NAME
• import PATH
• export PATH
• edit
• rename NAME
• cp PATH
• mv PATH
• del
• history
• env

With a folder selected in the sidebar

• new
• new collection NAME
• new folder NAME
• import PATH
• export PATH
• rename NAME
• cp PATH
• mv PATH
• del
• history
• env

With a collection selected in the sidebar

• new
• new collection NAME
• new folder NAME
• import PATH
• export PATH
• rename NAME
• cp
• del
• history
• env

Inside Home request sections or response focus

• history
• env

Home command notes

• new creates a request
• new folder NAME only makes sense when a collection or folder is selected
• cp on a collection does not take a destination path
• import PATH on Home imports collections as new copies
• export PATH exports all collections unless a collection is selected
• request-editing contexts intentionally reduce the command list to tab-switch actions
• sending is a key-driven action on Home with s, not a palette command

Env commands

• home
• env
• history
• new NAME
• rename NAME
• import PATH
• export PATH
• set KEY=value
• del
• del KEY
• edit

Env command notes

• new NAME creates a new env set
• rename NAME renames the selected env set
• set KEY=value writes a key into the current env set
• del KEY deletes an env variable by name
• del deletes the selected env set
• import PATH creates new env set(s) instead of merging into the selected set
• export PATH writes the current env pairs
• env import/export commands are key/value oriented; Description and Sensitive are part of app storage, not .env export files

History commands

• home
• env
• history
• replay

History command notes

• replay is only available on History
• replay uses the selected history entry
• r is also the direct replay key on History

Error and usage behavior

If a command is valid but incomplete, piespector reports a usage hint such as:

• Usage: import PATH
• Usage: rename NAME
• Usage: mv PATH

If quoting is broken, command parsing reports:

• Unclosed quote in command.

If a destination cannot be resolved for mv or cp, piespector reports one of:

• Destination not found.
• Destination is ambiguous. Use a fuller path.

Commands that existed in older docs but are not current palette commands include help, ?, q, send, and close.

quit and exit still quit the app if you type them directly, but they are not suggested as normal page commands.