Instance Settings and Configuration

Overview

After creating an instance, you can configure its AI model, messaging channels, web access, and SSH access. All configuration is done through the instance dashboard.

This page covers the settings available for each instance and how to change them.

LLM Configuration

The LLM (Large Language Model) configuration controls which AI provider and model your instance uses to process messages.

Setting Up the LLM

During the setup wizard (or later from Instance Settings):

1. Open the instance dashboard
2. Go to LLM Settings (or the setup wizard step 1)
3. Select a provider
4. Enter your API key
5. Optionally select a specific model
6. Save

Supported Providers

If you do not select a model, the default for your provider is used automatically.

Changing the LLM Later

You can update the LLM provider and API key at any time from the instance settings page. The change takes effect within a few seconds.

LLM Add-on (Managed Mode)

If you subscribe to a managed LLM add-on, ClawHosters provides the API key and handles billing for AI usage. You can choose between tiers:

• Eco — Lower-cost models, suitable for basic tasks
• Standard — Mid-range models for general use
• Premium — Top-tier models for demanding workloads

With the BYOK (Bring Your Own Key) option, you use your own API key and pay your provider directly.

Add-on configuration is available at Dashboard → Add-ons.

Telegram Configuration

Connect a Telegram bot to your instance so users can interact with your AI assistant through Telegram.

Setting Up Telegram

1. Create a bot through @BotFather on Telegram
2. Copy the bot token
3. Open the instance dashboard → Messenger Settings (or setup wizard step 2)
4. Paste the bot token
5. Optionally enter the bot username (without the @ symbol)
6. Choose a DM policy
7. Save

DM Policy

The DM policy controls who can message your bot:

Pairing Your Bot

If you use pairing mode (recommended):

1. Go to the instance dashboard
2. Click the Pair Telegram button
3. Follow the instructions to link your Telegram account
4. Once paired, the bot responds to your messages

Discord Configuration

Connect a Discord bot to your instance.

Setting Up Discord

1. Create a bot in the Discord Developer Portal
2. Enable the Message Content Intent in the bot settings
3. Copy the bot token
4. Open the instance dashboard → Messenger Settings
5. Paste the bot token
6. Choose a DM policy (pairing or open)
7. Save

The pairing process works the same as Telegram. The instance owner must pair first if using pairing mode.

Slack Configuration

Connect a Slack app to your instance.

Setting Up Slack

1. Create a Slack app at api.slack.com/apps
2. Configure the required permissions and enable Socket Mode
3. Copy both the Bot Token (starts with xoxb-) and the App Token (starts with xapp-)
4. Open the instance dashboard → Messenger Settings
5. Enter both tokens
6. Choose a DM policy
7. Save

Both tokens are required for Slack integration to work.

WhatsApp Configuration

WhatsApp connects through a QR code pairing process in the OpenClaw web interface.

Setting Up WhatsApp

1. Open the instance dashboard
2. Go to Messenger Settings
3. Enable WhatsApp
4. A QR code appears in the OpenClaw web interface
5. Scan the QR code with WhatsApp on your phone
6. The connection is established

QR codes expire after a short time. If it expires, refresh to get a new one.

WhatsApp allows only one linked device per phone number for the web interface. Disconnect any existing linked sessions first.

Web Access (Gateway)

Every running instance has a web interface (the OpenClaw Gateway) accessible through a URL.

Access Methods

There are two ways to access the web interface:

1. Token URL — A URL with an authentication token appended: https://{subdomain}.clawhosters.com/?token={token}
2. HTTP Basic Auth — Standard username/password authentication using your email and a generated password

Viewing Credentials

1. Open the instance dashboard
2. Click View Credentials in the quick actions section
3. Copy the Gateway URL or HTTP auth credentials

Regenerating the Password

If you need a new HTTP auth password:

1. Open the instance dashboard
2. Click Regenerate Password
3. The old password stops working immediately

The Gateway token is deterministic and does not change.

SSH Access

SSH access lets you connect directly to the underlying VPS for advanced debugging or customization.

Enabling SSH

1. Open the instance dashboard
2. Click SSH Access in the quick actions
3. Enter your public SSH key (ed25519 or RSA format)
4. Confirm that you understand the implications
5. SSH access is enabled

Connecting via SSH

ssh -p 2222 root@{ip_address}

Replace {ip_address} with the IP shown in your instance dashboard.

Important: SSH and Support

Enabling SSH access permanently sets your instance to no-support status. This means:

• The support team cannot assist with issues caused by manual server modifications
• The change cannot be reversed
• Standard support for billing and account issues is still available

Only enable SSH if you are comfortable managing the server yourself.

Instance Details

The instance dashboard shows these read-only details:

Resource Monitoring

The instance dashboard displays resource usage indicators:

These metrics update every 5 minutes. If any metric consistently reaches high levels, consider upgrading to a higher tier.

Related Documentation

• Instance Overview — Instance statuses, lifecycle, and tiers
• Starting and Stopping Instances — Power management and billing impact
• SSH Access to Your Instance — Detailed SSH setup, security, and support implications
• LLM Add-on — Managed AI models and BYOK configuration
• Troubleshooting Common Issues — Solutions for frequent problems