dscli-agent 0.1.0__tar.gz → 0.2.0__tar.gz

{dscli_agent-0.1.0/dscli_agent.egg-info → dscli_agent-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dscli-agent
-Version: 0.1.0
+Version: 0.2.0
 Summary: A local coding agent that uses the DeepSeek web chat UI as its model
 Author: Anish
 License-Expression: MIT
@@ -103,12 +103,20 @@ Start dscli without a task to open an ongoing conversation:
 dscli
 ```
 
-dscli shows an inline terminal UI inspired by Claude Code: an animated spinner with
-rotating status verbs, a smoothly revealed streaming answer, compact tool cards
-(`⏺ Read(...)`, `⏺ Update(...)`, `⏺ Run(...)`), colored diffs for approvals, and the
-final answer rendered as Markdown. Output stays in normal scrollback; dscli does not
-take over the full screen, and startup shows only `Starting agent` instead of browser
-or session internals.
+dscli shows an inline terminal UI inspired by Claude Code: a cleared screen and gradient
+ASCII wordmark on launch, an animated spinner with rotating status verbs, a smoothly
+revealed streaming answer, compact tool cards (`⏺ Read(...)`, `⏺ Update(...)`,
+`⏺ Run(...)`), colored diffs for approvals, and the final answer rendered as Markdown.
+Output stays in normal scrollback after startup; dscli does not take over the full
+screen, and the welcome card shows the workspace, active modes, and shortcuts. Plans
+render as a compact checklist, and a configured verification command appears as a
+`Verify` card after file edits. `dscli chat --verify CMD` applies the check to each
+message.
+
+On launch, the visible terminal is cleared before the wordmark appears. Pass
+`--no-clear` to `chat`, or set `DSCLI_NO_CLEAR=1`, to keep the previous screen contents;
+the logo and welcome card still show. This behavior is TUI-only: `--plain`, non-TTY
+output, `run`, `doctor`, `login`, and `config` keep their existing output.
 
 The agent session stays open while you work at the `❯` prompt. The complete JSON
 envelope is still parsed and validated before any tool runs. File approvals,
@@ -177,6 +185,10 @@ The final answer is printed to stdout. Progress, diffs, and approval prompts go
 stderr, so `dscli run ... > result.txt` captures only the answer. `run` never uses the
 interactive UI; its output contract is unchanged.
 
+Exit codes: `0` success, `1` error, `2` model-turn budget exhausted, and `3`
+verification failed (takes precedence over `2`). Verification failures are always
+logged to stderr, including under `-q`.
+
 ### Common flags
 
 | Flag | Meaning |
@@ -190,7 +202,10 @@ interactive UI; its output contract is unchanged.
 | `--deepthink` / `--search` | Turn DeepSeek's modes on for the run. |
 | `--max-steps N` | Maximum model turns (default 12). |
 | `--timeout N` | Response timeout per turn in seconds (default 300). |
+| `--verify CMD` | Run CMD automatically after file edits; failures block success. |
+| `--no-verify` | Disable the configured `verify_command` for this run. |
 | `--prompt-file PATH` | Read the task from a UTF-8 file. |
+| `--no-clear` | Keep previous terminal output when the TUI starts (chat only). |
 | `--no-auto-login` | Do not open a visible browser if a headless login is needed. |
 | `-v, --verbose` | Show model thoughts and raw replies. |
 | `-q, --quiet` | Only print the final answer. |
@@ -223,6 +238,8 @@ dscli parses the envelope (also tolerating unfenced JSON and small formatting
 variations), runs the tool calls locally, and sends the results back in the next
 message inside nonce-tagged markers. The loop ends when the model replies with
 `tool_calls: []` and a non-empty `final` string, or when the turn budget is exhausted.
+Before a final is accepted, unfinished plan steps and the configured verification
+command can send the model back for more work (see below).
 
 Malformed replies get up to two correction prompts. Every raw reply that fails to parse
 is saved to the debug directory.
@@ -237,10 +254,37 @@ is saved to the debug directory.
 | `list_files` | Bounded recursive listing. |
 | `delete_file` | Delete one file when explicitly requested (approval required). |
 | `run_command` | Run a shell command (only with `--allow-shell`, approval required). |
+| `update_plan` | Create or revise the task plan; the final is deferred while steps are unfinished. |
 
 `apply_patch` normalises line endings for matching, preserves the file's encoding and
 line endings when writing, and refuses ambiguous matches unless `replace_all` is set.
 
+### Plan and verification loop
+
+The agent can maintain a short task plan with `update_plan` (at most 20 steps). While
+any step is `pending` or `in_progress`, dscli holds the final answer back and sends a
+bounded reminder (at most two) asking the model to finish or revise the plan. If the
+steps are still unfinished at the turn limit, the answer is accepted with a visible
+"plan incomplete" warning rather than deadlocking the run. Plans apply to a single
+message on chat and are reset for every new task.
+
+Configure a verification command with `--verify CMD` or the `verify_command` config
+key, for example:
+
+```powershell
+dscli run -y --verify "python -m pytest -q" "Add a test for the parser"
+```
+
+After a turn changes files, dscli runs the command itself, shows the result, and feeds
+failures back to the model for up to two repair attempts. If the check still fails, the
+run ends with the best available answer, marks verification as failed, and `dscli run`
+exits with code `3`. Verification only runs when the current message changed files.
+
+The verification command is supplied by you and is never a model-callable tool. It is
+run without `--allow-shell` and without a per-command approval prompt because you
+configured it explicitly. Treat it like any other command you run from the shell: the
+model can modify the files it checks, so review the final diff.
+
 ## Approvals and safety
 
 - Tools are confined to the workspace unless `--allow-outside` is passed.
@@ -248,6 +292,9 @@ line endings when writing, and refuses ambiguous matches unless `replace_all` is
 - Every write, patch, delete, and command shows a diff/command and asks
   `[y]es / [n]o / [a]ll / [q]uit` before changing anything. `-y` skips the prompts.
 - Shell access is off by default and can be enabled only for a run.
+- The verification command is the one exception to the approval flow: when you configure
+  it with `--verify` or `verify_command`, dscli runs it automatically after edits without
+  `--allow-shell` or a prompt. The model can neither call nor change it.
 - Attachment contents, file contents, command output, and tool results are treated as
   untrusted data by the system prompt.
 - No network access is performed by the tools; the only network traffic is the browser
@@ -274,7 +321,8 @@ session import), `chrome_profile` (empty = Chrome's last-used profile, or a name
 installed browser), `response_timeout_sec`, `first_response_timeout_sec`,
 `stable_seconds`, `fallback_stable_seconds`, `max_steps`, `max_tool_calls`,
 `max_read_chars`, `max_attachment_mb`, `deepthink`, `search`, `allow_shell`,
-`allow_outside`.
+`allow_outside`, `verify_command` (empty disables verification),
+`verify_timeout_sec` (clamped to 1–600, default 300).
 
 Headless Chrome normally sends a `HeadlessChrome/...` user agent, which DeepSeek's CDN
 rejects with a CloudFront 403. dscli automatically replaces it with the installed