Two Syside CLI interfaces? Different functionality? What the heck, man

Syside
1

While using the professional license VS Code tools and trying to use the viz command qualifier, I found a separate modeler CLI installation. Both are named syside.exe, but they are not the same tool. Here are the differences:

CMD> syside --help
Usage: syside [OPTIONS] <COMMAND>

Subcommands:
  check        Check SysML and KerML files for syntax and semantic errors (Modeler).
  format       Format SysML files (Modeler).
  server       Run Syside language server.
  rule         Explain a rule or rules
  interactive  Drop into an interactive shell with a loaded model
  reqif        Import/export ReqIF files for SysMLv2.
  solver       Compute attainable sets of expressions over a SysML v2 model.
  version      Display the version of `syside`
  help         Display documentation for a command

Options:
  -h, --help     Print help
  -v, --version  Display version

Commercial Software (copyright) Sensmetry 2025-2026

CMD> syside --version
syside 0.10.3 (b6e216cb48b5336ea48283e99c68a0e10e17b8cc)

REM
REM I renamed the syside.exe product sysvew (sea view) to keep the two
REM CLI products separate and keep the theme syside, sysand, sysvew...
REM Product was downloaded and installed given the instructions at
REM https://docs.sensmetry.com/modeler/cli/install/#modeler-cli-install-main
REM

CMD> sysvew --help
Usage: syside <COMMAND>

Commands:
  check   Check SysML and KerML files for errors (requires Modeler license)
  format  Format SysML and KerML files (requires Modeler license)
  rule    Explain a rule or rules
  viz     Generate diagrams from SysML models (requires Modeler license)
  table   Operations on table and matrix views (requires Modeler license)
  help    Print this message or the help of the given subcommand(s)

Options:
  -h, --help     Print help
  -V, --version  Print version

Commercial Software (copyright) Sensmetry 2025-2026

CMD> sysvew --version
syside 0.10.3 f8ca4371147a2854109fef0ae84cfe3805bdfe3a

The questions are: a)Why are there two Sysides? b)Is this expected? and c) Why are the capabilities so different between them?

As you can see, I’ve found a way to use both, but this seems janky and possibly a product build issue (just guessing here, not blaming).

V/r @Richard_Wallace

2

Hi Richard,

What you have found here is the syside.exe behind the Python library. Since you have both the CLI and Automator library installed, you have “two” Sysides.

On your last question about why the capabilities are different, I am afraid I cannot answer it right now and I can only tell you to keep an eye out for some exciting announcements that are going to come soon. :wink:

Kind regards,
Simonas