Advanced Command Builder for Power Users

[dickt800]

Pre-submission checks

• I have searched both open and closed issues and confirmed this doesn't already exist
• I have checked the roadmap and this isn't already planned
• This feature aligns with the project's scope (RClone management)

Feature Description

First of all, thank you for this amazing project!

I've been using rclone from the command line for quite a while, and I really like the idea of making it more accessible through a modern GUI. I think RClone Manager has a lot of potential. :contentReference[oaicite:0]{index=0}

I have one suggestion that might make the application much more useful for experienced rclone users.

Currently, the GUI focuses on simplicity, which is great for beginners. However, many advanced users still switch back to the terminal because they frequently rely on command-line flags such as:

• --checksum
• --check-first
• --transfers
• --checkers
• --log-level
• --log-file
• --bwlimit
• ...

Instead of hiding these options, would it be possible to add an optional Advanced Command Builder?

For example:

• ☑ Checksum (--checksum)
• ☑ Check before transfer (--check-first)
• Transfers: 20
• Checkers: 20
• Log level: INFO
• Log file: rclone_log.txt

The GUI could then generate the corresponding rclone command in real time.

This would allow users to:

• understand exactly what will be executed
• copy the generated command
• save it as a reusable profile
• learn rclone flags naturally over time

Personally, I don't think a GUI should hide the command line. Instead, it can become a visual command builder that helps users understand and use rclone more effectively.

This would keep the current beginner-friendly experience while making the application much more attractive for power users.

Thank you again for all your hard work! 😊

One more suggestion:

It would be great if users could save custom command templates (or default profiles).

For example, I almost always use the following workflow for uploading:

rclone copy "Local Path" "Remote Path" ^
-P ^
--checksum ^
--check-first ^
--transfers 20 ^
--checkers 20 ^
--retries 5 ^
--low-level-retries 10 ^
--log-level INFO ^
--log-file rclone_log.txt ^
-v

And after the upload, I usually verify everything with:

rclone check "Local Path" "Remote Path" --checksum -P

It would be very convenient if users could:
Save their own command templates
Set one as the default template
Edit templates later
Quickly select a template when creating a new task

Different users have different workflows, so allowing customizable templates would be much more flexible than providing a single predefined configuration.

### Proposed Solution

It would be very convenient if users could:

Save their own command templates
Set one as the default template
Edit templates later
Quickly select a template when creating a new task

Different users have different workflows, so allowing customizable templates would be much more flexible than providing a single predefined configuration.

### Feature Category

Sync/Copy Operations

### Applicable Versions

- [x] Desktop (GUI application with window)
- [x] Headless (Web server accessed via browser)
- [x] Portable (Standalone executable)
- [x] All versions

### Mockups/Screenshots

_No response_

### Technical Considerations

_No response_

### Additional Context

_No response_

[Hakanbaban53]

Thanks for the detailed feature request, really appreciate the effort you put into this! 😊

You're right that RClone Manager was originally designed to keep things simple for everyday users. But based on requests like yours, it's grown, and some advanced use cases just don't fit well into the main UI anymore. Because of that, I've decided to design a separate page for this: #232

That page will be a more detailed dashboard, generally aimed at advanced users, things like a command builder, custom flags, and reusable profiles/templates similar to what you described here.

I'll make sure to take your suggestions (the advanced command builder, real-time command preview, and saveable/default templates) into account while designing it. Thanks again for taking the time to write this up in such detail!

[dickt800]

Thank you so much for the thoughtful reply! I really appreciate you taking the time to read my feature request in such detail.

I think separating advanced features into a dedicated page is a great design choice. It keeps the main UI simple while giving power users more flexibility.

I'm really looking forward to #232. Thanks again for your work on RClone Manager! If you'd like any feedback or testing once it's available, I'd be happy to help.

[dickt800]

One small suggestion for the advanced page:

Since RClone Manager already has a Chinese UI, it might be helpful to expose the local filename encoding (--local-encoding) as an advanced option.

On Windows, users with filenames containing full-width Chinese punctuation such as ：, ？, or ＊ may otherwise run into confusing "directory not found" errors because of rclone's default filename encoding behavior. I actually ran into this exact issue today while uploading files with Chinese filenames.

Keeping the default unchanged is probably the right choice, but making this option discoverable in the Advanced page could save users a lot of debugging time.

This is already documented by rclone, but it's easy to overlook if you're using the GUI instead of the CLI.

[Hakanbaban53]

Thanks for the great suggestion!

To be honest, I had never heard about this before. I just researched it, and it's really fascinating. It's a very important detail to know, not just for app development but also for system architecture.

Thank you for helping improve the project and teaching me something completely new today!

[Hakanbaban53]

Hey @dickt800, Actually, this value exists in the app:

But I did not add which one actually is which command line argument on UI like I uploaded in this image (Upcoming UI improvement). So I think that Encoding is what you want or am I wrong?

[dickt800]

Yes, that's exactly the option I was referring to.

The functionality already exists, so there is no need to add a new setting. My suggestion is mainly about the UI.

At the moment, users only see: Encoding. But they don't immediately know that this corresponds to the rclone CLI flag: --local-encoding. For users who mainly learn rclone from command-line examples, it would be very helpful if the UI showed something like: Encoding (--local-encoding); or Local Encoding (--local-encoding).

That small hint makes it much easier to connect the GUI with the official rclone documentation and existing command examples. This is especially useful because many online examples refer to the CLI flag instead of the GUI label. Thanks again for looking into this!

One small note from my recent experience:

I don't think this option should be highlighted as something users always need to change.

The default encoding works perfectly for almost all cases.

It only becomes useful for some special Windows filename situations (such as Unicode fullwidth characters like ：＊？). This issue is much more likely to affect users who frequently use Unicode fullwidth punctuation in filenames (for example, many Chinese and Japanese users).

So keeping the default behavior unchanged is probably the best choice.

I also discovered another interesting case. If you upload files using one encoding configuration but later run rclone check with a different encoding configuration, some filenames may no longer match even though the file contents are identical. As a result, rclone check reports files as missing because the filename encoding is interpreted differently. So it's important to keep the same encoding configuration for upload, sync, and check operations within the same repository.