Skip to content

Running Machinechat JEDI as a Service

Machinechat JEDI offers the flexibility to run either in an interactive command-line interface (CLI) mode or as a background service. Here's how to manage JEDI as a service for streamlined operation.

Default Behavior

When you execute mcjedi.exe (on Windows) or mcjedi.bin (on macOS/Linux) without any command-line options, JEDI automatically starts in interactive/CLI mode. This provides direct access to the JEDI command prompt.

Advantages of Running JEDI as a Service

  • Background Operation: The JEDI service runs continuously in the background, even if you are not actively logged in to the terminal.
  • Automated Startup: Configuring JEDI as a service ensures it automatically starts when your system boots up.
  • Reliability: Services are generally more robust and resilient to unexpected interruptions compared to interactive mode.

Important

  • You may need administrator privileges to manage the JEDI service.
  • Specific service installation procedures might slightly differ between Windows, macOS, and Linux environments. Consider referring to OS-specific documentation if needed.

Service Management

The mcjedi.bin (or mcjedi.exe) executable includes built-in options for installing, uninstalling, starting, and stopping the JEDI service.

To see a full breakdown of these options, run:

mcjedi.exe --help 
# Or, on macOS/Linux
mcjedi.bin --help

Key Commands

  • Installation: 
    mcjedi.exe --service install
# Or, on macOS/Linux
mcjedi.bin --service install
  • Uninstallation: 
    mcjedi.exe --service uninstall
# Or, on macOS/Linux
mcjedi.bin --service uninstall
  • Start Service: 
    mcjedi.exe --service start
# Or, on macOS/Linux
mcjedi.bin --service start
  • Stop Service: 
    mcjedi.exe --service stop
# Or, on macOS/Linux 
mcjedi.bin --service stop

Need help?

Contact our support team: support@machinechat.io