rgb-cln/doc/developers-guide/plugin-development.md

---
title: "Plugin Development"
slug: "plugin-development"
excerpt: "Customise your Core Lightning node by leveraging its powerful modular architecture via plugins."
hidden: false
createdAt: "2022-12-09T09:56:22.085Z"
updatedAt: "2023-02-06T03:21:36.614Z"
---
Plugins are a simple yet powerful way to extend the functionality provided by Core Lightning. They are subprocesses that are started by the main `lightningd` daemon and can interact with `lightningd` in a variety of ways:

- **[Command line option passthrough](doc:a-day-in-the-life-of-a-plugin)** allows plugins to register their own command line options that are exposed through `lightningd` so that only the main process needs to be configured. Option values are not remembered when a plugin is stopped or killed, but can be passed as parameters to [`plugin start`][lightning-plugin].
- **[JSON-RPC command passthrough](doc:json-rpc-passthrough)** adds a way for plugins to add their own commands to the JSON-RPC interface.
- **[Event stream subscriptions](doc:event-notifications)** provide plugins with a push-based notification mechanism about events from the `lightningd`.
- **[Hooks](doc:hooks)** are a primitive that allows plugins to be notified about internal events in `lightningd` and alter its behavior or inject custom behaviors.
doc: Add guides and GitHub workflow for doc sync This PR: - adds all the guides (in markdown format) that is published at https://docs.corelightning.org/docs - adds a github workflow to sync any future changes made to files inside the guides folder - does not include API reference (json-rpc commands). Those will be handled in a separate PR since they're used as manpages and will require a different github workflow Note that the guides do not exactly map to their related files in doc/, since we reorganized the overall documentation structure on readme for better readability and developer experience. For example, doc/FUZZING.md and doc/HACKING.md#Testing are merged into testing.md in the new docs. As on the creation date of this PR, content from each of the legacy documents has been synced with the new docs. Until this PR gets merged, I will continue to push any updates made to the legacy documents into the new docs. If this looks reasonable, I will add a separate PR to clean up the legacy documents from doc/ (or mark them deprecated) to avoid redundant upkeep and maintenance. Changelog-None 2023-04-22 14:21:44 +01:00			`---`
			`title: "Plugin Development"`
			`slug: "plugin-development"`
			`excerpt: "Customise your Core Lightning node by leveraging its powerful modular architecture via plugins."`
			`hidden: false`
			`createdAt: "2022-12-09T09:56:22.085Z"`
			`updatedAt: "2023-02-06T03:21:36.614Z"`
			`---`
			Plugins are a simple yet powerful way to extend the functionality provided by Core Lightning. They are subprocesses that are started by the main `lightningd` daemon and can interact with `lightningd` in a variety of ways:

			- [Command line option passthrough](doc:a-day-in-the-life-of-a-plugin) allows plugins to register their own command line options that are exposed through `lightningd` so that only the main process needs to be configured. Option values are not remembered when a plugin is stopped or killed, but can be passed as parameters to [`plugin start`][lightning-plugin].
			`- [JSON-RPC command passthrough](doc:json-rpc-passthrough) adds a way for plugins to add their own commands to the JSON-RPC interface.`
			- [Event stream subscriptions](doc:event-notifications) provide plugins with a push-based notification mechanism about events from the `lightningd`.
			- [Hooks](doc:hooks) are a primitive that allows plugins to be notified about internal events in `lightningd` and alter its behavior or inject custom behaviors.