deepsieve-cli 0.9.0__tar.gz → 0.10.0__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.
Files changed (12) hide show
  1. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/PKG-INFO +11 -4
  2. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/README.md +10 -3
  3. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/pyproject.toml +1 -1
  4. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/src/deepsieve_cli/main.py +661 -4
  5. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/tests/test_cli.py +26 -2
  6. deepsieve_cli-0.10.0/tests/test_cli_knowledge.py +750 -0
  7. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/.gitignore +0 -0
  8. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/src/deepsieve_cli/__init__.py +0 -0
  9. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/src/deepsieve_cli/__main__.py +0 -0
  10. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/src/deepsieve_cli/client.py +0 -0
  11. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/src/deepsieve_cli/config.py +0 -0
  12. {deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/tests/fixtures/conflict_page.json +0 -0
{deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: deepsieve-cli
3
- Version: 0.9.0
3
+ Version: 0.10.0
4
4
  Summary: DeepSieve CLI — run cited deep research from your terminal
5
5
  Requires-Python: >=3.11
6
6
  Requires-Dist: httpx>=0.27
@@ -53,6 +53,13 @@ deepsieve chat thread <run-id> # changes, with status + warnings
53
53
  deepsieve chat confirm <action-id> # apply a change that waits for confirmation
54
54
  deepsieve chat dismiss <action-id> # decline it; nothing is written
55
55
  deepsieve chat revert <action-id> # undo a change a chat answer applied
56
+ deepsieve knowledge list # what your team told DeepSieve about the field
57
+ deepsieve knowledge add --kind source_caution --statement "Lags a quarter." --host crunchbase.com
58
+ deepsieve knowledge edit <id> --statement "..." --revision 2 # a newer edit is refused
59
+ deepsieve knowledge retire <id> # stop using it; restore brings it back
60
+ deepsieve knowledge delete <id> # asks first; retire keeps it
61
+ deepsieve knowledge list --draft <session-id> # a draft's notes; any knowledge command takes --draft
62
+ deepsieve runs knowledge <run-id> # what your knowledge did in a run
56
63
  deepsieve setup mcp # MCP registration for this origin
57
64
  ```
58
65
 
@@ -80,7 +87,7 @@ DEEPSIEVE_API_KEY=ds_live_... deepsieve --json data get companies
80
87
  ## What it deliberately cannot do
81
88
 
82
89
  No billing, no organization or member management, no API-key management, and it
83
- cannot edit an active Blueprint. Those are decisions for a human in the app —
90
+ cannot edit an active Blueprint's schema. Those are decisions for a human in the app —
84
91
  and the restriction is enforced server-side by the credential's scopes, not just
85
92
  by the absence of a subcommand.
86
93
 
@@ -93,8 +100,8 @@ non-interactive shell unless you pass `--yes`.
93
100
  |---|---|
94
101
  | 0 | success |
95
102
  | 1 | failure |
96
- | 2 | usage error |
97
- | 3 | not authenticated |
103
+ | 2 | usage error, including a knowledge write that conflicts or edits an old revision |
104
+ | 3 | not authenticated, or a sign-in that cannot write knowledge yet (`deepsieve login` again) |
98
105
  | 4 | run still in progress |
99
106
 
100
107
  Full docs: <https://deepsieve.ai/developers/cli>
{deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/README.md RENAMED
@@ -45,6 +45,13 @@ deepsieve chat thread <run-id> # changes, with status + warnings
45
45
  deepsieve chat confirm <action-id> # apply a change that waits for confirmation
46
46
  deepsieve chat dismiss <action-id> # decline it; nothing is written
47
47
  deepsieve chat revert <action-id> # undo a change a chat answer applied
48
+ deepsieve knowledge list # what your team told DeepSieve about the field
49
+ deepsieve knowledge add --kind source_caution --statement "Lags a quarter." --host crunchbase.com
50
+ deepsieve knowledge edit <id> --statement "..." --revision 2 # a newer edit is refused
51
+ deepsieve knowledge retire <id> # stop using it; restore brings it back
52
+ deepsieve knowledge delete <id> # asks first; retire keeps it
53
+ deepsieve knowledge list --draft <session-id> # a draft's notes; any knowledge command takes --draft
54
+ deepsieve runs knowledge <run-id> # what your knowledge did in a run
48
55
  deepsieve setup mcp # MCP registration for this origin
49
56
  ```
50
57
 
@@ -72,7 +79,7 @@ DEEPSIEVE_API_KEY=ds_live_... deepsieve --json data get companies
72
79
  ## What it deliberately cannot do
73
80
 
74
81
  No billing, no organization or member management, no API-key management, and it
75
- cannot edit an active Blueprint. Those are decisions for a human in the app —
82
+ cannot edit an active Blueprint's schema. Those are decisions for a human in the app —
76
83
  and the restriction is enforced server-side by the credential's scopes, not just
77
84
  by the absence of a subcommand.
78
85
 
@@ -85,8 +92,8 @@ non-interactive shell unless you pass `--yes`.
85
92
  |---|---|
86
93
  | 0 | success |
87
94
  | 1 | failure |
88
- | 2 | usage error |
89
- | 3 | not authenticated |
95
+ | 2 | usage error, including a knowledge write that conflicts or edits an old revision |
96
+ | 3 | not authenticated, or a sign-in that cannot write knowledge yet (`deepsieve login` again) |
90
97
  | 4 | run still in progress |
91
98
 
92
99
  Full docs: <https://deepsieve.ai/developers/cli>
{deepsieve_cli-0.9.0 → deepsieve_cli-0.10.0}/pyproject.toml RENAMED
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "deepsieve-cli"
3
- version = "0.9.0"
3
+ version = "0.10.0"
4
4
  description = "DeepSieve CLI — run cited deep research from your terminal"
5
5
  requires-python = ">=3.11"
6
6
  readme = "README.md"