# Pylon

## Docs

- [construct](https://docs.pylon.to/cli/construct.md): pylon construct <name> creates a pylon pipeline interactively or from a template. Saves config to ~/.pylon/pylons/<name>/pylon.yaml.
- [doctor](https://docs.pylon.to/cli/doctor.md): pylon doctor checks all Pylon dependencies and configuration, reports issues and recommendations, and can interactively fix some problems.
- [jobs](https://docs.pylon.to/cli/jobs.md): List recent agent job runs, stream their logs, exec into a running container, or kill a stuck job. Job history is stored per-pylon in SQLite.
- [list](https://docs.pylon.to/cli/list.md): List all pylons, open their config in your editor, send test webhooks, or permanently delete a pipeline and its job history.
- [nexus](https://docs.pylon.to/cli/nexus.md): Launch the Nexus interactive terminal dashboard.
- [setup](https://docs.pylon.to/cli/setup.md): Run pylon setup to configure your default channel (Telegram or Slack), AI agent (Claude Code or OpenCode), and public URL. Saves to ~/.pylon/config.yaml.
- [start](https://docs.pylon.to/cli/start.md): pylon start powers up all pipelines and begins listening for webhook and cron triggers. Stop with Ctrl+C or SIGTERM. Optional name argument starts a single pylon.
- [upgrade](https://docs.pylon.to/cli/upgrade.md): Upgrade Pylon to the latest release, print the current version, generate shell tab-completion scripts, and manage the systemd service.
- [Agents](https://docs.pylon.to/concepts/agents.md): Agents are AI coding tools that run inside Docker containers. Learn how to configure Claude Code and OpenCode, set prompts, and control timeouts.
- [Channels](https://docs.pylon.to/concepts/channels.md): Channels define where Pylon posts agent results and approval requests. Supports Telegram, Slack, stdout, and generic webhooks.
- [Nexus](https://docs.pylon.to/concepts/nexus.md): Interactive terminal dashboard for managing pylons, jobs, and the daemon.
- [Pylons](https://docs.pylon.to/concepts/pylons.md): A pylon is a named pipeline that ties a trigger, workspace, agent, and channel together. Learn how pylons are configured and managed.
- [Triggers](https://docs.pylon.to/concepts/triggers.md): Triggers define what event activates a pylon. Pylon supports webhook and cron triggers today, with chat commands and API calls coming soon.
- [Workspaces](https://docs.pylon.to/concepts/workspaces.md): Workspaces define how Pylon provides a codebase to the agent. Choose from git-clone, git-worktree, local mount, or none.
- [Cron](https://docs.pylon.to/examples/cron.md): Schedule recurring AI agent runs with cron expressions.
- [Webhooks](https://docs.pylon.to/examples/webhooks.md): Set up webhook-triggered AI agent pipelines for Sentry errors, GitHub PRs, and custom services.
- [Installation](https://docs.pylon.to/installation.md): Download the Pylon binary for Linux or macOS (amd64 or arm64), verify your Docker setup, configure shell completion, and keep Pylon up to date with pylon upgrade.
- [Introduction](https://docs.pylon.to/introduction.md): Run event-driven AI coding agents on your own server. Pylon listens for webhook and cron events, sandboxes agents in Docker, and posts results to Telegram or Slack.
- [Quickstart](https://docs.pylon.to/quickstart.md): Install the daemon, connect your chat channel, build a pipeline from the Sentry template, and trigger your first AI agent run -- all from the command line.
- [Daemon](https://docs.pylon.to/running/daemon.md): Start, stop, and manage the Pylon daemon as a foreground process or systemd service.
- [Troubleshooting](https://docs.pylon.to/running/troubleshooting.md): Diagnose and fix common Pylon issues.
- [config.yaml](https://docs.pylon.to/yaml/config.md): Complete reference for the global Pylon configuration file. Defines the server port, Docker concurrency limits, and default agent runtime and notification channel at the machine level.
- [pylon.yaml](https://docs.pylon.to/yaml/pylon.md): Complete reference for the per-pylon configuration file. Defines triggers, workspaces, agent prompts with template variables, notification channels, and volume mounts for each Pylon pipeline.