kolega-code 0.47.0__tar.gz → 0.48.0__tar.gz

{kolega_code-0.47.0 → kolega_code-0.48.0}/CHANGELOG.md

@@ -6,6 +6,130 @@ This project uses GitHub Releases for detailed generated release notes. This fil
 
 ## Unreleased
 
+## 0.48.0 - 2026-11-06
+
+### Added
+
+- **Refuseless provider.** The built-in `refuseless` provider
+  (`REFUSELESS_API_KEY`, or a key saved in Settings) serves five routes —
+  GLM-5.3 Abliterated, GLM-5.3 Flash Abliterated, DeepSeek V4.1 Flash
+  Abliterated, DeepSeek V4.1 Flash Fast and MiniMax M3.1 Flash — with each
+  route's window, output limit, thinking-effort ladder and per-million pricing in
+  the shared catalog. Selecting it defaults to GLM-5.3 Abliterated; saving a key
+  alone does not change your provider or any existing defaults. Prepaid-credit
+  exhaustion surfaces as a billing error, including mid-answer, instead of a
+  silently truncated reply.
+- Gateway voice notes can transcribe through OpenAI (`gpt-transcribe`, reusing
+  your OpenAI key) as well as Groq, selectable under **Tools → Voice
+  transcription**.
+- Editor sessions over ACP accept image prompts, so a host can send screenshots
+  and diagrams with a message.
+- ACP sessions track durable usage accounting: a request's lifetime inference
+  survives cancellation, late usage evidence and resume, and costs resolve from
+  reported charges, overrides or bundled catalogue prices without network calls.
+
+### Changed
+
+- The install script now lives at `https://kolega.ai/code/install.sh`, which
+  always serves the current script from this repository:
+  `curl -fsSL https://kolega.ai/code/install.sh | sh`.
+- The managed Python eval kernel now always provisions CPython 3.14, independently
+  of the CLI's Python version, with numpy 2.5.4 and matplotlib 3.11.2. Runtime
+  upgrades use separate version/bundle directories, and failed builds leave
+  previous environments unchanged instead of falling back to an arbitrary host
+  interpreter. The first eval after upgrading may download the new runtime;
+  manually installed eval packages must be reinstalled, while configured
+  `eval_kernel_packages` migrate automatically. `eval_python_version` is
+  deprecated and ignored; `eval_python_path` remains an explicit unbundled override.
+- Automatic session titles no longer get reworded after every turn: the title
+  generator keeps the current title unless you move the session on to a
+  different task. The description still updates each turn.
+- Turns wait less on terminal and file tracking: ordinary terminal output is no
+  longer parsed character by character, a checkpoint records only the paths that
+  changed instead of every dirty path, and a large checkout's startup copies
+  finish in the background instead of holding up the first turn.
+- Startup imports fewer optional SDKs: Tavily, Firecrawl, Beautiful Soup and the
+  HTML extractor load only when a search or fetch needs them, and aiohttp only
+  when an aiohttp error is mapped.
+- Refreshed the OpenRouter and Ollama Cloud model catalogs.
+
+### Fixed
+
+- A title set with `/retitle <title>` is now pinned. The automatic refresh after
+  each turn no longer replaces it, and the pin is saved with the session.
+  `/retitle` with no title unpins it and generates a new title and description.
+- Project-memory tools now accept `file_path` as an alias for `path`, and reject
+  missing or unknown arguments with the tool's usage, instead of reporting an
+  opaque storage failure. Unexpected memory failures name the error type, and
+  the full error is kept in the local session log and diagnostics.
+- The installer and `kolega-code update` now ask uv for a supported Python
+  (3.11–3.14, or 3.11–3.12 on Intel Macs), downloading one when none is
+  installed. Before, uv picked its newest interpreter: on Python 3.15 several
+  dependencies have no wheels yet, so a fresh install failed building
+  tiktoken from source. Intel Macs no longer get 3.13 or 3.14, whose
+  onnxruntime wheels are missing or need macOS 13.
+- A reasoning stream that carries the reasoning tail and the first answer text in
+  the same delta no longer drops the start of the reply in the TUI; the stored
+  message was already complete.
+- The TUI no longer grows to tens of gigabytes in checkouts with many untracked
+  files: checkpoint baselines now live in an on-disk spool capped at 10 GiB per
+  session and paused when the volume has under 5 GiB free, files over 8 MB are
+  compared by signature instead of read, and restored copies are verified by
+  hash.
+- Saving settings repeatedly in one session no longer drops fields an earlier
+  save in that session had written.
+- An incomplete Responses stream (OpenAI and ChatGPT) no longer starts the tool
+  calls it reported before the response was validated, and the truncation is
+  reported as an error instead of a clean turn ending.
+- A goal loop now pauses after a failed turn instead of retrying the same
+  failing turn.
+- MCP tools with colliding names can no longer inherit each other's saved
+  permission grants, and a server id that could be parsed as another server's
+  grant now gets a process-local alias.
+- Hook command processes are cleaned up when a turn is cancelled.
+- ACP keeps protocol stdout to itself and retains lifecycle cleanup ownership on
+  shutdown, so stray output or a failed close no longer corrupts an editor
+  session or leaves tasks behind.
+- Skill activation history is per agent, so a sub-agent no longer reuses another
+  agent's activated skills.
+- Session-journal tail recovery takes the same lock as journal writers, so
+  opening a session while another process is appending no longer corrupts or
+  duplicates its events.
+- Shared replays show sub-agent lifecycle status and fold peer messages into the
+  transcript.
+- Rewinding no longer leaves a stale diff cache reporting the content just rolled
+  back, the vision-override warning names the model that blocks the image, and
+  `exec_command` accepts `cmd=` as an alias for `command`.
+- The memory screen no longer queues worker renders for rows it is pruning.
+
+### Security
+
+- Live sharing now requires a token and validates Host and Origin headers for
+  both HTTP and WebSocket requests. Loopback and LAN links work automatically;
+  tunnel users must explicitly allow their public origin with
+  `KOLEGA_CODE_SHARE_ALLOWED_ORIGINS` before launching Kolega Code.
+- Updated transformers to 5.20.2 in the optional `tinker` extra, fixing a
+  `save_pretrained` path traversal (CVE-2026-9856) and untrusted custom
+  generation code being written to disk before consent (CVE-2026-80047). The
+  pin was previously impossible because tinker-cookbook capped transformers
+  below the fixed releases; tinker-cookbook 0.5.9 lifts that cap.
+- Updated the dev-only virtualenv pin to 21.14.13, closing twelve 21.14.x
+  activation, seed-wheel and launcher advisories that stayed an accepted risk
+  while langfuse held packaging below 26. langfuse moves to 4.18.0, whose
+  bundle includes that fix; Langfuse tracing now uses the v4
+  `start_observation`/`propagate_attributes` API. Traces keep the same span
+  names, generations, user, session and tags, but require Langfuse Cloud or a
+  self-hosted Langfuse server that supports the v4 SDK.
+
+## 0.47.1 - 2026-10-27
+
+### Changed
+
+- GPT-6.1 Terra sessions on the ChatGPT-subscription provider now use the
+  backend's advertised 500,000-token window (372,000 input tokens after the 128K
+  output reservation) instead of the GPT-6 family's conservative 400,000-token
+  budget, so compression runs later on long sessions.
+
 ## 0.47.0 - 2026-10-27
 
 ### Added

