deepctl 0.3.2__tar.gz → 0.4.0__tar.gz

{deepctl-0.3.2/src/deepctl.egg-info → deepctl-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepctl
-Version: 0.3.2
+Version: 0.4.0
 Summary: Official Deepgram CLI for speech recognition and audio intelligence
 Author-email: Deepgram <devrel@deepgram.com>
 Maintainer-email: Deepgram <devrel@deepgram.com>
@@ -27,8 +27,8 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: click>=8.0.0
 Requires-Dist: deepgram-sdk<8,>=7.7.0
-Requires-Dist: deepctl-core>=0.2.18
-Requires-Dist: deepctl-cmd-login>=0.1.19
+Requires-Dist: deepctl-core>=0.3.0
+Requires-Dist: deepctl-cmd-login>=0.2.0
 Requires-Dist: deepctl-cmd-projects>=0.2.0
 Requires-Dist: deepctl-cmd-transcribe>=0.1.12
 Requires-Dist: deepctl-cmd-usage>=0.2.1
@@ -39,14 +39,14 @@ Requires-Dist: deepctl-cmd-debug-browser>=0.1.12
 Requires-Dist: deepctl-cmd-debug-network>=0.1.12
 Requires-Dist: deepctl-cmd-debug-audio>=0.1.14
 Requires-Dist: deepctl-cmd-debug-probe>=0.0.2
-Requires-Dist: deepctl-cmd-debug-toolkit>=0.1.0
+Requires-Dist: deepctl-cmd-debug-toolkit>=0.2.0
 Requires-Dist: deepctl-cmd-ffprobe>=0.0.3
 Requires-Dist: deepctl-cmd-update>=0.2.7
-Requires-Dist: deepctl-cmd-plugin>=0.1.13
-Requires-Dist: deepctl-cmd-skills>=0.0.8
-Requires-Dist: deepctl-cmd-init>=0.0.4
+Requires-Dist: deepctl-cmd-plugin>=0.1.14
+Requires-Dist: deepctl-cmd-skills>=0.0.9
+Requires-Dist: deepctl-cmd-init>=0.1.0
 Requires-Dist: deepctl-cmd-models>=0.1.1
-Requires-Dist: deepctl-cmd-speak>=0.0.4
+Requires-Dist: deepctl-cmd-speak>=0.0.5
 Requires-Dist: deepctl-cmd-keys>=0.1.0
 Requires-Dist: deepctl-cmd-read>=0.1.0
 Requires-Dist: deepctl-cmd-listen>=0.0.14
@@ -268,8 +268,15 @@ 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 -
@@ -288,6 +295,15 @@ echo "Hello" | dg speak -o greeting.mp3 -m aura-2-asteria-en
 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.
@@ -359,14 +375,42 @@ Add to your editor's MCP config:
 
 ### AI Tool Integration
 
-Automatically detect and configure AI coding assistants with Deepgram skills.
+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 `<!-- BEGIN deepctl CLI Reference` and `<!-- END deepctl CLI Reference -->` 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-<name>` 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-<name>` 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-<name>` copy; it does the same if `.deepctl-v03-<name>` 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.

{deepctl-0.3.2 → deepctl-0.4.0}/README.md

@@ -184,8 +184,15 @@ 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 -
@@ -204,6 +211,15 @@ echo "Hello" | dg speak -o greeting.mp3 -m aura-2-asteria-en
 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.
@@ -275,14 +291,42 @@ Add to your editor's MCP config:
 
 ### AI Tool Integration
 
-Automatically detect and configure AI coding assistants with Deepgram skills.
+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 `<!-- BEGIN deepctl CLI Reference` and `<!-- END deepctl CLI Reference -->` 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-<name>` 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-<name>` 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-<name>` copy; it does the same if `.deepctl-v03-<name>` 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.

{deepctl-0.3.2 → deepctl-0.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "deepctl"
-version = "0.3.2" # x-release-please-version
+version = "0.4.0" # x-release-please-version
 description = "Official Deepgram CLI for speech recognition and audio intelligence"
 readme = "README.md"
 license = "MIT"
@@ -35,8 +35,8 @@ requires-python = ">=3.10"
 dependencies = [
     "click>=8.0.0",
     "deepgram-sdk>=7.7.0,<8",
-    "deepctl-core>=0.2.18",
-    "deepctl-cmd-login>=0.1.19",
+    "deepctl-core>=0.3.0",
+    "deepctl-cmd-login>=0.2.0",
     "deepctl-cmd-projects>=0.2.0",
     "deepctl-cmd-transcribe>=0.1.12",
     "deepctl-cmd-usage>=0.2.1",
@@ -47,14 +47,14 @@ dependencies = [
     "deepctl-cmd-debug-network>=0.1.12",
     "deepctl-cmd-debug-audio>=0.1.14",
     "deepctl-cmd-debug-probe>=0.0.2",
-    "deepctl-cmd-debug-toolkit>=0.1.0",
+    "deepctl-cmd-debug-toolkit>=0.2.0",
     "deepctl-cmd-ffprobe>=0.0.3",
     "deepctl-cmd-update>=0.2.7",
-    "deepctl-cmd-plugin>=0.1.13",
-    "deepctl-cmd-skills>=0.0.8",
-    "deepctl-cmd-init>=0.0.4",
+    "deepctl-cmd-plugin>=0.1.14",
+    "deepctl-cmd-skills>=0.0.9",
+    "deepctl-cmd-init>=0.1.0",
     "deepctl-cmd-models>=0.1.1",
-    "deepctl-cmd-speak>=0.0.4",
+    "deepctl-cmd-speak>=0.0.5",
     "deepctl-cmd-keys>=0.1.0",
     "deepctl-cmd-read>=0.1.0",
     "deepctl-cmd-listen>=0.0.14",

{deepctl-0.3.2 → deepctl-0.4.0}/src/deepctl/__init__.py

@@ -1,7 +1,7 @@
 """deepctl - Official command-line interface for Deepgram's speech
 recognition API."""
 
-__version__ = "0.3.2"  # x-release-please-version
+__version__ = "0.4.0"  # x-release-please-version
 __author__ = "Deepgram"
 __email__ = "devrel@deepgram.com"
 __license__ = "MIT"

{deepctl-0.3.2 → deepctl-0.4.0/src/deepctl.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deepctl
-Version: 0.3.2
+Version: 0.4.0
 Summary: Official Deepgram CLI for speech recognition and audio intelligence
 Author-email: Deepgram <devrel@deepgram.com>
 Maintainer-email: Deepgram <devrel@deepgram.com>
@@ -27,8 +27,8 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: click>=8.0.0
 Requires-Dist: deepgram-sdk<8,>=7.7.0
-Requires-Dist: deepctl-core>=0.2.18
-Requires-Dist: deepctl-cmd-login>=0.1.19
+Requires-Dist: deepctl-core>=0.3.0
+Requires-Dist: deepctl-cmd-login>=0.2.0
 Requires-Dist: deepctl-cmd-projects>=0.2.0
 Requires-Dist: deepctl-cmd-transcribe>=0.1.12
 Requires-Dist: deepctl-cmd-usage>=0.2.1
@@ -39,14 +39,14 @@ Requires-Dist: deepctl-cmd-debug-browser>=0.1.12
 Requires-Dist: deepctl-cmd-debug-network>=0.1.12
 Requires-Dist: deepctl-cmd-debug-audio>=0.1.14
 Requires-Dist: deepctl-cmd-debug-probe>=0.0.2
-Requires-Dist: deepctl-cmd-debug-toolkit>=0.1.0
+Requires-Dist: deepctl-cmd-debug-toolkit>=0.2.0
 Requires-Dist: deepctl-cmd-ffprobe>=0.0.3
 Requires-Dist: deepctl-cmd-update>=0.2.7
-Requires-Dist: deepctl-cmd-plugin>=0.1.13
-Requires-Dist: deepctl-cmd-skills>=0.0.8
-Requires-Dist: deepctl-cmd-init>=0.0.4
+Requires-Dist: deepctl-cmd-plugin>=0.1.14
+Requires-Dist: deepctl-cmd-skills>=0.0.9
+Requires-Dist: deepctl-cmd-init>=0.1.0
 Requires-Dist: deepctl-cmd-models>=0.1.1
-Requires-Dist: deepctl-cmd-speak>=0.0.4
+Requires-Dist: deepctl-cmd-speak>=0.0.5
 Requires-Dist: deepctl-cmd-keys>=0.1.0
 Requires-Dist: deepctl-cmd-read>=0.1.0
 Requires-Dist: deepctl-cmd-listen>=0.0.14
@@ -268,8 +268,15 @@ 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 -
@@ -288,6 +295,15 @@ echo "Hello" | dg speak -o greeting.mp3 -m aura-2-asteria-en
 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.
@@ -359,14 +375,42 @@ Add to your editor's MCP config:
 
 ### AI Tool Integration
 
-Automatically detect and configure AI coding assistants with Deepgram skills.
+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 `<!-- BEGIN deepctl CLI Reference` and `<!-- END deepctl CLI Reference -->` 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-<name>` 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-<name>` 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-<name>` copy; it does the same if `.deepctl-v03-<name>` 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.

{deepctl-0.3.2 → deepctl-0.4.0}/src/deepctl.egg-info/requires.txt

@@ -1,7 +1,7 @@
 click>=8.0.0
 deepgram-sdk<8,>=7.7.0
-deepctl-core>=0.2.18
-deepctl-cmd-login>=0.1.19
+deepctl-core>=0.3.0
+deepctl-cmd-login>=0.2.0
 deepctl-cmd-projects>=0.2.0
 deepctl-cmd-transcribe>=0.1.12
 deepctl-cmd-usage>=0.2.1
@@ -12,14 +12,14 @@ deepctl-cmd-debug-browser>=0.1.12
 deepctl-cmd-debug-network>=0.1.12
 deepctl-cmd-debug-audio>=0.1.14
 deepctl-cmd-debug-probe>=0.0.2
-deepctl-cmd-debug-toolkit>=0.1.0
+deepctl-cmd-debug-toolkit>=0.2.0
 deepctl-cmd-ffprobe>=0.0.3
 deepctl-cmd-update>=0.2.7
-deepctl-cmd-plugin>=0.1.13
-deepctl-cmd-skills>=0.0.8
-deepctl-cmd-init>=0.0.4
+deepctl-cmd-plugin>=0.1.14
+deepctl-cmd-skills>=0.0.9
+deepctl-cmd-init>=0.1.0
 deepctl-cmd-models>=0.1.1
-deepctl-cmd-speak>=0.0.4
+deepctl-cmd-speak>=0.0.5
 deepctl-cmd-keys>=0.1.0
 deepctl-cmd-read>=0.1.0
 deepctl-cmd-listen>=0.0.14