Skip to content

Let a request router plugin leave connection settings to the requester or approver #67

Open

Description

@grtn91

Problem

A request router plugin reads every setting of a request from the connection config an admin saved, or from a routing rule. The host can't tell that a setting such as a quality profile or root folder could be chosen per request. Only the admin can choose, and only in advance.

This comes up for anyone with one download server that serves several uses. The requester, or the admin approving the request, knows which profile or folder a title should get, but the plugin has no way to let them say so. It started from Silo-Community/silo-plugins-requests-seerr#10, which asks for Silo routes to choose the Seerr Radarr/Sonarr server, profile and folder. Solving it takes changes in this SDK, in silo-server and in the plugin.

Proposal

Add requester_options to RequestRouterDescriptor. Each entry names:

  • field: a select with dynamic_options in the plugin's admin form, which is the setting that can be chosen per request.
  • media_type and label: optional, for where the choice applies and how the host labels it.
  • chooser_field: a static select in the same form where the admin says, per connection, who chooses. The values are admin, requester or approver.

The host takes the choices from ListConfigOptions for the server the title would go to, checks the pick against them, and passes it as that key of RouterConnection.config. The plugin's RPCs don't change. Manifest validation requires field to be a select with dynamic_options, and chooser_field to be a static select that offers only those three values.

Compatibility

  • An older host drops the unknown field and never offers the choice, so a plugin can declare options without raising its minimum host version.
  • No existing field changes meaning.
  • A Silo host that predates the field refuses a bare plugin binary that declares it, because it reads a binary's manifest strictly. On such a host the plugin has to be installed from an archive. This goes in docs/compatibility.md.

Alternatives considered

  • A boolean per option (allow_requester_choice): it can't also express "the approving admin chooses" without another field.
  • A new RPC for per-request choices: it would change the plugin contract for something the host can do by overlaying config, as it already does for route overrides.

PRs

AI disclosure: Claude Code, claude-sonnet-5-5, fully AI-generated, human verified.

Activity

  1. added
    enhancementNew feature or request
    triagedHigh-confidence review completed; does not mean fixed, validated, or accepted for release.
    on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttriagedHigh-confidence review completed; does not mean fixed, validated, or accepted for release.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions