@loonglab/loongcode-cli 0.1.2 → 0.1.3

package/CHANGELOG.md

@@ -4,8 +4,33 @@ All notable changes to LoongCode will be documented in this file.
 
 ## [Unreleased]
 
+## [0.1.3] - 2026-10-13
+
+A model-configuration and context-management release. The setup flow sets a
+model's context window and output ceiling again; `/model` edits and removes
+models — seeded from what is saved, never displaying a stored key, and always
+tested before anything is written; and a run whose context overflows no longer
+ends when compaction cannot help: the request is reduced instead, and every
+compaction that cannot progress is reported rather than discarded. It also
+records the rename and the command consolidation the code has carried since
+0.1.2, which are listed below.
+
 ### Added
 
+- Model configuration is complete again in the product. The setup flow's
+  unnumbered `Configure limits…` sub-step sets a new model's `contextWindow` and
+  `maxOutputTokens` (defaulting to 128000 and 8192, validated as positive
+  integers with the output ceiling no larger than the window); the values are
+  shown on the screen that confirms the connection test, and the probe tests
+  exactly the configuration that will be saved. `/model` offers `Edit model…`,
+  which runs the same sequence seeded from what is saved — the id and its
+  derived name stay put, the stored API key is never displayed and is either
+  kept or replaced through the masked prompt, and nothing is written until a
+  connection test succeeds — and `Remove model…`, which confirms by name.
+  Removing the active model reopens setup immediately instead of waiting for the
+  next task; removing any other model leaves the active one alone. All three
+  actions are refused while a task or a compaction is running, so a model change
+  can never take the workspace view out from under a run.
 - An empty transcript now opens with a large `LOONGCODE` block wordmark and the
   descriptor "an opinionated coding agent", followed by the existing keyboard
   hints. The hero is a true empty state: it is centered as a group in the
@@ -58,6 +83,11 @@ All notable changes to LoongCode will be documented in this file.
 
 ### Removed
 
+- The `settings.json` key `model`. It documented a "default active model id"
+  that nothing ever read, and its validation could fail a settings load — and
+  through it a run — over a value with no effect. The active model has always
+  been owned by `models.json`; a settings file that still carries the key keeps
+  loading, because unknown keys are ignored.
 - Slash command `/reload`. Prompt templates are discovered live, `AGENTS.md` /
   `CLAUDE.md` and agent-facing resources load on every run, so there is nothing
   left to refresh manually.
@@ -77,6 +107,42 @@ All notable changes to LoongCode will be documented in this file.
   capabilities now live inside the `/session` manager; they are not retained
   as aliases.
 
+### Fixed
+
+- A run no longer ends when its context overflows and compaction cannot help. In
+  a single-task run the compactable region is the task itself — everything the
+  run produced sits after the last user message — so compaction reported
+  `no-progress / empty-tail` and the run stopped with `context overflow detected
+  but compaction made no progress: empty-tail`. The request projection is now
+  reduced instead: tool output the model can get back is withheld from the
+  request — output a cap spilled to a captured artifact (`spillPath`), or a
+  `read` that names the file it read (`sourcePath`, plus `resumeOffset` when the
+  read was capped) — while the two most recent recoverable results, failed
+  executions, and observed-failure evidence are kept, and each withheld result
+  states what it held and how to get back to it. The two kinds of route do not
+  promise the same thing: a spill artifact holds the output as it was, while a
+  path re-reads the file's current contents — so a read whose file a later write
+  or edit in the same history names is kept, rather than offered a route that
+  would return something the model never read. Only the request is reduced:
+  durable history is untouched, and a reference that no longer resolves fails as
+  a normal read error rather than returning invented content. Recovery is
+  bounded like compaction retries (five per run), never sends a reduced request
+  identical to one a provider has already rejected, and ends the run naming the
+  failed stage and carrying the provider's own diagnostic when nothing
+  recoverable remains.
+- Compaction that cannot progress is no longer silent. The proactive check used
+  to discard a `no-progress` outcome entirely, so the only trace of it was the
+  failure it eventually caused; every attempt now emits a `compaction_skipped`
+  event naming the reason (`empty-tail`, `no-compactable-region`,
+  `empty-summary`) and the trigger (`proactive`, `reactive`, `provider`), a
+  recovery emits `projection_reduced`, and the run record carries
+  `compactionSkips` and `projectionRecoveries` so a finished run still explains
+  itself. A proactive verdict is reported once per unchanged history: the
+  attempt is not repeated — with its checkpoint and its event — on every
+  iteration that changes nothing compaction could act on, and is retried as soon
+  as the history moves. `/compact` reports which reason applied instead of a
+  bare "nothing to compact".
+
 ## [0.1.2] - 2026-10-12
 
 A cross-platform compatibility release. Windows gets a real choice of shell —

package/README.md

@@ -25,9 +25,16 @@ On first launch no model is active, and LoongCode says so: it opens the setup
 flow (protocol `openai` or `anthropic`, endpoint, model name, API key) before
 the workspace appears, and the normal interface is not reachable until a model
 is active. `/model` is that same flow — it lists the models you have configured
-and offers `Add model…` for a new one. Context and output limits are defaulted,
-and only exposed under an optional *Configure limits…* step. Cancelling setup
-exits; a task you had already typed is not run and is not saved.
+and offers `Add model…`, `Edit model…` and `Remove model…`. Context and output
+limits are defaulted to 128000 and 8192, and changeable in the flow's optional
+*Configure limits…* step. Cancelling setup exits; a task you had already typed
+is not run and is not saved.
+
+Editing a model reuses the flow, seeded from what is saved: the stored API key
+is never displayed — you choose to keep it or enter a replacement — and the
+change is saved only after a connection test succeeds. Model changes are refused
+while a task or a compaction is running, and removing the active model reopens
+setup.
 
 ## Scripting