Skip to content

feat(seerr): choose the root folder from storage groups by free space - #2

Open
grtn91 wants to merge 3 commits into
grtn91/feature-enhance-seer-request-with-profile-and-pathfrom
grtn91/storage-groups
Open

grtn91 wants to merge 3 commits into
grtn91/feature-enhance-seer-request-with-profile-and-pathfrom
grtn91/storage-groups

Conversation

@grtn91

@grtn91 grtn91 commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

Stacked on the profile and folder PR.

Problem

A connection sends every request to one root folder. With several disks, that folder fills up while the others have room, and an admin has to change the setting by hand.

Approach

"Use storage groups" lets the plugin choose the root folder of each request.

  • A group is a named list of Radarr and Sonarr root folders, filled either in order or by most free space. The folder lists are marked as ordered, so their order can be set by dragging.

  • Groups are tried in order. A folder with less than the minimum free space (default 50 GB) counts as full, and a full group hands over to the next.

  • When no group has room, the request fails with a message. It is not sent to Seerr's default folder.

  • While groups are on, the root folder selects and their "chosen by" selects are hidden. A storage group select takes their place: Automatic starts at the first group, a named group starts there. A routing rule can set it, for example to send anime to another group.

  • A picked group is stored by its name, so the pick follows the group when the order changes. Two groups cannot share a name.

  • A media type no group has folders for keeps Seerr's default folder. A group folder the server no longer has is skipped for requests and reported on save and on connection test.

  • With a separate 4K server, the groups hold the folders of the standard servers. A 4K request keeps its own 4K root folder setting.

The form declares eight group slots. With the SDK and silo-server changes linked below, the form shows one group and an "Add storage group" button, and groups can be folded, reordered and deleted. Without them, all eight groups are shown and a group's folders keep the order they were selected in.

Validation

  • go test ./... and go vet: pass, also when built against the SDK branch that knows list sections.
  • Not yet run against a live Seerr by the author of the code.

Risks

  • Free space is read from Seerr when the request is submitted. The plugin does not know a title's size, so the minimum has to cover the largest downloads.
  • Open design points for issue 10: the cap of eight groups, and a picked group never falling back to an earlier group.

Related PRs

Based on #1. Same feature in the other repos:

AI Disclosure

  • Harness: Claude Code
  • Tool(s): Claude Code
  • Model(s): claude-fable-5-2
  • Involvement: Fully AI-generated, human verified
  • Adversarial review: n/a

🤖 Generated with Claude Code

A connection sends every request to one root folder. With several disks
that folder fills up while the others have room, and an admin has to
change the setting by hand.

"Use storage groups" lets the plugin choose the folder. A group is a
named list of Radarr and Sonarr root folders that is filled in order or
by most free space. Groups are tried in order; a folder with less than
the minimum free space counts as full, and a full group hands over to
the next. When no group has room the request fails with a message
instead of going to Seerr's default folder.

While groups are on, the root folder selects and their "chosen by"
selects are hidden and a storage group select takes their place:
Automatic starts at the first group, and a named group starts there, on
the connection or in a routing rule. A pick is stored by the group's
name so it follows the group when the order changes. Requesters and
approving admins are offered no folder while groups decide it.

The form declares eight group slots. A Silo server that knows list
sections shows one and an "Add storage group" button; an older one
shows all eight.

AI disclosure: written with Claude Fable 5.2 in Claude Code. go test ./... and
go vet pass locally, also against the SDK branch that knows list
sections. Not yet run against a live Seerr by the author.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
grtn91 and others added 2 commits November 11, 2026 22:39
"In order" fills a group's folders by their place in the list, but the
list kept the order the folders were clicked in and could not be
rearranged.

The group folder lists are marked as ordered, so a Silo server that
knows the flag shows them as a list that is put in order by dragging.
The form texts and the README also describe deleting a group from its
header, which the list sections of that Silo server provide.

AI disclosure: written with Claude Fable 5.2 in Claude Code. go test ./... and
go vet pass locally.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Storage groups hold the folders of the standard servers. With a separate
4K server, the 4K request keeps its own 4K root folder setting.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant