Viewerly

Plugins

Plugin policy

What a plugin has to be to be listed in the directory, and what gets it refused or pulled.

Plugins may not compete with Viewerly Premium.

  1. No working around a limit or the licence: the sessions-per-project limit, the Claude account limit, tier checks or licence tokens.
  2. No remote access to sessions, for anyone: no relays, tunnels, sync or mirroring of sessions, terminals or statuses to other devices or web services, and no answering permissions or typing from outside the machine. Viewerly's own Sync, phones and dashboard are the way to do that. Telling a person that a session needs them (a chat message, a webhook) is allowed; acting on the session from there is not.
  3. The Free kinds carry nothing that does either. Themes, icon packs and agent definitions hold nothing that breaks the first two points: no "agent" that is really a tunnel, for example.
  4. A plugin that breaks the policy is refused, or pulled once listed, and its author is told why.

Also: plugins must be open source, with the source in the linked repository, and must not collect personal data beyond what their stated purpose needs.

Questions about a decision go to [email protected].