Skip to main content

Overview

This example walks through running ArkSim against an OpenClaw personal AI assistant. OpenClaw is an open-source assistant that runs on your own hardware and can manage tasks, smart home devices, messaging, calendar, and files. You use this setup to simulate and evaluate conversations against your own OpenClaw deployment. The agent is exposed via a Chat Completions-compatible endpoint; the example config.yaml is already configured for the OpenClaw gateway.

Prerequisites

Before getting started:
  • OpenClaw installed and configured: openclaw.ai
  • OpenClaw gateway running with the HTTP Chat Completions endpoint enabled
  • OpenAI API key: used by ArkSim to power the simulated user
  • OpenClaw gateway token: for authenticating to your OpenClaw instance (see ~/.openclaw/openclaw.json under gateway.auth.token)

Scenarios

The example ships with pre-built scenarios in scenarios.json representing realistic interactions with a personal AI assistant. Each scenario defines a simulated user with a distinct persona, goal, and background knowledge (files, smart home setup, contacts, tasks, etc.). The scenario goals are:
  • Manage reminders and to-do lists for files and storage (cleanup Downloads, cloud folders, storage alerts, important documents).
  • Control and automate smart home devices and scenes (lights, thermostat, blinds, locks, scenes like Good Morning, Movie Night, Leaving Home, Goodnight).
  • Send and manage messages across WhatsApp, iMessage, Slack, email, and Telegram using contacts and recent conversations.
  • Manage calendar and schedule (e.g. call dentist to confirm appointment, schedule car maintenance, recurring reminders, upcoming tasks).
  • Organize files and documents across local folders and cloud storage (cleanup Downloads, duplicate photos, Trash, important items and shared folders).
Scenarios are defined in scenarios.json in the example directory and can be edited or extended to reflect your assistant’s capabilities.

Setup

1

Enable Chat Completions in OpenClaw

In ~/.openclaw/openclaw.json, enable the HTTP Chat Completions endpoint:
2

Start the OpenClaw gateway

3

Set environment variables

Your gateway token is in ~/.openclaw/openclaw.json under gateway.auth.token.
4

Verify the OpenClaw connection

Before running simulation, confirm the gateway is responding:
You should receive a valid JSON response from the gateway.
5

Run simulation and evaluation

Run from the examples/openclaw directory:
The config.yaml has the agent_config pointed at http://localhost:18789/v1/chat/completions with Authorization: Bearer ${OPENCLAW_TOKEN} and x-openclaw-agent-id: main.

Configuration

The example uses a single config file for both simulation and evaluation. Agent configuration is specified inline under the agent_config key:

Output

Results are written under the example directory:

Example Files


Adapting to Your Own Assistant

To use this example as a starting point for your own personal assistant:
  1. Scenarios: Edit or add scenarios in scenarios.json so goals and knowledge reflect your assistant’s capabilities.
  2. Agent config: If your endpoint, port, or auth headers differ from the OpenClaw defaults, update the agent_config section within config.yaml file accordingly.
See Agent configuration for supported protocols and how to configure agent connections.