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. 
pylon list
Example output: 
NAME                         TRIGGER      PATH                           DESCRIPTION
my-sentry                    webhook      /my-sentry                     Sentry error triage
pr-review                    webhook      /pr-review                     GitHub PR reviewer
weekly-audit                 cron         0 9 * * 1 (Every Monday 9am)   Weekly security audit

​
pylon edit

Opens the pylon’s config file in your $EDITOR (defaults to vi). 
pylon edit <name>
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. 
pylon test <name>
pylon test <name> --payload '{"error":"divide by zero","issue":{"title":"NullPointerException"}}'
​
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: 
Sending test webhook to http://0.0.0.0:8080/my-sentry
Payload: {
  "error": "Test error from pylon test my-sentry",
  "issue": { "title": "Test issue for my-sentry" },
  ...
}

Response [202]: { "job": "a1b2c3d4" }
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 destroy <name>
Pylon asks for confirmation before deleting: 
This will delete pylon "my-sentry" and all its job history.
Are you sure? [y/N]
This is irreversible. The config file and SQLite job database at ~/.pylon/pylons/<name>/ are removed permanently.