Do plugins have to be AGPL in Logseq?

Customization
1

Do plugins have to be AGPL in Logseq? From what I understand, it’s a grey area in the AGPL, so I was wondering how the core team was interpreting it. In other words, can I develop a plugin under a proprietary license in order to sell it to a customer? I couldn’t find anything in this forum or the Discord.

2

Claude Opus 4.5 says that it’s a grey area but a Logseq plugin could likely be distributed under a proprietary license, because:

  1. Plugins are distributed separately, not bundled with Logseq
  2. They communicate through a defined plugin API rather than modifying Logseq’s source
  3. They can be argued to be independent works that merely use Logseq’s interface

I’m assuming that the Logseq team don’t disagree strongly with that, or they probably would have answered the question in these past 9 months since I asked it.