Web Console

edge_agent starts the Web Console after the Wi-Fi stack is ready, providing chat, status view, and configuration features. The Web Console implementation is located at http_serverapplication/edge_agent/components/http_server/.

Security notice

edge_agent is not intended for production use. The edge_agent Web Console assumes a trusted environment and returns almost all information.

• Do not expose the Web configuration page port to the public Internet.
• The retained SoftAP console also has full privileges. Set a password or enable auto-disable SoftAP when possible.
• The service runs on LAN and does not use HTTPS by default.
• The configuration page and NVS contain secret tokens. Do not publicly share exported config files or full-device NVS dumps.
• The configuration page can download almost all content in the filesystem.

See GitHub issue #41 for more details.

Open the Web Console

Your computer or phone must be on the same LAN as the board, or connected to the SoftAP hotspot provided by the board (default SSID in edge_agent is esp-claw-XXXXXX, where XXXXXX is the device MAC address).

Open in browser: http://esp-claw.local/ or http://<device-ip>/

Note

• If .local cannot be resolved, use the IP printed in serial logs, or check DHCP assignments in your router admin page.
• Default port is 80; if default port or mDNS domain is changed, use the updated port/domain.

System Status

The System Status page shows basic ESP-Claw status, including network information, IP address, Wi-Fi mode, SoftAP SSID, and SoftAP IP.

Web Chat

Web Chat lets you interact with ESP-Claw without configuring extra IM channels. Web Chat also supports regular features and triggering Event Router capabilities through messages. For example, you can use /new to create and switch Session.

Web Chat currently does not support receiving image attachments.

Web Chat unavailable?

Check whether Local IM is disabled on the Capabilities management page.

System Settings

Basic Settings

Basic settings include Wi-Fi and timezone settings.

• Wi-Fi settings configure SSID and password. Requires Restart
  • Currently, except ESP32-C5, other chips only support 2.4 GHz Wi-Fi.
  • Empty password means the current Wi-Fi has no password.
• SoftAP settings configure SoftAP SSID, password, and start/stop behavior. Requires Restart
  • ESP-Claw enables SoftAP by default for provisioning and configuration adjustments.
  • Empty SSID means using the MAC-based default SSID (esp-claw-XXXXXX).
  • Empty password means open hotspot. If password is set, it must be at least 8 characters.
  • You can configure SoftAP to auto-disable after successful Wi-Fi connection. For security, this is recommended.
• In Advanced settings, timezone settings adjust device timezone. Requires Restart
  • Must be in POSIX TZ string format. Recommended reference: this table.
  • Example: timezone for Beijing/Hong Kong/Singapore is CST-8.
  • Timezone affects Schedule task execution and the time provided to LLM.
  • On first setup, the system attempts to infer timezone from browser automatically. This inference may be inaccurate and cannot infer DST details.

LLM Settings Requires Restart

LLM settings configure provider, API key, model, and other LLM options. For easier onboarding, ESP-Claw includes presets for common LLM providers. For those providers, you only need API key and model name.

ESP-Claw also supports custom LLM providers. Currently, ESP-Claw supports two backend types: OpenAI-compatible API and Anthropic-compatible API. You need to provide Base URL manually, and configure fields like Max Tokens field name if required by the provider.

ESP-Claw recommends models at least comparable to gpt-5.4, qwen3.6-plus, deepseek-v4-pro, and claude-sonnet-4-6 to unlock its full potential. If you use other models, tune LLM advanced options such as “supports vision input” to match the model capabilities.

Pay attention to Base URL format

For custom LLM providers, the Base URL path must be kept up to the version segment:

• Keep only the part before /chat/completions (OpenAI format) or /messages (Anthropic format);
• Do not end with /.

For example:

https://api.openai.com/v1/chat/completions
vvvvvvvv Base URL vvvvvvv
https://api.openai.com/v1

https://api.anthropic.com/v1/messages
vvvvvvvvvv Base URL vvvvvvvv
https://api.anthropic.com/v1

https://api.deepseek.com/chat/completions
vvvvvvv Base URL vvvvvvv
https://api.deepseek.com

IM Settings Requires Restart

The IM settings page lets you connect or adjust different instant messaging platforms, including WeChat, QQ, Feishu, Telegram, and more.

WeChat

To enable WeChat, click “Generate QR” and scan it with WeChat “Scan” to complete setup. Save and restart for changes to take effect.

WeChat Base URL and CDN Base URL in Advanced settings usually do not need changes. Default values are:

https://ilinkai.weixin.qq.com # WeChat Base URL
https://novac2c.cdn.weixin.qq.com/c2c # WeChat CDN Base URL

QQ

To enable QQ, create a QQ bot on QQ Open Platform, then fill App ID and App Secret in the corresponding fields. Save and restart for changes to take effect.

Feishu

To enable Feishu, create a Feishu bot app on Feishu Open Platform - Create Feishu Agent App, then fill App ID and App Secret in the corresponding fields. Save and restart for changes to take effect.

Note: Lark international edition is not supported yet.

Telegram

To enable Telegram, chat with @botfather in Telegram app, create a bot, and obtain Bot Token. Then fill the Bot Token field. Save and restart for changes to take effect.

Network & Search Settings

ESP-Claw can connect to Brave or Tavily search APIs to retrieve online resources during runtime; it can also issue HTTP requests (GET/POST/…) for real-time online access.

Search API Keys: optional. Once configured, online resources can be retrieved via search APIs.

• Brave Search API Key: Brave Search API Key, see Brave API docs.
• Tavily API Key: Tavily API Key, see Tavily API docs.

HTTP Requests: configure HTTP allowlist. Wildcard * is supported; standalone * allows all domains/IPs.

Memory Management

The Memory Management page is for viewing long-term memory and managing “Soul”, “Identity”, and “User Info” in the memory system.

• Long-term Memory is a human-readable file generated from structured memory. Editing this file does not directly modify structured memory, so it is read-only for inspection.
• Soul, Identity, and User Info are editable files used to store personalized information for the device and user.

After chatting with ESP-Claw, click “Refresh” or “Refresh All” to refresh memory files and view the latest memory content.

Memory Reference Learn details about long-term memory, Soul, Identity, and User Info

Capabilities Management

The Capabilities Management page controls whether each ESP-Claw capability is enabled. If disabled, the capability is not loaded. By default, all capabilities are enabled. You can enable or disable each capability by checking or unchecking it.

To reduce context length, not all capabilities are LLM-visible by default. Some capabilities provide Skills. When LLM chooses to activate the corresponding Skill, that capability automatically provides its tools to the LLM.

Lua Modules Management Requires Restart

Lua Modules Management controls whether Lua modules translated from IDF low-level modules are enabled. These are different from Lua modules provided by Skills.

Lua Modules Reference Learn details about Lua modules

File Management

The Web configuration page provides simple file management, so you can browse and read/write filesystem files directly without going through LLM. For ESP-Claw runtime filesystem structure, see Filesystem layout.

By default, File Management is read-only. Write actions are enabled only after turning on “Admin Mode” (Dev Mode). After enabling “Admin Mode”, you can manually add Skills, edit automation rules, modify Lua scripts, and more.

Warning

After enabling “Admin Mode”, operate carefully. Deleting important files or invalid JSON may cause system failures, even reboot loops.

Note

• Online file read/write has size limits, depending on CONFIG_HTTP_MAX_UPLOAD_SIZE when firmware is built.
• After changing automation rules, remember to run auto reload in Console (see Console usage) or restart.