I know devlopers always see freerouting as a design platfrom, but in face it is often not very easy to use and most people just export .dsn in their own EDA to route,

So I think if we can provide CLI and HTTP(s) Interface for CAD and Linux users (who doesn't have a desktop environment) .

• HTTP Interface can refer EasyEDA Std Tutorial: Local-Auto-Router .

In this example, EasyEDA's auto-router has own HTTP Interface to call by EasyEDA (EasyEDA based on electron, more like a browser).

In most case EasyEDA's auto-router doesn't do well like freerouting, so maybe analyse the network activity from EasyEDA can provide a native routing support for it. :)

Of cource, many CAD supports add-ons (Thanks to electron). If you supports HTTP-Interface, by Javascript, maybe we can let more CAD natively supports freerouting.

• CLI Interface can improve from now, just add --no-gui option and --interactive or --no-Interactive for human or program.

It just like in interactive:

$ java -jar freerouting.jar --no-gui --interactive
Welcome to freerouting v1.8.0.
Freerouting is a free software, xxxxxxx
Type 'help' if you need help.
> help
......
> config optimize false
> auto-routing
Auto-routing started.
Auto-routing \#1 was running, xxx routed, xxx to be route, xxx failed.
Auto-routing \#2 was running, xxx routed, xxx to be route, xxx failed.
......

or in no-interactive:

$ java -jar freerouting.jar --no-gui --no-interactive --auto-routing --no-optimize
Welcome to freerouting v1.8.0.
Freerouting is a free software, xxxxxxx
Auto-routing started.
Auto-routing \#1 was running, xxx routed, xxx to be route, xxx failed.
Auto-routing \#2 was running, xxx routed, xxx to be route, xxx failed.

Maybe CLI will be cooler and faster than now GUI, I think.

PS: \# eqals to #, just ensure that I will not mention some issues.