pythinker-code 0.44.0__tar.gz → 0.45.0__tar.gz

{pythinker_code-0.44.0 → pythinker_code-0.45.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythinker-code
-Version: 0.44.0
+Version: 0.45.0
 Summary: Pythinker — an agentic CLI developed by Pythoughts-labs.
 Keywords: cli,agent,ai,coding-assistant,llm,claude,openai,terminal
 Author: Pythoughts-labs
@@ -115,13 +115,14 @@ It speaks the [**Agent Client Protocol (ACP)**](https://github.com/agentclientpr
 
 ---
 
-## 🆕 What's New in 0.44.0
+## 🆕 What's New in 0.45.0
 
-- **Toggle auto-update from the CLI.** `/update` now opens a menu — *Check for updates now* (the default, so a bare `/update` still checks immediately) or *Auto-update on startup* with its current state. `/update auto on|off` sets it directly, the same toggle appears in `/settings`, and `pythinker info` reports the status. Every surface shows the *effective* state, so an external override (`PYTHINKER_CLI_NO_AUTO_UPDATE` or a source checkout) is surfaced as the reason instead of silently no-opping.
-- **No more spurious "could not close the program" error on Windows updates.** The native installer now waits for the launching `pythinker.exe` to fully exit (its PID is passed via `/PID`) before its Restart Manager scan runs, so the scan no longer races the launcher's teardown into a false "close the program and retry" dialog. The update already succeeded in that case; now it completes cleanly.
-- **Simpler Windows update path.** With every shipped Windows install updating through the native installer, the Windows-only detached-spawn upgrade helper is gone; the remaining pip/uv/pipx path runs the upgrade inline and surfaces real command output and errors instead of a fire-and-forget process.
+- **Agent-tracing dashboard.** `pythinker dashboard` opens a local web UI for inspecting sessions, wire events, context messages, tool statistics, and usage over time — also reachable from the shell via `/reports` or `/dashboard`.
+- **Project instructions immune to compaction.** `AGENTS.md` is now delivered as a fresh `<system-reminder>` on every request instead of being baked into the system prompt, so compaction can never summarize it away and the token budget can never truncate it. `pythinker system-prompt` shows the assembled prompt with the reminder below a labeled divider.
+- **Accept-edits mode.** `/accept-edits` auto-approves reversible in-workspace file edits while still prompting for shell, destructive, config, and sensitive host-file writes (`.git/hooks`, `.zshrc`, `.ssh`, etc.) — never swept into the auto-approve tier.
+- **Recover from output-token truncation.** When a turn is cut off by the output-token limit, the model is nudged to continue from where it stopped (up to `loop_control.max_truncation_recoveries` times, default 3) instead of treating a half-finished answer as complete.
 
-Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.44.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
+Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.45.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
 
 
 ---
@@ -211,7 +212,7 @@ matches your OS — no Python, Node, or `uv` prerequisite.
 
 | Platform | Recommended install | Artifact source |
 |---|---|---|
-| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.44.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
+| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.45.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> / <img src="https://img.shields.io/badge/-Linux-FCC624?style=flat-square&logo=linux&logoColor=black" alt="Linux">** | `curl -fsSL https://pythinker.com/install.sh \| bash` | native tarball from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> — Homebrew** | `brew install Pythoughts-labs/pythinker/pythinker-code` | auto-published Homebrew tap |
 | **🐳 Docker** | `docker run --rm -it ghcr.io/pythoughts-labs/pythinker-code` | GHCR multi-arch image |
@@ -239,7 +240,7 @@ pythinker                      # start the interactive TUI
 
 ### 🪟 Windows — native installer
 
-`PythinkerSetup-0.44.0.exe` is a signed* Inno Setup wizard. Installs per-user
+`PythinkerSetup-0.45.0.exe` is a signed* Inno Setup wizard. Installs per-user
 into `%LOCALAPPDATA%\Programs\Pythinker`, registers `pythinker` on your user
 PATH (`HKCU\Environment`), broadcasts `WM_SETTINGCHANGE` so new shells see
 the change. **No UAC prompt.**
@@ -250,13 +251,13 @@ irm https://pythinker.com/install.ps1 | iex
 
 # Or manually download the installer + checksum from the Releases page,
 # verify with Get-FileHash, then run:
-.\PythinkerSetup-0.44.0.exe
+.\PythinkerSetup-0.45.0.exe
 
 # Open a fresh PowerShell
 pythinker --version
 ```
 
-**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.44.0.exe /ALLUSERS`
+**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.45.0.exe /ALLUSERS`
 installs to `%ProgramFiles%\Pythinker` and writes PATH to HKLM (requires admin).
 
 **Upgrade:** `pythinker update` from inside the running app — it downloads
@@ -314,26 +315,26 @@ attached to every GitHub Release.
 
 ```sh
 # Debian / Ubuntu (x86_64)
-sudo dpkg -i pythinker-code_0.44.0_amd64.deb
+sudo dpkg -i pythinker-code_0.45.0_amd64.deb
 sudo apt-get install -f       # only if dpkg reports missing deps
 
 # Debian / Ubuntu (ARM64)
-sudo dpkg -i pythinker-code_0.44.0_arm64.deb
+sudo dpkg -i pythinker-code_0.45.0_arm64.deb
 
 # Fedora / RHEL / openSUSE (x86_64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.x86_64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.x86_64.rpm.sha256
-sha256sum -c pythinker-code-0.44.0.x86_64.rpm.sha256
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.x86_64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.x86_64.rpm.sha256
+sha256sum -c pythinker-code-0.45.0.x86_64.rpm.sha256
 # Fedora / RHEL:
-sudo dnf install ./pythinker-code-0.44.0.x86_64.rpm
+sudo dnf install ./pythinker-code-0.45.0.x86_64.rpm
 # openSUSE:
-sudo zypper install ./pythinker-code-0.44.0.x86_64.rpm
+sudo zypper install ./pythinker-code-0.45.0.x86_64.rpm
 
 # Fedora / RHEL (aarch64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.aarch64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.aarch64.rpm.sha256
-sha256sum -c pythinker-code-0.44.0.aarch64.rpm.sha256
-sudo dnf install ./pythinker-code-0.44.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.aarch64.rpm.sha256
+sha256sum -c pythinker-code-0.45.0.aarch64.rpm.sha256
+sudo dnf install ./pythinker-code-0.45.0.aarch64.rpm
 ```
 
 Both packages drop a small `/usr/bin/pythinker` launcher that execs the real
@@ -342,8 +343,8 @@ binary under `/usr/lib/pythinker/`, so your `$PATH` stays tidy.
 **Verify before install:**
 
 ```sh
-sha256sum -c pythinker-code_0.44.0_amd64.deb.sha256        # Debian/Ubuntu
-sha256sum -c pythinker-code-0.44.0.x86_64.rpm.sha256       # Fedora/RHEL
+sha256sum -c pythinker-code_0.45.0_amd64.deb.sha256        # Debian/Ubuntu
+sha256sum -c pythinker-code-0.45.0.x86_64.rpm.sha256       # Fedora/RHEL
 ```
 
 **Upgrade:** download the new `.deb`/`.rpm` from Releases and `dpkg -i` /
@@ -809,8 +810,8 @@ make test-pythinker-sdk   # SDK only
 ```sh
 make web-back             # web backend
 make web-front            # web frontend
-make vis-back             # vis backend
-make vis-front            # vis frontend
+make dashboard-back       # dashboard backend
+make dashboard-front      # dashboard frontend
 ```
 
 </td>
@@ -835,7 +836,7 @@ make help                 # all targets
 
 ```
 pythinker-code/
-├── 📦 src/pythinker_code/         CLI runtime · tools · UIs · ACP · MCP · hooks · plugins · skills · web · vis backends
+├── 📦 src/pythinker_code/         CLI runtime · tools · UIs · ACP · MCP · hooks · plugins · skills · web · dashboard backends
 ├── 🧱 packages/
 │   ├── pythinker-core/           Provider-agnostic message, tool, and chat-provider abstractions
 │   ├── pythinker-host/           Local/remote host filesystem and command execution

{pythinker_code-0.44.0 → pythinker_code-0.45.0}/README.md

@@ -50,13 +50,14 @@ It speaks the [**Agent Client Protocol (ACP)**](https://github.com/agentclientpr
 
 ---
 
-## 🆕 What's New in 0.44.0
+## 🆕 What's New in 0.45.0
 
-- **Toggle auto-update from the CLI.** `/update` now opens a menu — *Check for updates now* (the default, so a bare `/update` still checks immediately) or *Auto-update on startup* with its current state. `/update auto on|off` sets it directly, the same toggle appears in `/settings`, and `pythinker info` reports the status. Every surface shows the *effective* state, so an external override (`PYTHINKER_CLI_NO_AUTO_UPDATE` or a source checkout) is surfaced as the reason instead of silently no-opping.
-- **No more spurious "could not close the program" error on Windows updates.** The native installer now waits for the launching `pythinker.exe` to fully exit (its PID is passed via `/PID`) before its Restart Manager scan runs, so the scan no longer races the launcher's teardown into a false "close the program and retry" dialog. The update already succeeded in that case; now it completes cleanly.
-- **Simpler Windows update path.** With every shipped Windows install updating through the native installer, the Windows-only detached-spawn upgrade helper is gone; the remaining pip/uv/pipx path runs the upgrade inline and surfaces real command output and errors instead of a fire-and-forget process.
+- **Agent-tracing dashboard.** `pythinker dashboard` opens a local web UI for inspecting sessions, wire events, context messages, tool statistics, and usage over time — also reachable from the shell via `/reports` or `/dashboard`.
+- **Project instructions immune to compaction.** `AGENTS.md` is now delivered as a fresh `<system-reminder>` on every request instead of being baked into the system prompt, so compaction can never summarize it away and the token budget can never truncate it. `pythinker system-prompt` shows the assembled prompt with the reminder below a labeled divider.
+- **Accept-edits mode.** `/accept-edits` auto-approves reversible in-workspace file edits while still prompting for shell, destructive, config, and sensitive host-file writes (`.git/hooks`, `.zshrc`, `.ssh`, etc.) — never swept into the auto-approve tier.
+- **Recover from output-token truncation.** When a turn is cut off by the output-token limit, the model is nudged to continue from where it stopped (up to `loop_control.max_truncation_recoveries` times, default 3) instead of treating a half-finished answer as complete.
 
-Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.44.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
+Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.45.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
 
 
 ---
@@ -146,7 +147,7 @@ matches your OS — no Python, Node, or `uv` prerequisite.
 
 | Platform | Recommended install | Artifact source |
 |---|---|---|
-| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.44.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
+| **🪟 Windows** | `irm https://pythinker.com/install.ps1 \| iex` | `PythinkerSetup-0.45.0.exe` from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> / <img src="https://img.shields.io/badge/-Linux-FCC624?style=flat-square&logo=linux&logoColor=black" alt="Linux">** | `curl -fsSL https://pythinker.com/install.sh \| bash` | native tarball from [Releases](https://github.com/Pythoughts-labs/pythinker-code/releases/latest) |
 | **<img src="https://img.shields.io/badge/-macOS-000000?style=flat-square&logo=apple&logoColor=white" alt="macOS"> — Homebrew** | `brew install Pythoughts-labs/pythinker/pythinker-code` | auto-published Homebrew tap |
 | **🐳 Docker** | `docker run --rm -it ghcr.io/pythoughts-labs/pythinker-code` | GHCR multi-arch image |
@@ -174,7 +175,7 @@ pythinker                      # start the interactive TUI
 
 ### 🪟 Windows — native installer
 
-`PythinkerSetup-0.44.0.exe` is a signed* Inno Setup wizard. Installs per-user
+`PythinkerSetup-0.45.0.exe` is a signed* Inno Setup wizard. Installs per-user
 into `%LOCALAPPDATA%\Programs\Pythinker`, registers `pythinker` on your user
 PATH (`HKCU\Environment`), broadcasts `WM_SETTINGCHANGE` so new shells see
 the change. **No UAC prompt.**
@@ -185,13 +186,13 @@ irm https://pythinker.com/install.ps1 | iex
 
 # Or manually download the installer + checksum from the Releases page,
 # verify with Get-FileHash, then run:
-.\PythinkerSetup-0.44.0.exe
+.\PythinkerSetup-0.45.0.exe
 
 # Open a fresh PowerShell
 pythinker --version
 ```
 
-**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.44.0.exe /ALLUSERS`
+**Per-machine install** (IT-managed boxes): `.\PythinkerSetup-0.45.0.exe /ALLUSERS`
 installs to `%ProgramFiles%\Pythinker` and writes PATH to HKLM (requires admin).
 
 **Upgrade:** `pythinker update` from inside the running app — it downloads
@@ -249,26 +250,26 @@ attached to every GitHub Release.
 
 ```sh
 # Debian / Ubuntu (x86_64)
-sudo dpkg -i pythinker-code_0.44.0_amd64.deb
+sudo dpkg -i pythinker-code_0.45.0_amd64.deb
 sudo apt-get install -f       # only if dpkg reports missing deps
 
 # Debian / Ubuntu (ARM64)
-sudo dpkg -i pythinker-code_0.44.0_arm64.deb
+sudo dpkg -i pythinker-code_0.45.0_arm64.deb
 
 # Fedora / RHEL / openSUSE (x86_64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.x86_64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.x86_64.rpm.sha256
-sha256sum -c pythinker-code-0.44.0.x86_64.rpm.sha256
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.x86_64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.x86_64.rpm.sha256
+sha256sum -c pythinker-code-0.45.0.x86_64.rpm.sha256
 # Fedora / RHEL:
-sudo dnf install ./pythinker-code-0.44.0.x86_64.rpm
+sudo dnf install ./pythinker-code-0.45.0.x86_64.rpm
 # openSUSE:
-sudo zypper install ./pythinker-code-0.44.0.x86_64.rpm
+sudo zypper install ./pythinker-code-0.45.0.x86_64.rpm
 
 # Fedora / RHEL (aarch64)
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.aarch64.rpm
-curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.44.0/pythinker-code-0.44.0.aarch64.rpm.sha256
-sha256sum -c pythinker-code-0.44.0.aarch64.rpm.sha256
-sudo dnf install ./pythinker-code-0.44.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.aarch64.rpm
+curl -LO https://github.com/Pythoughts-labs/pythinker-code/releases/download/v0.45.0/pythinker-code-0.45.0.aarch64.rpm.sha256
+sha256sum -c pythinker-code-0.45.0.aarch64.rpm.sha256
+sudo dnf install ./pythinker-code-0.45.0.aarch64.rpm
 ```
 
 Both packages drop a small `/usr/bin/pythinker` launcher that execs the real
@@ -277,8 +278,8 @@ binary under `/usr/lib/pythinker/`, so your `$PATH` stays tidy.
 **Verify before install:**
 
 ```sh
-sha256sum -c pythinker-code_0.44.0_amd64.deb.sha256        # Debian/Ubuntu
-sha256sum -c pythinker-code-0.44.0.x86_64.rpm.sha256       # Fedora/RHEL
+sha256sum -c pythinker-code_0.45.0_amd64.deb.sha256        # Debian/Ubuntu
+sha256sum -c pythinker-code-0.45.0.x86_64.rpm.sha256       # Fedora/RHEL
 ```
 
 **Upgrade:** download the new `.deb`/`.rpm` from Releases and `dpkg -i` /
@@ -744,8 +745,8 @@ make test-pythinker-sdk   # SDK only
 ```sh
 make web-back             # web backend
 make web-front            # web frontend
-make vis-back             # vis backend
-make vis-front            # vis frontend
+make dashboard-back       # dashboard backend
+make dashboard-front      # dashboard frontend
 ```
 
 </td>
@@ -770,7 +771,7 @@ make help                 # all targets
 
 ```
 pythinker-code/
-├── 📦 src/pythinker_code/         CLI runtime · tools · UIs · ACP · MCP · hooks · plugins · skills · web · vis backends
+├── 📦 src/pythinker_code/         CLI runtime · tools · UIs · ACP · MCP · hooks · plugins · skills · web · dashboard backends
 ├── 🧱 packages/
 │   ├── pythinker-core/           Provider-agnostic message, tool, and chat-provider abstractions
 │   ├── pythinker-host/           Local/remote host filesystem and command execution

{pythinker_code-0.44.0 → pythinker_code-0.45.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "pythinker-code"
-version = "0.44.0"
+version = "0.45.0"
 description = "Pythinker — an agentic CLI developed by Pythoughts-labs."
 readme = "README.md"
 requires-python = ">=3.12"

{pythinker_code-0.44.0 → pythinker_code-0.45.0}/src/pythinker_code/CHANGELOG.md

@@ -15,6 +15,95 @@ GitHub Releases page; `0.8.0` is the new starting line.
 
 ## Unreleased
 
+## 0.45.0 (2026-06-14)
+
+- **Agent-tracing dashboard.** Added `pythinker dashboard` — a local web UI for inspecting sessions, wire events, context messages, tool statistics, and usage over time. It is also reachable from the interactive shell via the `/reports` slash command (aliased `/dashboard`).
+- **Gemini finish_reason is now sticky once truncation is detected.** A second candidate with any non-`MAX_TOKENS` finish reason no longer overwrites a previously captured `"length"` signal at either the streaming or non-streaming path in the Google GenAI provider.
+- **Budget-exhausted and stuck-loop messages are now visible in the shell.** Both handoff messages were appended to context but never sent to the wire, so the interactive shell showed no feedback when a spend ceiling or stuck-loop exit fired. Both now emit a `TextPart` wire event so the message appears in the shell.
+- **Dark-theme prompt_toolkit border colors now match the TUI token constants.** Six stale slate hex values in `_PROMPT_STYLE_DARK` diverged from the current `border` and `border_muted` token values; they are now in sync and a parity test binds them going forward.
+- **Non-review successful agents now show a summary preview in the agent tree.** Completed subagents with a `summary_preview` now display a dim preview line in the RunAgents tree renderer (review runs continue to use the findings table instead).
+- **Non-string values in `required_mcp_servers` YAML are silently dropped.** Integers, booleans, and `null` entries were previously coerced to strings (`"1"`, `"False"`, `"None"`), creating permanently unsatisfiable MCP server names. Only actual string entries are now retained.
+- **Fixed MiniMax token-plan `/usage` accuracy.** The token-plan response now meters by
+  percentage (the count fields are 0) and reports reset times in milliseconds; the adapter was
+  reading the zero counts (showing "0 requests used") and treating milliseconds as seconds
+  (showing resets like "171d" for a 5-hour window). It now reads `*_remaining_percent` and
+  converts reset times correctly, so e.g. a week at 82% remaining shows "18% used" resetting in
+  hours, not days.
+- **GLM-5.2 (1M context) is now the default Z.AI model.** Logging in with Z.AI selects
+  `z-ai/glm-5.2` with its full 1,000,000-token context window. GLM-5.2 is absent from z.ai's
+  model-listing API, so it is pinned into the catalog and offered even when discovery omits it;
+  if z.ai later lists it, the API definition wins and it is shown once (no duplicate). Earlier
+  GLM models (5.1, 5, 5-turbo, 4.7, 4.5-air) remain available.
+- **Kimi K2.7 Code added, and a new Kimi Coding Plan provider.** `kimi-k2.7-code` is now the
+  default model on the Moonshot plan, and a separate "Kimi Coding Plan" provider
+  (`/login kimi`) targets Moonshot's Anthropic-compatible coding endpoint with `kimi-k2.7-code`.
+- **Verb spinner stays visible while a foreground tool or subagent runs.** The shimmering
+  "Working…/Thinking…" activity indicator now persists for the whole active turn — including
+  while a foreground tool (such as a shell-started server) or a subagent is executing — instead
+  of disappearing until the tool finished. This keeps long tool/subagent waits feeling alive
+  rather than frozen. An in-progress todo still swaps the verb for the todo title as before.
+- **Project instructions delivered as a separate authoritative message.** The merged
+  `AGENTS.md` is no longer baked into the system prompt; it is delivered as a session-start,
+  user-role `<system-reminder>` preamble, assembled fresh on every request from session
+  state. This keeps the project rules immune to two regressions a system-prompt move would
+  otherwise risk — context compaction can no longer summarize them away (they never enter the
+  persisted history) and the dynamic-injection token budget can no longer truncate them —
+  while keeping the system prompt free of per-project content. `pythinker system-prompt` shows
+  the reminder below a labeled divider so the dump stays faithful.
+- **Inspect the assembled system prompt.** New `pythinker system-prompt` command
+  renders and prints the fully-assembled system prompt for an agent
+  (`--agent <name>`, `--agent-file <path>`, `--work-dir <dir>`) — substituting the
+  live work directory, OS/shell, merged `AGENTS.md`, and discovered skills. It is
+  read-only: no session is created, no provider auth is required, and no MCP
+  servers are loaded.
+- **Bound parallel tool fan-out.** Parallel-safe tool calls in one turn still
+  overlap, but now up to a fixed concurrency cap (10) instead of without bound, so
+  a turn that fans out many readers (e.g. dozens of web fetches) can no longer open
+  an unbounded number of sockets/file handles at once. Mutating-tool ordering and
+  writer exclusivity are unchanged.
+- **Optional per-session spend ceiling.** New `loop_control.max_session_cost_usd`
+  config option (off by default). When set, a turn stops with a clear
+  budget-exhausted handoff message once the session's accumulated estimated cost
+  reaches the ceiling, instead of running to the step limit — and goal
+  auto-continuations and agent flows halt too. Best-effort: cost is `0` for models
+  with unknown pricing, so the ceiling never blocks when spend cannot be estimated.
+- **Sensitive host files always re-confirm.** Writes to shell startup files
+  (`.zshrc`, `.bash_profile`, …), `.git` internals/hooks, the custom `.githooks`
+  hooks directory, `.ssh`, `.vscode`, and git
+  credentials (`.gitconfig`, `.netrc`, `.git-credentials`) are now classified as a
+  distinct edit action that re-confirms every time — even under yolo/auto — and is
+  never recorded as session-approved, exactly like edits to pythinker's own config.
+  This closes an auto-approve gap where a `.git/hooks` write inside the workspace was
+  treated as an ordinary edit.
+- **Accept-edits mode.** New `/accept-edits` toggle auto-approves reversible
+  in-workspace ordinary file edits while still prompting for shell, destructive,
+  outside-workspace, config-surface, and sensitive host-file edits. It is
+  session-local (not persisted) and suppressed by safe mode. Pairs with the deny-set
+  above so a `.git/hooks` or shell-rc write is never swept into the auto-approve tier.
+- **Agents can declare required MCP servers.** A markdown agent's frontmatter may set
+  `required_mcp_servers: [..]`; spawning that agent (via `Agent` or `RunAgents`) is
+  rejected with a clear message when those servers are configured-and-absent, instead of
+  wasting a turn on an agent that cannot reach its tools. While MCP is still loading the
+  spawn is allowed (the servers may yet connect).
+- **UserPromptSubmit hooks can add context.** A non-blocking `UserPromptSubmit` hook's
+  `additionalContext` is now injected into the user turn as a system reminder, so the
+  model sees it as context for the prompt (previously only a hook *block* was honored).
+  Slash-command parsing still reads only the user's text, never the appended context.
+- **Stale-overwrite guard for file edits.** If you read a file and it then changes on
+  disk (edited by you in another window or by another tool), overwriting it with WriteFile
+  or editing it with StrReplaceFile is now rejected with "File has been modified since you
+  last read it" so external changes are not silently clobbered — read it again first. This
+  catches external edits that StrReplaceFile's exact-string matching alone would miss.
+  First-contact writes (a file you never read) are unaffected, and a tool's own write
+  refreshes the read-state so consecutive edits are never falsely flagged.
+- **Recover from output-token truncation.** When a response is cut off by the
+  output-token limit and makes no tool call, the turn no longer ends with a half-finished
+  answer treated as complete — the model is nudged to continue from where it stopped, up
+  to `loop_control.max_truncation_recoveries` times per turn (default 3; `0` disables).
+  pythinker-core now surfaces the provider's truncation signal so the loop can detect it.
+
+Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.45.0`, or use the native installer for your platform from the [Releases page](https://github.com/Pythoughts-labs/pythinker-code/releases/latest).
+
 ## 0.44.0 (2026-06-13)
 
 - **Toggle auto-update from the CLI.** Running `/update` now opens a menu — *Check for updates now* (the default, so a bare `/update` + Enter still checks immediately) or *Auto-update on startup* with its current state — so the toggle is discoverable without knowing a subcommand. `/update auto on|off` still sets it directly, and `/update auto` with no value opens an interactive On/Off picker (cursor defaulted to the current setting). The same toggle appears in the interactive `/settings` panel, and `pythinker info` reports the auto-update status. All surfaces show the *effective* state — an external override (`PYTHINKER_CLI_NO_AUTO_UPDATE` or a source checkout) is surfaced as the reason, renders the `/settings` row read-only, and makes `/update auto` report the read-only state rather than popping a no-op picker, so the toggle is never a silent no-op.

{pythinker_code-0.44.0 → pythinker_code-0.45.0}/src/pythinker_code/agents/default/system.md

@@ -242,19 +242,8 @@ ${PYTHINKER_ADDITIONAL_DIRS_INFO}
 ## 11. Project Instructions (AGENTS.md)
 
 `AGENTS.md` files carry the agent-facing context a README omits — build steps, test commands, conventions, structure, and user preferences — kept separate so agents have a predictable place for instructions while READMEs stay human-focused.
-{% if PYTHINKER_AGENTS_MD %}
 
-The block below is authoritative and already merged: every `AGENTS.md` from the project root down to the working directory, deeper (more specific) files overriding shallower ones, each governing its own directory and everything beneath it.
-
-${PYTHINKER_AGENTS_MD_FENCE}
-${PYTHINKER_AGENTS_MD}
-${PYTHINKER_AGENTS_MD_FENCE}
-
-Treat the merged block as complete for the root-to-working-directory range; look for additional `AGENTS.md` only in directories **below** the working directory and apply them by the same precedence when editing there.
-{% else %}
-
-No `AGENTS.md` files were found between the project root and the working directory; look for them only in directories **below** the working directory and apply them when editing there.
-{% endif %}
+When any `AGENTS.md` files apply between the project root and the working directory, their merged content is **delivered as a separate authoritative message at the start of this session** — every file from the project root down to the working directory, deeper (more specific) files overriding shallower ones, each governing its own directory and everything beneath it. Treat that merged message as complete for the root-to-working-directory range, with the same authority as these instructions; look for additional `AGENTS.md` only in directories **below the working directory** and apply them by the same precedence when editing there.
 
 Precedence per §2. `README`/`README.md` files are optional supplementary context, not instructions. If a change you make invalidates anything an `AGENTS.md` documents (build/test commands, conventions, structure, workflows), update that `AGENTS.md` in the same change so it stays trustworthy.
 

{pythinker_code-0.44.0 → pythinker_code-0.45.0}/src/pythinker_code/auth/__init__.py

@@ -7,6 +7,7 @@ OPENAI_CHATGPT_PLATFORM_ID = "openai-chatgpt"
 OPENCODE_GO_PLATFORM_ID = "opencode-go"
 MINIMAX_PLATFORM_ID = "minimax"
 MOONSHOT_PLATFORM_ID = "moonshot"
+KIMI_PLATFORM_ID = "kimi"
 DEEPSEEK_PLATFORM_ID = "deepseek"
 ANTHROPIC_PLATFORM_ID = "anthropic"
 OPENROUTER_PLATFORM_ID = "openrouter"
@@ -18,6 +19,7 @@ __all__ = [
     "ALIBABA_PLATFORM_ID",
     "ANTHROPIC_PLATFORM_ID",
     "DEEPSEEK_PLATFORM_ID",
+    "KIMI_PLATFORM_ID",
     "LM_STUDIO_PLATFORM_ID",
     "MINIMAX_PLATFORM_ID",
     "MOONSHOT_PLATFORM_ID",