{kolega_code-0.47.0 → kolega_code-0.48.0}/CONTRIBUTING.md

@@ -120,6 +120,19 @@ You can pass additional pytest arguments through the wrapper:
 ./run_tests.sh tests/test_git_env.py -ra
 ```
 
+When changing persisted settings or session event formats, also run the
+previous-release compatibility check. It downloads the latest published
+release and its dependencies from PyPI:
+
+```bash
+uv run --frozen python scripts/check_previous_release_compat.py --install-previous
+```
+
+The check covers one old-writer settings save and an ordinary append to a
+complete journal, not general mixed-version concurrency, repeated old-writer
+saves, or journal repair. It verifies the downloaded wheel's SHA-256; its
+dependencies are resolved from PyPI without pinned hashes.
+
 ## Comments
 
 Comments are rare here. Write one only where the code cannot say it: a non-obvious

{kolega_code-0.47.0 → kolega_code-0.48.0}/MIGRATION.md

@@ -233,14 +233,35 @@ session in the store, including ones recorded for unrelated projects. With it,
 every other session answers 404 — not 403, which would confirm they exist.
 
 The same scope is available on the app directly, as
-`ServerConfig(store=..., session_ids=frozenset({...}))`. It defaults to `None`,
-meaning unrestricted, so a host serving its own sessions needs no change:
+`ServerConfig(store=..., token=..., session_ids=frozenset({...}))`. The session
+scope defaults to `None`, meaning all sessions. **A token is now required even
+for loopback embedding**; missing, empty, whitespace or non-ASCII tokens are
+rejected at app construction:
 
 ```python
