Skip to content

← All guides

ZeroClaw Rust and VPS Preparation: Before You Build

ZeroClaw.net · Updated

You need Rust when compiling or modifying ZeroClaw. A compatible prebuilt release lets you run the executable without installing the Rust toolchain. Choose the route first, then prepare the server around it.

For download commands, use the installation guide. For a complete first-run sequence, use the setup checklist.

Decide whether a source build is necessary#

A source build is useful when you need to change code or select features unavailable in your packaged build. Check the chosen release's build instructions, toolchain requirements and feature flags before compiling.

  • Record the release tag or commit you build.
  • Use a regular development account for the Rust toolchain.
  • Check the target operating system and CPU.
  • Preserve matching frontend assets if you need the dashboard.

If compilation fails, keep the exact error and check the dependency or toolchain requirement it names. Removing .await from arbitrary source lines is not a general build repair.

Prepare the VPS account and storage#

Run the assistant under a dedicated account with access to its own configuration, data and workspace. Decide where each directory lives and which files need to survive a restart or replacement deployment.

A hosted model can keep inference off the VPS. For local inference, size the server for the model as well as ZeroClaw. See the provider chooser.

Keep a record of:

  • The account that owns the process and data.
  • The config directory used at startup.
  • The workspace and persistent storage locations.
  • The backup location and restore procedure.

Check ports before adding remote access#

Start locally and use the listener address printed by the gateway. If the port is occupied, identify the existing process or choose another port. The dashboard troubleshooting steps include the error and a successful alternate-port check.

A private listener is not directly reachable from your laptop when it runs on a remote server. Choose an authenticated remote-access method deliberately; do not disable pairing simply to make a browser connect.

Review Discord and other channel permissions#

Before connecting Discord, check the selected ZeroClaw release's channel configuration and the bot permissions your workflow needs. Confirm the message intents, channel access, agent routing and authorized users together.

Avoid Administrator permissions and wildcard user authorization as setup shortcuts. Start with a private test channel and one authorized account. Use the same approach for any messaging integration: connection health and permission to invoke an agent are separate checks.

Choose the model independently of the channel. The older walkthrough's MiniMax selection was one provider choice, not a prerequisite for VPS deployment.

Plan service startup and recovery#

Before enabling background startup, verify the foreground process with the intended account and config directory. Then check your chosen service manager's working directory, environment, restart policy and log location.

After a restart, confirm that:

  • The process uses the same config and workspace.
  • The gateway is reachable through the intended access route.
  • One direct model request returns a reply.
  • Persistent data remains available.

For containers, follow the Docker deployment guide. For replacing a binary or restoring data, use the update and backup guide.