Zeph configuration reference for LLM providers, memory, tools, channels, and features. Use when the user asks about setup, configuration, environment variables, TOML settings, or how to enable specific features like Telegram, Qdrant, A2A, MCP, Candle, or orchestrator. Keywords: config, setup, install, configure, toml, environment, provider, feature, enable.
Switch to ultra-compressed, telegraphic output. Use when the user asks for terse, brief, minimal, "caveman", or no-fluff answers; wants responses with articles and filler words dropped; or requests maximally short fragments. Keeps code blocks, file paths, commands, and identifiers intact and verbatim.
Cross-platform OS automation — send desktop notifications, read and write the clipboard, take screenshots, open files and URLs in default apps, launch and manage applications, control system volume, check WiFi status, create scheduled tasks and cron jobs, and manage display brightness. Use when the user asks to send a notification, copy to clipboard, take a screenshot, open a file or URL, launch an app, adjust volume, check WiFi, schedule a task, or control OS UI and system settings on macOS, Windows, or Linux. Do not use for running arbitrary shell commands or scripts — use the shell tool instead.
Monitor, manage, and control system processes. Use when the user asks to list running processes, find a process by name or PID, kill or terminate processes, manage background jobs, check resource usage, set resource limits, manage system services with systemctl or launchctl, or troubleshoot CPU and RAM usage with ps, top, htop, kill, pgrep, and related tools.
Handoff protocol for the Rust multi-agent development team (rust-architect, rust-developer, rust-testing-engineer, rust-performance-engineer, rust-security-maintenance, rust-code-reviewer, rust-cicd-devops, rust-debugger, rust-critic). Use only when orchestrating subagents via structured YAML files in .local/handoff/. Not for general agent interactions or memory updates.
Send HTTP API requests using curl. Use when the user asks to call an API, fetch data from a URL, send POST/PUT/PATCH/DELETE requests, work with REST or GraphQL endpoints, upload files, authenticate with Bearer tokens or API keys, debug HTTP responses, or interact with any web service via HTTP.
Browser automation via Playwright MCP — navigate pages, click elements, fill forms, take screenshots, extract text, manage tabs, and run JavaScript in the browser. Use when the user asks to open a website, interact with a web page, scrape dynamic content, fill out forms, take a page screenshot, test a web application, or automate browser workflows. Requires a Playwright MCP server configured in [[mcp.servers]].
LSP-based code analysis via mcpls MCP server. Use for compiler-accurate type inspection, go-to-definition, find-all-references, diagnostics, call hierarchy, workspace symbol search, code actions, rename refactoring, and document formatting. Provides real compiler errors — not guesses. Keywords: LSP, language server, type, definition, references, diagnostics, hover, symbol, call hierarchy, rename, refactor, code actions, rust-analyzer, pyright, gopls, clangd.