-create_app(ServerConfig(store=store))                       # every session, as before
-create_app(ServerConfig(store=store, session_ids=allowed))  # only these
+import secrets
+
+token = secrets.token_urlsafe(16)
+create_app(ServerConfig(store=store, token=token))                       # every session
+create_app(ServerConfig(store=store, token=token, session_ids=allowed))  # only these
 ```
 
+HTTP and WebSocket requests also validate Host and Origin before authentication.
+`ServerConfig.allowed_hosts` defaults to `127.0.0.1`, `localhost` and `::1`; pass
+the concrete hostname or address when embedding on another interface. Origins
+for these native hosts must match the request's scheme, host and effective port
+unless explicitly included in `ServerConfig.allowed_origins`. Additional origins
+also admit their hostnames, but those inferred hosts require an exact configured
+Origin rather than trusting other schemes or ports on the same hostname.
+Only exact HTTP(S) origins are accepted, not paths or wildcard patterns.
+An absent Origin is allowed for API clients; `Origin: null` is rejected.
+
+`ShareServer` configures its bound address automatically. For a tunnel, pass
+`allowed_origins=frozenset({"https://share.example.com"})`, or set the
+comma-separated `KOLEGA_CODE_SHARE_ALLOWED_ORIGINS` process environment variable.
+An explicit `allowed_origins` argument overrides the environment, including an
+empty set. Forwarded headers are not trusted.
+
 **A served session is not redacted.** `export_bundle` scrubs every string it
 writes; this serves recorded events as they are. Anything the agent printed —
 credentials, file contents, command output — is visible to whoever holds the

{kolega_code-0.47.0 → kolega_code-0.48.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kolega-code
-Version: 0.47.0
+Version: 0.48.0
 Summary: Multi-agent coding in the terminal
 Project-URL: Homepage, https://kolega-ai.github.io/kolega-code/
 Project-URL: Documentation, https://kolega-ai.github.io/kolega-code/
@@ -41,7 +41,7 @@ Requires-Dist: google-genai==2.12.1
 Requires-Dist: httpx==0.28.1
 Requires-Dist: idna==3.18
 Requires-Dist: jinja2==3.1.6
-Requires-Dist: langfuse==3.14.5
+Requires-Dist: langfuse==4.18.0
 Requires-Dist: lxml-html-clean==0.4.5
 Requires-Dist: markdownify==1.2.3
 Requires-Dist: markitdown[docx,pdf,pptx,xls,xlsx]==0.1.6
@@ -51,7 +51,7 @@ Requires-Dist: onnxruntime==1.19.2; sys_platform == 'darwin' and platform_machin
 Requires-Dist: onnxruntime==1.27.0; python_version >= '3.14' and sys_platform != 'win32'
 Requires-Dist: openai==2.46.0
 Requires-Dist: opentelemetry-api==1.45.1
-Requires-Dist: packaging==25.0
+Requires-Dist: packaging==26.3
 Requires-Dist: pathspec==1.1.1
 Requires-Dist: pillow==13.0.0
 Requires-Dist: playwright==1.59.0
@@ -83,11 +83,12 @@ Requires-Dist: pytest-xdist==3.8.0; extra == 'dev'
 Requires-Dist: pytest==9.0.3; extra == 'dev'
 Requires-Dist: ruff==0.15.12; extra == 'dev'
 Requires-Dist: twine==6.2.0; extra == 'dev'
-Requires-Dist: virtualenv==21.14.5; extra == 'dev'
+Requires-Dist: virtualenv==21.14.13; extra == 'dev'
 Provides-Extra: tinker
-Requires-Dist: tinker-cookbook==0.5.4; extra == 'tinker'
-Requires-Dist: tinker==0.25.0; extra == 'tinker'
+Requires-Dist: tinker-cookbook==0.5.9; extra == 'tinker'
+Requires-Dist: tinker==0.35.0; extra == 'tinker'
 Requires-Dist: tml-renderers==0.1.0; extra == 'tinker'
+Requires-Dist: transformers==5.20.2; extra == 'tinker'
 Description-Content-Type: text/markdown
 
 # Kolega Code
@@ -200,7 +201,7 @@ for Zed, VS Code, and other ACP clients is in the
 **1. Install** with the script:
 
 ```bash
-curl -fsSL https://kolega.dev/install-kolega-code.sh | sh
+curl -fsSL https://kolega.ai/code/install.sh | sh
 ```
 
 Or with [uv](https://docs.astral.sh/uv/) (or `pip`):
@@ -210,6 +211,10 @@ uv tool install kolega-code
 # or: pip install kolega-code
 ```
 
+Kolega Code supports Python 3.11–3.14. uv uses its newest Python unless told
+otherwise, so if that is 3.15 or newer add `--python 3.14` (`--python 3.12` on
+Intel Macs). The install script picks a supported version for you.
+
 Verify the install:
 
 ```bash

{kolega_code-0.47.0 → kolega_code-0.48.0}/README.md

@@ -108,7 +108,7 @@ for Zed, VS Code, and other ACP clients is in the
 **1. Install** with the script:
 
 ```bash
