Is it possible to set custom command parameters?

[quazar-omega]

I'm trying to run a bisync with my Proton drive remote, but it fails now that I edited a file
in the destination:

[2026-01-22T22:07:41.631745767Z] [ERROR] Bisync operation Job 1516 failed: bisync aborted

Output:
2026/01/22 23:07:32 ERROR : myfile.txt: Failed to copy: a draft exist - usually this means a file is being uploaded at another client, or, there was a failed upload attempt. Can use --protondrive-replace-existing-draft=true to temporarily override the existing draft
2026/01/22 23:07:32 ERROR : proton drive root link ID 'Synchronized': not deleting files as there were IO errors
2026/01/22 23:07:32 ERROR : proton drive root link ID 'Synchronized': not deleting directories as there were IO errors
2026/01/22 23:07:32 NOTICE: copy2to1: Received error: a draft exist - usually this means a file is being uploaded at another client, or, there was a failed upload attempt. Can use --protondrive-replace-existing-draft=true to temporarily override the existing draft - retrying as --resilient is set. Retry 1/3
[repeating same errors...]
2026/01/22 23:07:41 ERROR : Bisync aborted. Must run --resync to recover.

So I would need to run the bisync with --protondrive-replace-existing-draft=true, but I don't see the option available, so I wonder if, to support these very specific parameters, an option for custom ones could be added

[Hakanbaban53]

You can actually edit the resync flags directly in the Bisync settings, so there is no need to use command line parameters.
Here is how to find them:

• Go to Bisync Configuration.
• Select Edit Configuration (for the profile you are using).
• Scroll down past the path selections.
  You should see the options there.

Since app use the rclone api I dont know we can run the --protondrive-replace-existing-draft=true
Currently there is a limited things like resync and other things exist. I gonna test this custom command line arguments on rclone rcd. For now app not support these args.

Apologies that I can't provide screenshots at the moment, but hopefully, this helps you find it!

[vdavide]

It would be good. I understand that adding every rclone flag for every remote is time consuming so adding a single field with custom command line options would be extremely useful

[bo-ecoexpert]

I would need it too. Any news or workaround?

[Hakanbaban53]

This will be a bit late, but I've implemented custom flag arguments in the preferences modal (Ctrl +,).

I'm not sure yet whether flags can be passed directly via rclone rc, but they do work as command-line arguments at launch:

[bo-ecoexpert]

That is for rclone global flags, not for specific action flags. If you try e.g. to put some specific bisync flag, it fails to restart the engine

[Hakanbaban53]

Looking at the rclone flags docs, the custom flag support I implemented is intended for global flags, things like logging, caching, and other static options that apply to the rclone engine as a whole.

Backend-specific flags like --protondrive-replace-existing-draft=true are a different case. These probably belong in the backend/remote configuration rather than the global flags setting, or alternatively exposed as a separate per-remote custom flags field.

Worth deciding where these should live before implementing support for them.

[bo-ecoexpert]

i think it should be put here:

[Hakanbaban53]

Here's what I found: flags like --protondrive-replace-existing-draft are already available in the remote configuration UI, but changing them there modifies the config permanently, which isn't ideal if you only need a one-off override.

I also discovered these can be set at runtime via rclone rc, which is what RClone Manager already uses internally, so this is straightforward to support.

My proposal: add a Runtime Config section to the shared remote settings.

Instead of separating options into "advanced" and "normal" categories, show all available backend options in one place. Changes made here would only apply at runtime via rclone rc, without touching the saved remote configuration.

This gives users a way to temporarily override backend options per-operation without permanently changing their remote setup. Thoughts?

[bo-ecoexpert]

Don't know about the proton one, but for example i don't find anywhere the option --recover (specific for the bisync operation).
For my understanding, the best place is to put a custom command line override on the operation settings (like my previous screenshot)

[Hakanbaban53]

I understand the request, but this isn't something RClone Manager can support in its current form, here's why.

RClone Manager doesn't use the rclone CLI to manage syncs, mounts, or serves. It communicates entirely through the rclone RC API (remote control). When CLI arguments are passed through that path, rclone simply ignores them, I've tested this multiple times and confirmed it doesn't work.

The configuration values you see in the remote config and configuration dialogs aren't stored in the app either, they come directly from the rclone API at runtime.

So while the request makes sense on the surface, there's no clean way to pass arbitrary CLI flags through RC right now. Once I find a proper solution, it will be integrated straight away.

[vdavide]

Understood, so we have to wait rclone to implement those flags in the API. Il ven 13 mar 2026, 20:01 Hakan İSMAİL ***@***.***> ha scritto:

…

I understand the request, but this isn't something RClone Manager can support in its current form, here's why. RClone Manager doesn't use the rclone CLI to manage syncs, mounts, or serves. It communicates entirely through the *rclone RC API* (remote control). When CLI arguments are passed through that path, rclone simply ignores them, I've tested this multiple times and confirmed it doesn't work. The configuration values you see in the remote config and configuration dialogs aren't stored in the app either, they come directly from the rclone API at runtime. So while the request makes sense on the surface, there's no clean way to pass arbitrary CLI flags through RC right now. Once I find a proper solution, it will be integrated straight away. —