Skip to content

Console usage

Connect the board over USB, use idf.py monitor, minicom, or the web flasher Console to reach the edge_agent prompt (default app> ).

Each session uses its own history file (see Memory). Long-term memory data is managed in the shared memory/ directory.

session demo
session

ask starts a multi-turn chat with history. ask_once is single-turn and does not append to session history.

ask list what you can do for me
ask_once one-off question, do not use history
cap list

The second argument must be valid JSON (mind quoting/escaping).

cap call get_current_time '{}'
cap call list_dir '{"keyword":"scripts"}'

A capability may expose many tools. They are grouped so you can enable/disable/unload whole sets at once.

cap groups
cap enable <group_id>
cap disable <group_id>
cap unload <group_id>

On the model side: activate_skill. On serial: the skill command (registered by cmd_cap_skill) can manage Skills, e.g.:

skill --catalog
skill --list --session default
skill --activate weather --session default

Keep --session aligned with the active session id, otherwise it looks “activated but not in context”.

auto reload
auto rules
auto last
...
Dataflow and automation More commands and details in this doc

edge_agent registers help, cap, auto, time, web_search, mcp_client, mcp_server, llm_inspect, event_router, etc. Type help in the Console for the full list.

Besides the usual cap subcommands (list, call, groups, enable, disable, unload), cap load qq dynamically registers the cap_im_qq group implemented by cap_im_platform.

For runtime Wi‑Fi / LLM edits, Web is often easier:

Web configuration Change settings and files from the LAN
Configuration NVS keys and how values apply