Skip to content

Run Tools with Voice Commands

Goal

Use spoken trigger phrases to route dictated text into HTTP endpoints or shell command templates for local automation.

Why This Pattern Exists

Trigger routing is designed for intent-based automation layered on top of dictation. The rationale:

  • Natural language stays the input surface.
  • Trigger phrases define explicit automation boundaries.
  • Template variables ({{TEXT}}, {{AFTER_TRIGGER}}, etc.) let you pass context safely.

Keeping this in a dedicated profile avoids mixing regular prose dictation with command execution behavior.

Safety First Principles

  • Start with non-destructive commands.
  • Test every route in the Trigger Command Designer before real usage.
  • Keep command profile separate from your writing profile.
  • Enable auto-paste suppression when routes match to avoid accidental insertion.

Preset: Developer Command Profile

Setting Where Value Why
Profile name Profiles -> Profile Developer - Commands Isolates automation behavior from normal dictation.
Trigger Routing Enabled Profiles -> Trigger Routing On Activates route matching and execution.
Trigger Routing Library Profiles -> Trigger Routing Dev Command Routes Keeps command routes grouped and portable.
Disable auto paste on trigger routing Profiles -> Trigger Routing On Prevents command text from being pasted when a route fires.
Auto paste into active window Profiles -> Profile On or Off On for non-route dictation, Off for strict command mode.
LLM Enabled Profiles -> LLM Off (recommended initially) Keeps command phrases deterministic.
Word Replacement Enabled Profiles -> Word Replacements On (optional) Useful if you normalize common command aliases.
Add transcriptions to temporary history Profiles -> Profile On Maintains quick audit of recent inputs.

Trigger Routing Library Preset: Dev Command Routes

Route 1: Run a Local HTTP Webhook

Field Value
Route name Run Webhook
Trigger phrase call webhook
Match mode Contains
Action type HTTP/HTTPS
Method POST
Host 127.0.0.1
Port 8080
Path /voice-command
Header Content-Type: application/json
Payload template {"command":"{{AFTER_TRIGGER}}","fullText":"{{TEXT}}"}

Route 2: Local Shell Script Wrapper

Field Value
Route name Run Script
Trigger phrase run script
Match mode Starts With
Action type Shell Command
Command template echo {{AFTER_TRIGGER}}

Start with simple echo behavior first. Replace with a vetted wrapper script only after preview/testing succeeds.

Setup Sequence

  1. Create profile Developer - Commands.
  2. Enable Trigger Routing and assign Dev Command Routes.
  3. Enable Disable auto paste on trigger routing.
  4. Build first route in Trigger Command Designer.
  5. Use sample transcription and Test Command until output matches expectation.
  6. Add one route at a time and retest.

Validation Checklist

  • Matching trigger fires action and shows expected response.
  • Non-trigger dictation does not accidentally execute routes.
  • Auto-paste suppression works when a trigger route matches.
  • Route behavior remains stable across small phrasing variations.

Tuning Guidance

  • If routes trigger too often: switch match mode from Contains to Starts With or tighten phrases.
  • If commands need multi-step logic: route to a stable script endpoint rather than embedding large shell templates.
  • If you want multiple commands in one sentence: evaluate Split Routing with connector trimming.

Quick Tips

  • Trigger routing evaluates every enabled match, not just the first one. Use a dedicated command profile so overlapping phrases cannot silently combine with ordinary writing behavior.
  • Keep auto-paste suppression enabled for command profiles. A successful route can then act without also inserting the spoken command into whichever application is focused.

See Also

Visual Notes

  • TODO: add screenshot of command profile settings.
  • TODO: add screenshot of command designer with sample trigger text.
  • TODO: add GIF speaking a trigger phrase and showing command test response.