-curl -fsSL https://kolega.dev/install-kolega-code.sh | sh
+curl -fsSL https://kolega.ai/code/install.sh | sh
 ```
 
 Or with [uv](https://docs.astral.sh/uv/) (or `pip`):
@@ -118,6 +118,10 @@ uv tool install kolega-code
 # or: pip install kolega-code
 ```
 
+Kolega Code supports Python 3.11–3.14. uv uses its newest Python unless told
+otherwise, so if that is 3.15 or newer add `--python 3.14` (`--python 3.12` on
+Intel Macs). The install script picks a supported version for you.
+
 Verify the install:
 
 ```bash

{kolega_code-0.47.0 → kolega_code-0.48.0}/RELEASING.md

@@ -1,7 +1,7 @@
 # Releasing Kolega Code
 
 This project publishes the `kolega-code` package to PyPI and serves the public
-installer from `https://kolega.dev/install-kolega-code.sh`. Each published
+installer from `https://kolega.ai/code/install.sh`. Each published
 version should also have a GitHub Release for its matching tag.
 
 ## Release process
@@ -71,8 +71,8 @@ because those forms can select and recreate the development `.venv`.
    - Use the release date from the release PR merge.
    - Leave an empty `Unreleased` section above the new release section.
 
-4. Bootstrap the dedicated release environment, run the fast test suite, and
-   run the same pre-commit checks as CI:
+4. Bootstrap the dedicated release environment, run the fast test suite and
+   the same pre-commit checks as CI, and run the compatibility preflight:
 
    ```bash
    UV_PROJECT_ENVIRONMENT="$PWD/.venv-release" \
@@ -81,11 +81,17 @@ because those forms can select and recreate the development `.venv`.
      ./run_tests.sh
    UV_PROJECT_ENVIRONMENT="$PWD/.venv-release" \
      uv run pre-commit run --all-files --show-diff-on-failure
+   UV_PROJECT_ENVIRONMENT="$PWD/.venv-release" \
+     uv run --frozen python scripts/check_previous_release_compat.py --install-previous --release-preflight
    ```
 
    `UV_PROJECT_ENVIRONMENT` is inherited by pre-commit's local `pyright` hook,
    including the hook's nested `uv run`.
 
+   The compatibility preflight installs the latest stable PyPI release older
+   than the candidate in an isolated environment. Run it before opening the
+   release PR; it is not run by CI or the release workflow.
+
    To reproduce a version-specific CI failure, target the same disposable
    environment explicitly:
 
@@ -130,7 +136,7 @@ because those forms can select and recreate the development `.venv`.
 8. Verify the release:
 
    ```bash
-   uv tool install --force kolega-code
+   kolega-code update
    kolega-code --version
    gh release view v0.3.2 --repo kolega-ai/kolega-code
    ```
@@ -159,24 +165,21 @@ the organization request.
    The release workflow publishes to PyPI automatically when a release tag is
    pushed; no manual deployment approval is required.
 
-## Installer handoff
+## Installer
 
-The canonical installer source is tracked at:
+The installer source is tracked at:
 
 ```text
 scripts/install-kolega-code.sh
 ```
 
-The `kolega.dev` site repo should publish that file verbatim at:
-
-```text
-https://kolega.dev/install-kolega-code.sh
-```
-
-After updating the site, verify:
+`https://kolega.ai/code/install.sh` redirects to that file on `main`, via a
+rule in the kolega-website repo's `next.config.mjs`. There is no copy to
+publish: an installer change is live as soon as it merges, so it must work
+with the release currently on PyPI. After merging one, verify:
 
 ```bash
-curl -fsSL https://kolega.dev/install-kolega-code.sh | sh
+curl -fsSL https://kolega.ai/code/install.sh | sh
 ```
 
 ## Transfer to the PyPI organization

{kolega_code-0.47.0 → kolega_code-0.48.0}/kolega_code/__init__.py

@@ -174,4 +174,4 @@ __all__ = [
     "parse_git_status_output",
 ]
 
-__version__ = "0.47.0"
+__version__ = "0.48.0"

{kolega_code-0.47.0 → kolega_code-0.48.0}/kolega_code/acp/__init__.py

@@ -18,7 +18,7 @@ from kolega_code.acp.permissions import AcpPermissionBroker
 from kolega_code.acp.plans import task_entries_from_markdown
 from kolega_code.acp.server import AcpAgent
 from kolega_code.acp.session import AcpSession
-from kolega_code.acp.usage import build_usage_update, context_window_for
+from kolega_code.acp.usage import build_context_usage_update, build_usage_update, context_window_for
 
 __all__ = [
     "ACP_AGENT_MODE",
@@ -33,6 +33,7 @@ __all__ = [
     "AgentFactory",
     "TOOL_KINDS",
     "build_usage_update",
+    "build_context_usage_update",
     "context_window_for",
     "task_entries_from_markdown",
 ]