duet-cli 0.2.0__tar.gz → 0.2.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {duet_cli-0.2.0/duet_cli.egg-info → duet_cli-0.2.1}/PKG-INFO +7 -3
- {duet_cli-0.2.0 → duet_cli-0.2.1}/README.md +6 -2
- {duet_cli-0.2.0 → duet_cli-0.2.1/duet_cli.egg-info}/PKG-INFO +7 -3
- {duet_cli-0.2.0 → duet_cli-0.2.1}/pyproject.toml +1 -1
- {duet_cli-0.2.0 → duet_cli-0.2.1}/LICENSE +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/duet.py +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/duet_cli.egg-info/SOURCES.txt +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/duet_cli.egg-info/dependency_links.txt +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/duet_cli.egg-info/entry_points.txt +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/duet_cli.egg-info/requires.txt +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/duet_cli.egg-info/top_level.txt +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/setup.cfg +0 -0
- {duet_cli-0.2.0 → duet_cli-0.2.1}/tests/test_duet.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: duet-cli
|
|
3
|
-
Version: 0.2.
|
|
3
|
+
Version: 0.2.1
|
|
4
4
|
Summary: Two CLI agents in conversation. One Python file. Stdlib only.
|
|
5
5
|
Author: Volkan Altan
|
|
6
6
|
License-Expression: MIT
|
|
@@ -56,7 +56,9 @@ codex plugin add duet@volkan-duet
|
|
|
56
56
|
```
|
|
57
57
|
|
|
58
58
|
Start a new Codex thread and invoke `$duet`, or just ask Codex to use duet in
|
|
59
|
-
plain language.
|
|
59
|
+
plain language. Like the Claude Code plugin, the skill shells out to the `duet`
|
|
60
|
+
CLI, so install that first (see below) and make sure `command -v duet` passes in
|
|
61
|
+
Codex's shell. Full guide:
|
|
60
62
|
[docs/CODEX_PLUGIN.md](https://github.com/volkan/duet/blob/main/docs/CODEX_PLUGIN.md).
|
|
61
63
|
|
|
62
64
|
### 3. From the terminal — `duet`
|
|
@@ -69,7 +71,9 @@ duet --task "Fix the failing test" --cwd ~/code/myrepo
|
|
|
69
71
|
The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library),
|
|
70
72
|
so `pipx`/`uvx` isolation is recommended. Add `'duet-cli[yaml]'` if you want
|
|
71
73
|
`--config foo.yaml`. One-shot, no install:
|
|
72
|
-
`uvx --from duet-cli duet --task "..."
|
|
74
|
+
`uvx --from duet-cli duet --task "..."` — note this is ephemeral and does not put
|
|
75
|
+
`duet` on PATH, so the `/duet` and `$duet` plugins need a persistent install
|
|
76
|
+
(`pipx install duet-cli` or `make install`) instead.
|
|
73
77
|
|
|
74
78
|
## Examples
|
|
75
79
|
|
|
@@ -35,7 +35,9 @@ codex plugin add duet@volkan-duet
|
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
Start a new Codex thread and invoke `$duet`, or just ask Codex to use duet in
|
|
38
|
-
plain language.
|
|
38
|
+
plain language. Like the Claude Code plugin, the skill shells out to the `duet`
|
|
39
|
+
CLI, so install that first (see below) and make sure `command -v duet` passes in
|
|
40
|
+
Codex's shell. Full guide:
|
|
39
41
|
[docs/CODEX_PLUGIN.md](https://github.com/volkan/duet/blob/main/docs/CODEX_PLUGIN.md).
|
|
40
42
|
|
|
41
43
|
### 3. From the terminal — `duet`
|
|
@@ -48,7 +50,9 @@ duet --task "Fix the failing test" --cwd ~/code/myrepo
|
|
|
48
50
|
The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library),
|
|
49
51
|
so `pipx`/`uvx` isolation is recommended. Add `'duet-cli[yaml]'` if you want
|
|
50
52
|
`--config foo.yaml`. One-shot, no install:
|
|
51
|
-
`uvx --from duet-cli duet --task "..."
|
|
53
|
+
`uvx --from duet-cli duet --task "..."` — note this is ephemeral and does not put
|
|
54
|
+
`duet` on PATH, so the `/duet` and `$duet` plugins need a persistent install
|
|
55
|
+
(`pipx install duet-cli` or `make install`) instead.
|
|
52
56
|
|
|
53
57
|
## Examples
|
|
54
58
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: duet-cli
|
|
3
|
-
Version: 0.2.
|
|
3
|
+
Version: 0.2.1
|
|
4
4
|
Summary: Two CLI agents in conversation. One Python file. Stdlib only.
|
|
5
5
|
Author: Volkan Altan
|
|
6
6
|
License-Expression: MIT
|
|
@@ -56,7 +56,9 @@ codex plugin add duet@volkan-duet
|
|
|
56
56
|
```
|
|
57
57
|
|
|
58
58
|
Start a new Codex thread and invoke `$duet`, or just ask Codex to use duet in
|
|
59
|
-
plain language.
|
|
59
|
+
plain language. Like the Claude Code plugin, the skill shells out to the `duet`
|
|
60
|
+
CLI, so install that first (see below) and make sure `command -v duet` passes in
|
|
61
|
+
Codex's shell. Full guide:
|
|
60
62
|
[docs/CODEX_PLUGIN.md](https://github.com/volkan/duet/blob/main/docs/CODEX_PLUGIN.md).
|
|
61
63
|
|
|
62
64
|
### 3. From the terminal — `duet`
|
|
@@ -69,7 +71,9 @@ duet --task "Fix the failing test" --cwd ~/code/myrepo
|
|
|
69
71
|
The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library),
|
|
70
72
|
so `pipx`/`uvx` isolation is recommended. Add `'duet-cli[yaml]'` if you want
|
|
71
73
|
`--config foo.yaml`. One-shot, no install:
|
|
72
|
-
`uvx --from duet-cli duet --task "..."
|
|
74
|
+
`uvx --from duet-cli duet --task "..."` — note this is ephemeral and does not put
|
|
75
|
+
`duet` on PATH, so the `/duet` and `$duet` plugins need a persistent install
|
|
76
|
+
(`pipx install duet-cli` or `make install`) instead.
|
|
73
77
|
|
|
74
78
|
## Examples
|
|
75
79
|
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|