Analyze JSON structure of a command output WITHOUT showing raw JSON. USE WHEN: You don't know the JSON structure and need JSON/object paths. HOW: Pass COMMAND (not JSON) -> Returns paths with types (formatted for powershell or jq depending on current shell). EXAMPLE: analyze_json(command='aws lambda list-functions') -> On PowerShell: .Functions.FunctionName | string -> On Bash/Zsh: .Functions[].FunctionName | string Then use the appropriate ConvertFrom-Json or jq query in run_shell_command.

Retrieve cached output from previous command. USE WHEN: Output was truncated, user asks about earlier command, need specific lines. LINE SELECTION: '-100' -> Last 100 lines (best for logs) '+50' -> First 50 lines '+20,-80' -> First 20 + last 80 '10-50' -> Lines 10-50 (omit) -> Full output (50K limit) EXAMPLE: get_cached_output(cache_id='cmd_001', lines='-100')

Execute a shell command on the remote SSH server. CRITICAL - Minimize Output: - ALWAYS filter at source (jq, grep, head) - For file searches: ALWAYS limit results RULES: - Output shown to user - DON'T repeat in response - NEVER use echo to communicate - Use this instead of run_shell_command when working on the remote machine. SAFETY: - is_safe=true: read-only (ls, cat, grep) - runs immediately - is_safe=false: destructive (rm, dd) - needs user approval - Command visible to user before execution

Execute a shell command on the user's machine. CRITICAL - Minimize Output: - ALWAYS filter at source (ConvertFrom-Json / Select-Object on PowerShell, jq / head on Bash/Zsh) - For AWS/cloud: pipe to jq (Bash/Zsh) or ConvertFrom-Json (PowerShell) for specific fields - For file searches: ALWAYS limit results (Select-Object -First 50, head -50) Examples: ✅ (Bash/Zsh) aws lambda list-functions | jq '.Functions[].FunctionName' ✅ (PowerShell) (aws lambda list-functions | ConvertFrom-Json).Functions.FunctionName ✅ Get-ChildItem -Recurse -Filter '*.py' | Select-Object -First 50 ✅ find . -name '*.py' -type f | head -50 ❌ aws lambda list-functions (dumps everything) ❌ Get-ChildItem -Recurse (no limit) RULES: - Use shell-appropriate commands for detected OS/shell - Output shown to user - DON'T repeat in response - NEVER use echo to communicate - For git: use --no-pager (git --no-pager diff) SAFETY: - is_safe=true: read-only (dir, cat, grep) - runs immediately - is_safe=false: destructive (rm, dd) - needs user approval - Command visible to user before execution