deepsieve-cli 0.3.0__tar.gz → 0.5.0__tar.gz

{deepsieve_cli-0.3.0 → deepsieve_cli-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: deepsieve-cli
-Version: 0.3.0
+Version: 0.5.0
 Summary: DeepSieve CLI — run cited deep research from your terminal
 Requires-Python: >=3.11
 Requires-Dist: httpx>=0.27
@@ -20,19 +20,31 @@ scoped API key. Nothing to copy, nothing pasted into your shell history. The
 credential appears in **Settings → API keys** on your deployment and can be
 revoked there at any time.
 
+The key covers the CLI's own commands and cannot create a Blueprint. If an agent
+will use it to create Blueprints, run `deepsieve login --preset agent`; the
+approval screen lists the extra scopes.
+
 ## Commands
 
 ```bash
-deepsieve whoami                              # identity, workspace, scopes
+deepsieve whoami                              # identity, organization, active Blueprint, scopes
 deepsieve runs create --query "..." --dry-run # free simulated run (~15s)
-deepsieve runs create --query "..." --wait    # real run: spends credits
-deepsieve runs create --seeds "..." --allowed-source "*.gov"  # only cite these
+deepsieve runs create --blueprint <id> --query "..." --wait  # real run: spends credits
+deepsieve runs create --blueprint <id> --seeds "..." --allowed-source "*.gov"  # only cite these
 deepsieve runs list
 deepsieve runs get <id>                       # exit 4 while still running
 deepsieve runs cancel <id>
-deepsieve members list                        # who is in the workspace + seat usage
+deepsieve members list                        # who is in the organization + seat usage
+deepsieve changes list --live                 # merges, renames, successor links
+deepsieve changes undo <id>                   # asks first; --yes in scripts
+deepsieve merge preview <entity> --survivor <id> --loser <id>   # writes nothing
+deepsieve merge apply <entity> --survivor <id> --loser <id> [--choice KEY=loser]
 deepsieve data catalog                        # entities + columns (never guess)
 deepsieve data get companies --receipts       # rows with per-cell citations
+deepsieve chat thread <run-id>                # changes, with status + warnings
+deepsieve chat confirm <action-id>            # apply a change that waits for confirmation
+deepsieve chat dismiss <action-id>            # decline it; nothing is written
+deepsieve chat revert <action-id>             # undo a change a chat answer applied
 deepsieve setup mcp                           # MCP registration for this origin
 ```
 

{deepsieve_cli-0.3.0 → deepsieve_cli-0.5.0}/README.md

@@ -12,19 +12,31 @@ scoped API key. Nothing to copy, nothing pasted into your shell history. The
 credential appears in **Settings → API keys** on your deployment and can be
 revoked there at any time.
 
+The key covers the CLI's own commands and cannot create a Blueprint. If an agent
+will use it to create Blueprints, run `deepsieve login --preset agent`; the
+approval screen lists the extra scopes.
+
 ## Commands
 
 ```bash
-deepsieve whoami                              # identity, workspace, scopes
+deepsieve whoami                              # identity, organization, active Blueprint, scopes
 deepsieve runs create --query "..." --dry-run # free simulated run (~15s)
-deepsieve runs create --query "..." --wait    # real run: spends credits
-deepsieve runs create --seeds "..." --allowed-source "*.gov"  # only cite these
+deepsieve runs create --blueprint <id> --query "..." --wait  # real run: spends credits
+deepsieve runs create --blueprint <id> --seeds "..." --allowed-source "*.gov"  # only cite these
 deepsieve runs list
 deepsieve runs get <id>                       # exit 4 while still running
 deepsieve runs cancel <id>
-deepsieve members list                        # who is in the workspace + seat usage
+deepsieve members list                        # who is in the organization + seat usage
+deepsieve changes list --live                 # merges, renames, successor links
+deepsieve changes undo <id>                   # asks first; --yes in scripts
+deepsieve merge preview <entity> --survivor <id> --loser <id>   # writes nothing
+deepsieve merge apply <entity> --survivor <id> --loser <id> [--choice KEY=loser]
 deepsieve data catalog                        # entities + columns (never guess)
 deepsieve data get companies --receipts       # rows with per-cell citations
+deepsieve chat thread <run-id>                # changes, with status + warnings
+deepsieve chat confirm <action-id>            # apply a change that waits for confirmation
+deepsieve chat dismiss <action-id>            # decline it; nothing is written
+deepsieve chat revert <action-id>             # undo a change a chat answer applied
 deepsieve setup mcp                           # MCP registration for this origin
 ```
 

{deepsieve_cli-0.3.0 → deepsieve_cli-0.5.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "deepsieve-cli"
-version = "0.3.0"
+version = "0.5.0"
 description = "DeepSieve CLI — run cited deep research from your terminal"
 requires-python = ">=3.11"
 readme = "README.md"

{deepsieve_cli-0.3.0 → deepsieve_cli-0.5.0}/src/deepsieve_cli/client.py

@@ -21,10 +21,19 @@ USER_AGENT = "deepsieve-cli"
 
 
 class ApiError(Exception):
-    def __init__(self, code: str, message: str, *, request_id: str | None = None) -> None:
+    def __init__(
+        self,
+        code: str,
+        message: str,
+        *,
+        request_id: str | None = None,
+        details: dict | None = None,
+    ) -> None:
         self.code = code
         self.message = message
         self.request_id = request_id
+        #: Structured facts from the error envelope (`locked_until`), when the API sent them.
+        self.details = details or {}
         super().__init__(message)
 
     def __str__(self) -> str:
@@ -87,6 +96,7 @@ class Client:
                 err.get("code", f"http_{r.status_code}"),
                 err.get("message", f"HTTP {r.status_code} from {path}"),
                 request_id=err.get("request_id"),
+                details=err.get("details"),
             )
         return body