Quick Start

Join the “Hitchhiking to AGI” Program

Submit an application to join the first wave of Inference Noderunners on Fortytwo: Application Form

Please ensure you have received an acceptance email with an activation code before attempting to install the Inference Node. A unique activation code is required for each device on which the node is installed.

1. Preparing

System Requirements

Before installing a Fortytwo Inference Node, verify that your device meets the following minimum requirements.

What App Should You Run?

Depending on how you want your node to operate, you have two options:

1. Fortytwo App —> your node selects a model automatically.
2. Fortytwo CLI —> you manually select a model for your node to run.

Differences in node workflow for automatic & manual model selection methods:

Automatic model selection

Your node does all the work:

• Models are selected automatically.
• Performance is balanced.
• You don’t need to know anything about language models.

Use Fortytwo App for more complex, real time model auto-management on your system. Fortytwo CLI can recommend options based on your resources but will not be as optimal in its recommendations as the Fortytwo App.

Manual model selection

You can maximize your node’s potential but it requires knowledge and commitment:

• You choose which model your node runs.
• Performance depends on your choices.
• This mode is intended for noderunners who are familiar with language models.

2. Installing the Node: Fortytwo App & Fortytwo CLI

Please ensure you have received an acceptance email with an activation code before attempting to install the Inference Node. If not, submit an Application Form to join the first wave of Inference Noderunners on Fortytwo.

A unique activation code is required for each device the node is installed on.

Fortytwo CLI

macOS

1. Open the Terminal.

2. Navigate to your preferred installation directory with cd command, or run the following command to continue installation in the default location in your home directory:

   Zsh

   mkdir -p ~/FortytwoCLI && cd ~/FortytwoCLI
   

3. Run the following commands to download the node package, extract it, and execute the installation script:

   Zsh

   curl -L -o fortytwo-console-app.zip https://github.com/Fortytwo-Network/fortytwo-console-app/archive/refs/heads/main.zip
   unzip fortytwo-console-app.zip -d . && rm fortytwo-console-app.zip
   cd fortytwo-console-app-main
   chmod +x macos.sh && ./macos.sh
   

4. Follow the on-screen instructions in the script to complete the setup.

5. The node will start automatically.

3. Operating Your Node

The node will remain fully operational until it is terminated by the user or the system restarts. You can minimize the terminal window or switch to other applications – the node will continue running in the background.

Updating Your Node

Fortytwo node automatically updates every time it is launched. When you start the node, it checks for the latest available version and installs any updates before running.

Stopping Your Node

Press Ctrl+C in the terminal window to terminate the node process.

Restarting Fortytwo Node

On October 23, 2025, we’ve changed the name of the default folder from Fortytwo to FortytwoCLI. If you’ve installed your Fortytwo CLI before this date, your default path will differ. To access the folder, look for Fortytwo instead of FortytwoCLI.

macOS

1. Open the Terminal.

2. Navigate to the directory where the node is installed using the cd command. If the node was installed in the default location, run:

   Zsh

   cd ~/FortytwoCLI/fortytwo-console-app-main
   

3. Run the node startup script:

   Zsh

   ./macos.sh
   

4. Follow the on-screen instructions.

5. The node will start automatically.

Performance Considerations

Currently, the Fortytwo CLI does not support full load balancing. We recommend stopping the app (by closing the terminal) before running resource-intensive applications (e.g. videogames, video editing, or graphics software) to prevent performance issues.

This does not apply to nodes running on dedicated machines, where the node app runs independently without impacting other tasks.

Future versions will include load balancing, which will allow nodes to run alongside other resource-intensive applications without any noticeable performance impact.