Actions Overview

​

What Are Actions?

rcli ask "open Safari"
rcli ask "create a note called Meeting Notes"
rcli ask "play some jazz on Spotify"

​

How Tool Calling Works

1. User input — Voice (STT) or text query arrives at the LLM
2. Relevance filtering — Keyword scoring selects top-k relevant actions (reduces context size for small LLMs)
3. LLM inference — The model generates a tool call in its native format:
   • Qwen3: <tool_call>{"name": "open_app", "arguments": {"app": "Safari"}}</tool_call>
   • LFM2: <|tool_call_start|>{"name": "open_app", "arguments": {"app": "Safari"}}<|tool_call_end|>
4. Parsing — ModelProfile::parse_tool_calls() extracts the action name and JSON arguments
5. Execution — ActionRegistry::execute() runs the action (AppleScript or shell command)
6. Result fusion — The LLM receives the result JSON and generates a natural language response

> open Safari
  ~ [TRACE] Tool call: open_app({"app": "Safari"})
  ~ [TRACE] open_app -> OK: {"success": true, "output": "Opened Safari"}
  RCLI: Done! Safari is now open.

​

All 43 Actions

• ✓ = Enabled by default
• — = Disabled by default (enable in the Actions panel or via CLI)

​

Action Categories

​

Quick Examples

rcli listen
# Say: "Create a note called Team Standup"
# Say: "Play Bohemian Rhapsody on Spotify"
# Say: "What's my battery level?"

​

Next Steps

• Browse actions by category in the left sidebar
• Press A in the TUI to manage actions interactively
• Run rcli actions to list all actions and their status
• See Managing Actions for enable/disable controls