Skip to main content
These commands let you inspect, modify, test, and remove the pipelines you’ve constructed. Use them day-to-day to manage your Pylon setup without touching config files directly.

pylon list

Lists all constructed pipelines with their trigger type, path or schedule, and description.
Example output:

pylon edit

Opens the pylon’s config file in your $EDITOR (defaults to vi).
The file is at ~/.pylon/pylons/<name>/pylon.yaml. The daemon hot-reloads it automatically after you save.

pylon test

Sends a mock HTTP POST to the pylon’s webhook endpoint. Requires pylon start to be running.
name
string
required
The pylon to test.
--payload
string
A custom JSON string to use as the webhook body. If omitted, Pylon generates a default mock payload containing repo, ref, error, and issue fields.
Example output:
Use --payload with a real payload captured from your external service to verify your prompt templates expand correctly.

pylon destroy

Permanently deletes a pylon’s config directory and all its job history.
Pylon asks for confirmation before deleting:
This is irreversible. The config file and SQLite job database at ~/.pylon/pylons/<name>/ are removed permanently.