# Deepgram CLI [![Test](https://github.com/deepgram/cli/actions/workflows/test.yml/badge.svg)](https://github.com/deepgram/cli/actions/workflows/test.yml) [![Version](https://img.shields.io/pypi/v/deepctl)](https://pypi.org/project/deepctl/) [![Python](https://img.shields.io/pypi/pyversions/deepctl)](https://pypi.org/project/deepctl/) [![License](https://img.shields.io/github/license/deepgram/cli)](https://github.com/deepgram/cli/blob/main/LICENSE) ```sh Usage: dg [OPTIONS] COMMAND [ARGS]... ████████████████ ██████████████████ ████████████████████ █████████████████████ ███████ ████████ ███████ ███████ ████████ ███████████████ ████████████████ ████████████████ ████████████████ deepctl — Official Deepgram CLI STT · TTS · Audio Intelligence ``` The official Deepgram CLI brings speech-to-text, text-to-speech, audio intelligence, and project management directly into your terminal. Aliases: `deepctl`, `deepgram`, `dg`. ## Installation ### Quick Install **macOS / Linux (Homebrew):** ```bash # Install and trust only the Deepgram formula. brew install deepgram/tap/deepgram ``` Homebrew brings in `ffmpeg` and `portaudio` automatically — `dg listen --mic`, `dg debug probe`, and raw audio piping all work without further setup. To upgrade later: `brew upgrade deepgram`. **macOS / Linux (curl):** ```bash curl -fsSL https://deepgram.com/install.sh | sh ``` **Windows (PowerShell):** ```powershell iwr https://deepgram.com/install.ps1 -useb | iex ``` ### Package Managers ```bash pip install deepctl # pip uv tool install deepctl # uv pipx install deepctl # pipx ``` ### Try Without Installing ```bash uvx deepctl --help pipx run deepctl --help ``` ## Getting Started ```bash # Authenticate with Deepgram dg login # Transcribe an audio file dg listen recording.wav # Text-to-speech (Flux TTS by default) dg speak "Hello from Deepgram" -o hello.wav # Live microphone transcription dg listen --mic # Analyze text for sentiment and topics dg read "The product is amazing" --sentiment --topics ``` ## Examples ### Speech-to-text ```bash # File or URL — auto-detected dg listen keynote.mp3 --diarize --model nova-3 dg listen https://cdn.example.com/podcast.mp3 # Pipe to jq for scripting dg -o json listen standup.mp3 \ | jq '.results.channels[0].alternatives[0].transcript' # Live microphone with interim (partial) results dg listen --mic --model nova-3 --interim # Redact sensitive numbers and spell numbers as digits (files or live) # Flux STT (v2) accepts --redact numbers|aggressive_numbers; v1 also pci, ssn, … dg listen call.wav --redact numbers --numerals # Raw audio stream from ffmpeg ffmpeg -i video.mp4 -f s16le -ar 16000 -ac 1 - \ | dg listen --encoding linear16 ``` ### Captions (WebVTT & SRT) ```bash # Generate a WebVTT file dg listen keynote.mp3 --webvtt --save-to keynote.vtt # SRT with speaker labels dg listen interview.mp3 --srt --diarize --save-to interview.srt # Stream live captions from the microphone dg listen --mic --webvtt # Captions from a video via ffmpeg ffmpeg -i video.mp4 -f s16le -ar 16000 -ac 1 - \ | dg listen --encoding linear16 --srt ``` ### Text intelligence ```bash dg read earnings.txt --sentiment --summarize --topics ``` ### Text-to-speech ```bash # Stream directly to a player (Flux TTS streams a WAV; -loglevel error hides # ffmpeg's cosmetic end-of-stream notice) dg speak "Hello from Deepgram" | ffplay -loglevel error -nodisp -autoexit - ``` ### Account & project management ```bash dg whoami # Auth status dg projects --list # List projects dg keys --create --comment 'ci-pipeline' --dry-run # Dry-run key creation dg usage --last-month # Usage stats dg requests --status failed --endpoint listen # Debug failed requests ``` ### Raw API & MCP ```bash # Hit any endpoint directly dg api /v1/projects --jq '.projects[0].name' # MCP server for AI editors (Claude Code, Cursor, etc.) dg mcp --transport sse --port 8000 ``` ## Features ### Speech-to-Text Transcribe audio files, URLs, or live microphone input. ```bash dg listen meeting.wav --diarize --smart-format dg listen https://example.com/audio.mp3 --model nova-3 dg listen --mic --model nova-3 --language en-US cat audio.raw | dg listen --encoding linear16 --sample-rate 16000 ``` ### Text-to-Speech Convert text to natural speech. Supports file output and piping. By default `dg speak` uses Flux TTS (`flux-alexis-en`) — the Speak v2 WebSocket API, which streams and emits raw audio; its `linear16` output is wrapped in a WAV container so it is directly playable. Pass an `aura-*` model to use the Speak v1 batch REST API instead, which supports containerized formats like MP3. ```bash # Quickstart — synthesize and hear it straight away dg speak "Hello from Deepgram" --play # Discover voices dg speak --list-voices # Flux TTS (v2, WebSocket streaming) — the default dg speak "Hello from Flux" -o hello.wav dg speak "Save it and play it" -o hello.wav --play # Piped audio is a streaming WAV; -loglevel error hides ffmpeg's cosmetic # end-of-stream notice (the audio is complete). dg speak "Hello from Flux" | ffplay -loglevel error -nodisp -autoexit - # Flux TTS streaming controls (flux-* only): --speed 0.85–1.15 (0.05 steps). # --expressivity -2..2 is beta; its default 0 is nominal delivery. dg speak "A little slower" --speed 0.9 --expressivity 1 -o slow.wav # Aura (v1, batch REST) — opt in with -m aura-*; needed for MP3 output dg speak "Welcome to Deepgram" -o welcome.mp3 -m aura-2-asteria-en dg speak --file script.txt -o output.mp3 -m aura-2-luna-en echo "Hello" | dg speak -o greeting.mp3 -m aura-2-asteria-en # Aura-2 also has Spanish voices (e.g. aura-2-selena-es); run `dg models` # for the full, current list. dg speak "Hola, bienvenido a Deepgram" -o hola.mp3 -m aura-2-selena-es ``` `--play` uses the first available system player (`ffplay`, `afplay`, `paplay`, or `aplay`); install `ffmpeg` if none is present. With the Flux default the audio is streamed into the player as it arrives, so playback starts at first-audio latency rather than after the whole utterance. Each fallback player is checked against the requested format before the API call: `aplay` plays PCM/WAV only and `paplay` adds FLAC and Opus but not MP3 or AAC, while `ffplay` and `afplay` (macOS) play every format. Playing Aura's default MP3 on Linux needs `ffplay` or `--encoding flac`. ### Text Intelligence Analyze text for sentiment, summaries, topics, and intents. ```bash dg read "Customer called about billing" --sentiment --summarize dg read --file article.txt --topics --intents cat feedback.txt | dg read --sentiment ``` ### Project Management Manage your Deepgram account from the terminal. ```bash dg projects --list # List projects dg keys --list # List API keys dg keys --create --comment "staging" # Create API key dg members # List team members dg members --invite user@co.com # Invite member dg usage --last-month # View usage stats dg billing # Check balances dg requests --limit 20 --status failed # Request history dg models --type tts # List available models ``` ### Direct API Access Make authenticated requests to any Deepgram endpoint. ```bash dg api /v1/projects dg api /v1/projects -X POST -f name="New Project" dg api /v1/listen -X POST --input audio.wav --jq '.results' ``` ### Debugging Tools Diagnose audio, network, and browser issues. ```bash dg debug audio --file recording.wav # Analyze audio compatibility dg debug network --verbose # Test connectivity to Deepgram dg debug probe --port 3100 # Live stream audio analysis ``` ### MCP Server Connect Deepgram tools to AI coding assistants (Claude Code, Cursor, etc.). ```bash dg mcp # Start MCP server (stdio) dg mcp --transport sse --port 8000 # SSE transport ``` Add to your editor's MCP config: ```json { "mcpServers": { "deepgram": { "type": "stdio", "command": "dg", "args": ["mcp"] } } } ``` ### AI Tool Integration Install the Deepgram skills as folders in each AI coding assistant's skills folder. ```bash dg skills status # Detect AI tools dg skills setup # Interactive setup wizard dg skills install --all # Install for all detected tools dg skills update # Replace the folders deepctl installed dg skills remove --all # Delete the folders deepctl installed ``` | Tool | Skills folder | |---|---| | Claude Code | `~/.claude/skills` | | OpenAI Codex | `~/.agents/skills` | | Gemini CLI | `~/.gemini/skills` | | Cursor | `~/.cursor/skills` | | OpenCode | `~/.config/opencode/skills` | | Cline | `~/.cline/skills` | | Amazon Q Developer, Aider | none: deepctl prints where to get the skills | deepctl replaces or deletes a folder only if skills.json records it for that tool, it is a real folder directly in that tool's skills folder, it holds deepctl's `.deepctl-skill` marker, and its contents are exactly what deepctl installed. So folders from `npx skills add`, and symlinked skill folders, are left alone. These commands abort if the filesystem cannot provide locking or no-replace directory moves. Installed skill folders and skills.json stay as they were, though the tool's skills folder and `~/.deepctl/skills/skills.json.lock` may already have been created. While another `dg skills`, `dg login` or `dg plugin` command is changing skills, the next one waits up to 30 seconds for it to finish. If another of these commands removes or changes a tool's skills while `dg skills update` or a plugin refresh is running, the refresh leaves that tool as the other command left it and prints a warning. That holds even for the same ref, because a branch such as `main` can move between two downloads. `dg skills update` run with `--ref` still applies its ref to a tool another command updated, but does not reinstall skills another command removed. `dg login` offers to install the skills, and `dg plugin install`, `update` and `remove` refresh the installed ones, through the same path as `dg skills install` and `update`. A skills installation failure prints a warning on stderr and does not change those commands' exit codes. Ctrl-C still cancels the command. If you edit a deepctl folder, or add a file or link to it, deepctl leaves it alone: `update` stops without changing anything and `remove` won't delete it. To get updates again, rename or move your edited copy, or delete it yourself. Opening a skill folder in Finder or Explorer can add `.DS_Store`, `Thumbs.db` or `desktop.ini`, which counts as an edit. #### Upgrading from deepctl 0.2.16 through 0.3.x On macOS and Linux, once `dg skills install` or `update` (or `dg login`, or `dg plugin install`, `update` or `remove`) has installed a tool's skill folders, deepctl removes the files older deepctl wrote for that tool, and prints which ones on stderr: `~/.claude/commands/deepgram/*.md`, `~/.cursor/rules/deepctl.mdc`, `~/.cline/rules/deepctl.md`, and the section between the `` lines in `~/.codex/instructions.md`, `~/.gemini/GEMINI.md` and `~/.opencode/agents.md`. In those three files, everything between the two marker lines is removed, including anything you changed there; the rest of the file is kept, apart from the blank line deepctl added before its section. Deepctl keeps the original file next to it as `.deepctl-kept-v03-*`; compare it for any late write from an open editor, then delete it if you do not need it. deepctl removes a file only if its content is exactly a deepgram/skills version that older deepctl copied, even if you made that copy yourself. It keeps a file you edited, a link, a file in a folder reached through a link (such as a dotfiles `~/.claude`), and a section that is incomplete, repeated or in a read-only or locked file, and warns once about each file 0.3.x recorded. An I/O failure, such as permission denied, is retried on the next install or update, with a warning for files 0.3.x recorded. Amazon Q Developer and Aider files (`~/.amazonq/rules/deepctl.md`, `~/.deepctl/skills/deepctl-conventions.md`) are kept, because those tools have no skill folders; if you delete Aider's, also remove its entry under `read:` in `~/.aider.conf.yml`. On Windows, deepctl leaves this 0.3.x content untouched because a parent folder could become a junction during cleanup; remove it yourself if you do not need it. While deepctl works on a file on macOS or Linux, it moves it to `.deepctl-v03-` in the same folder. If deepctl is interrupted, the next install or update puts the file back and says so. If both the file and its `.deepctl-v03-` are there, as after you saved the file while deepctl was editing it, deepctl changes neither and names both on each run until you compare them and delete the `.deepctl-v03-` copy; it does the same if `.deepctl-v03-` is a link or folder deepctl didn't make. A `.deepctl-v03-*.tmp` file is an unused draft; delete it. ### Starter Apps Scaffold a new project from Deepgram templates. ```bash dg init --list # Browse templates dg init node-live-transcription # Clone and set up ``` ## CI / Automation Every command is CI-friendly. Authentication works via environment variables, all interactive prompts have flag-based alternatives, and destructive operations require explicit `--yes`. ```bash # CI authentication export DEEPGRAM_API_KEY="your-key" export DEEPGRAM_PROJECT_ID="your-project-id" # Non-interactive usage dg listen recording.wav dg speak "Deploy complete" -o notification.mp3 -m aura-2-asteria-en dg keys --create --comment "ci-key" --scopes member dg keys --delete KEY_ID --yes dg read --file report.txt --summarize # Output formats for scripting dg projects --list -o json dg keys --list -o csv dg usage --last-week -o yaml ``` In CI, in AI coding tools, and in any fully non-interactive environment with no terminal attached (cron, systemd, `docker run` without `-t`), the CLI detects the context and automatically switches to structured JSON output with plain-text status messages. A plain pipe on its own does not trigger this — `dg projects | jq` from an interactive shell still gets the human-readable table, so pass `-o json` explicitly when you are piping by hand. ### Exit codes Since 0.3.0, `dg` exits non-zero when a command fails — branch on the exit code, not on parsing output: | Code | Meaning | | --- | --- | | `0` | Success | | `1` | Error — a failed command, a crash, or a usage error (bad flag, unknown command) | | `2` | Cancelled by the user (Ctrl-C, or declining a confirmation prompt) | Note that `dg` reports `2` for an interrupt rather than the shell's conventional `130`, so the code is the same whether the cancellation came from Ctrl-C or from declining a prompt. Human-readable status and error messages go to stderr, and stdout carries the result. With an explicit structured-output mode, authentication-guard failures and commands that return an error result write a payload with `"status": "error"` to stdout — authentication failures, `dg ffprobe`, and `dg debug audio` included. Usage errors and handler-raised exceptions report on stderr and can leave stdout empty. Branch on the exit code rather than on whether stdout parsed. If a CI step relied on `dg` always exiting `0` (every command did, before 0.3.0), it will now fail where it previously passed silently. ### Forcing non-interactive mode Three explicit ways to skip every prompt and run with defaults — useful from a real terminal where auto-detection wouldn't otherwise trigger: ```bash # Global flag (before any command, or after a leaf command) dg --non-interactive listen recording.wav dg listen --non-interactive recording.wav # Environment variable (good for whole scripts) CI=1 dg listen recording.wav ``` Also recognised: `--agent-friendly` (alias intended for AI coding tools — same effect plus JSON metadata output), and the auto-detected env vars `CLAUDECODE`, `CLAUDE_CODE_ENTRYPOINT`, `CODEX_SANDBOX`, and Aider's `OR_APP_NAME` / `OR_SITE_URL`. ## Plugins Extend the CLI with custom commands. ```bash dg plugin search deepctl- # Find plugins dg plugin install # Install dg plugin list # List installed dg plugin remove # Remove ``` Create your own — see the [plugin example](packages/deepctl-plugin-example). ## Configuration **Priority:** CLI flags > environment variables > profile config > project config ```bash dg login # Interactive or --api-key dg login --profile staging --api-key SK # Named profiles dg profiles --list # List profiles dg profiles --switch staging # Switch profile ``` For structured output, use `--output json|yaml|table|csv` after leaf commands that do not define their own output option, or before any command as a global flag: `dg --output json `. `dg speak --output FILE` writes audio to `FILE`, so use `dg --output json speak ...` for Speak's structured output. ## Telemetry The CLI phones home anonymous error reports to help us catch crashes and regressions before users have to file an issue. It's **on by default** and easy to turn off. **What's collected:** Python exceptions, stack traces, the CLI version, and the Python runtime. Request bodies, headers, cookies, API keys, email addresses, IP addresses, and usernames are scrubbed before send. No performance traces, no profiling, no replays — errors only. **Where it goes:** the `dx-cli` Sentry project owned by the Deepgram DX team. ### Opt out Persistent (recommended) — add this to your `config.yaml` (`~/.config/deepctl/config.yaml` on Linux, `~/Library/Application Support/deepctl/config.yaml` on macOS, `%LOCALAPPDATA%\deepgram\deepctl\config.yaml` on Windows): ```yaml telemetry: enabled: false ``` One-shot (CI, scripts, single command): ```bash DEEPCTL_TELEMETRY_DISABLED=1 dg listen recording.wav ``` ### Override the destination For forks or self-hosted Sentry, point telemetry at your own DSN: ```bash export DEEPCTL_TELEMETRY_DSN='https://@/' ``` `DEEPCTL_TELEMETRY_DISABLED` always wins. The default DSN is baked into the package and only used when the override is unset. ## Development ```bash git clone https://github.com/deepgram/cli && cd cli uv sync --group dev make dev # Format + lint + test make check # Format + lint + typecheck (no tests) ``` ### Architecture ``` cli/ ├── src/deepctl/ # Main CLI entry point ├── packages/ │ ├── deepctl-cmd-api/ # API command for deepctl │ ├── deepctl-cmd-billing/ # Billing command for deepctl │ ├── deepctl-cmd-completion/ # Shell completion command for deepctl │ ├── deepctl-cmd-debug/ # Debug command group for deepctl │ ├── deepctl-cmd-debug-audio/ # Audio debug subcommand for deepctl │ ├── deepctl-cmd-debug-browser/ # Browser debug subcommand for deepctl │ ├── deepctl-cmd-debug-network/ # Network debug subcommand for deepctl │ ├── deepctl-cmd-debug-probe/ # Debug probe subcommand for deepctl — live ffprobe analysis during streaming │ ├── deepctl-cmd-debug-toolkit/ # Toolkit subcommand for dg debug — runs field support scripts from deepgram/support-toolkit │ ├── deepctl-cmd-ffprobe/ # FFprobe configuration command for deepctl │ ├── deepctl-cmd-init/ # Init command for deepctl — scaffold Deepgram starter apps │ ├── deepctl-cmd-keys/ # API keys management command for deepctl │ ├── deepctl-cmd-listen/ # Listen (live speech-to-text) command for deepctl │ ├── deepctl-cmd-login/ # Login command for deepctl │ ├── deepctl-cmd-mcp/ # MCP proxy command for deepctl — connects to Deepgram's developer API │ ├── deepctl-cmd-members/ # Members management command for deepctl │ ├── deepctl-cmd-models/ # Models command for deepctl │ ├── deepctl-cmd-plugin/ # Plugin management command for deepctl │ ├── deepctl-cmd-projects/ # Projects command for deepctl │ ├── deepctl-cmd-read/ # Read (text intelligence) command for deepctl │ ├── deepctl-cmd-requests/ # Requests history command for deepctl │ ├── deepctl-cmd-skills/ # AI coding assistant skill management for deepctl │ ├── deepctl-cmd-speak/ # Speak (text-to-speech) command for deepctl │ ├── deepctl-cmd-transcribe/ # Transcribe command for deepctl │ ├── deepctl-cmd-update/ # Update command for deepctl │ ├── deepctl-cmd-usage/ # Usage command for deepctl │ ├── deepctl-core/ # Core components for deepctl │ ├── deepctl-plugin-example/ # Example plugin for deepctl │ ├── deepctl-shared-utils/ # Shared utilities for deepctl │ └── deepctl-telemetry/ # Opt-out phone-home telemetry for deepctl ├── tests/ # Integration tests └── Makefile # Development tasks ``` ### Commands | Command | Description | |---------|-------------| | `deepctl api` | API command for deepctl | | `deepctl billing` | Billing command for deepctl | | `deepctl completion` | Shell completion command for deepctl | | `deepctl debug audio` | Audio debug subcommand for deepctl | | `deepctl debug browser` | Browser debug subcommand for deepctl | | `deepctl debug network` | Network debug subcommand for deepctl | | `deepctl debug probe` | Debug probe subcommand for deepctl — live ffprobe analysis during streaming | | `deepctl debug toolkit` | Toolkit subcommand for dg debug — runs field support scripts from deepgram/support-toolkit | | `deepctl debug` | Debug command group for deepctl | | `deepctl ffprobe` | FFprobe configuration command for deepctl | | `deepctl init` | Init command for deepctl — scaffold Deepgram starter apps | | `deepctl keys` | API keys management command for deepctl | | `deepctl listen` | Listen (live speech-to-text) command for deepctl | | `deepctl login` | Login command for deepctl | | `deepctl logout` | Login command for deepctl | | `deepctl mcp` | MCP proxy command for deepctl — connects to Deepgram's developer API | | `deepctl members` | Members management command for deepctl | | `deepctl models` | Models command for deepctl | | `deepctl plugin` | Plugin management command for deepctl | | `deepctl profiles` | Login command for deepctl | | `deepctl projects` | Projects command for deepctl | | `deepctl read` | Read (text intelligence) command for deepctl | | `deepctl requests` | Requests history command for deepctl | | `deepctl skills` | AI coding assistant skill management for deepctl | | `deepctl speak` | Speak (text-to-speech) command for deepctl | | `deepctl transcribe` | Transcribe command for deepctl | | `deepctl update` | Update command for deepctl | | `deepctl usage` | Usage command for deepctl | | `deepctl whoami` | Login command for deepctl | ### Packages | Package | Description | |---------|-------------| | [`deepctl-cmd-api`](packages/deepctl-cmd-api) | API command for deepctl | | [`deepctl-cmd-billing`](packages/deepctl-cmd-billing) | Billing command for deepctl | | [`deepctl-cmd-completion`](packages/deepctl-cmd-completion) | Shell completion command for deepctl | | [`deepctl-cmd-debug`](packages/deepctl-cmd-debug) | Debug command group for deepctl | | [`deepctl-cmd-debug-audio`](packages/deepctl-cmd-debug-audio) | Audio debug subcommand for deepctl | | [`deepctl-cmd-debug-browser`](packages/deepctl-cmd-debug-browser) | Browser debug subcommand for deepctl | | [`deepctl-cmd-debug-network`](packages/deepctl-cmd-debug-network) | Network debug subcommand for deepctl | | [`deepctl-cmd-debug-probe`](packages/deepctl-cmd-debug-probe) | Debug probe subcommand for deepctl — live ffprobe analysis during streaming | | [`deepctl-cmd-debug-toolkit`](packages/deepctl-cmd-debug-toolkit) | Toolkit subcommand for dg debug — runs field support scripts from deepgram/support-toolkit | | [`deepctl-cmd-ffprobe`](packages/deepctl-cmd-ffprobe) | FFprobe configuration command for deepctl | | [`deepctl-cmd-init`](packages/deepctl-cmd-init) | Init command for deepctl — scaffold Deepgram starter apps | | [`deepctl-cmd-keys`](packages/deepctl-cmd-keys) | API keys management command for deepctl | | [`deepctl-cmd-listen`](packages/deepctl-cmd-listen) | Listen (live speech-to-text) command for deepctl | | [`deepctl-cmd-login`](packages/deepctl-cmd-login) | Login command for deepctl | | [`deepctl-cmd-mcp`](packages/deepctl-cmd-mcp) | MCP proxy command for deepctl — connects to Deepgram's developer API | | [`deepctl-cmd-members`](packages/deepctl-cmd-members) | Members management command for deepctl | | [`deepctl-cmd-models`](packages/deepctl-cmd-models) | Models command for deepctl | | [`deepctl-cmd-plugin`](packages/deepctl-cmd-plugin) | Plugin management command for deepctl | | [`deepctl-cmd-projects`](packages/deepctl-cmd-projects) | Projects command for deepctl | | [`deepctl-cmd-read`](packages/deepctl-cmd-read) | Read (text intelligence) command for deepctl | | [`deepctl-cmd-requests`](packages/deepctl-cmd-requests) | Requests history command for deepctl | | [`deepctl-cmd-skills`](packages/deepctl-cmd-skills) | AI coding assistant skill management for deepctl | | [`deepctl-cmd-speak`](packages/deepctl-cmd-speak) | Speak (text-to-speech) command for deepctl | | [`deepctl-cmd-transcribe`](packages/deepctl-cmd-transcribe) | Transcribe command for deepctl | | [`deepctl-cmd-update`](packages/deepctl-cmd-update) | Update command for deepctl | | [`deepctl-cmd-usage`](packages/deepctl-cmd-usage) | Usage command for deepctl | | [`deepctl-core`](packages/deepctl-core) | Core components for deepctl | | [`deepctl-plugin-example`](packages/deepctl-plugin-example) | Example plugin for deepctl | | [`deepctl-shared-utils`](packages/deepctl-shared-utils) | Shared utilities for deepctl | | [`deepctl-telemetry`](packages/deepctl-telemetry) | Opt-out phone-home telemetry for deepctl | ## Release Merging [conventional commits](https://www.conventionalcommits.org/) to `main` triggers [release-please](https://github.com/googleapis/release-please) to open a release PR. Merging that PR creates tags and publishes all changed packages to PyPI. Each package is versioned independently. ## Requirements - Python 3.10+ - Cross-platform: Linux, Windows, macOS ## Contributing 1. Fork the repository 2. `uv sync --group dev` 3. `make dev` (formats, lints, tests) 4. Submit a pull request See [CONTRIBUTING.md](CONTRIBUTING.md) for the contributor workflow. ## Links - [Documentation](https://developers.deepgram.com/docs/cli) - [API Reference](https://developers.deepgram.com/reference) - [Discord](https://discord.gg/deepgram) - [Issues](https://github.com/deepgram/cli/issues) ## License MIT