Console usage
Connect the board over USB, use idf.py monitor, minicom, or the web flasher Console to reach the basic_demo prompt (default basic_demo> ).
Session and Q&A
Section titled “Session and Q&A”Switch session
Section titled “Switch session”Each session uses its own history file (see Memory). Long-term memory data is managed in the shared memory/ directory.
Chat with the LLM
Section titled “Chat with the LLM”ask starts a multi-turn chat with history. ask_once is single-turn and does not append to session history.
List capabilities
Section titled “List capabilities”Invoke a capability
Section titled “Invoke a capability”The second argument must be valid JSON (mind quoting/escaping).
Group management
Section titled “Group management”A capability may expose many tools. They are grouped so you can enable/disable/unload whole sets at once.
On the model side: activate_skill / deactivate_skill. On serial: the skill command (registered by cmd_cap_skill) can manage Skills, e.g.:
Keep --session aligned with the active session id, otherwise it looks “activated but not in context”.
Other registered cap commands
Section titled “Other registered cap commands”basic_demo 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 loads the cap_im_qq group.
System configuration
Section titled “System configuration”For runtime Wi‑Fi / LLM edits, Web is often easier: