free-computer-use 0.2.4 → 0.2.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,22 @@
2
2
 
3
3
  ## Unreleased
4
4
 
5
+ ## 0.2.6 - 2026-09-27
6
+
7
+ ### Fixed
8
+
9
+ - Keep unchanged controls and page data in follow-up planner context when a
10
+ compact page diff would omit them. Use diffs only when they contain the full
11
+ current snapshot needed by the next stateless provider call.
12
+
13
+ ## 0.2.5 - 2026-09-27
14
+
15
+ ### Changed
16
+
17
+ - Planner responses no longer repeat the task goal. The runtime keeps the
18
+ validated original goal, preserving the 4,000-character limit while leaving
19
+ more output budget for steps, actions and checks.
20
+
5
21
  ## 0.2.4 - 2026-09-27
6
22
 
7
23
  ### Fixed
package/README.md CHANGED
@@ -24,16 +24,16 @@
24
24
 
25
25
  Use an API or supported model CLI for open-ended tasks. Skip model setup for common page-reading jobs: deterministic local strategies read visible text, links and tables without a model call.
26
26
 
27
- ## New in 0.2.4: one task-goal limit everywhere
27
+ ## New in 0.2.6: keep current context between plans
28
28
 
29
- CLI, library, dashboard and MCP tasks now share the same 4,000-character goal limit. Overlong goals fail before the browser opens or a run is saved, instead of reaching a planner schema that cannot accept them. Version 0.2.3 aligned the planner schema with the dashboard and MCP limit.
29
+ When a task needs another planning pass, unchanged controls and page text stay available to the next plan. The agent uses a compact diff only when it contains all current controls and relevant page data; otherwise it sends the full bounded snapshot. This fixes follow-up plans that could lose useful context between stateless model calls.
30
30
 
31
31
  ## No model key needed
32
32
 
33
33
  Install the release and start the local dashboard:
34
34
 
35
35
  ```bash
36
- npm install --global free-computer-use@0.2.4
36
+ npm install --global free-computer-use@0.2.6
37
37
  FCU_BROWSER_CHANNEL=chrome agent doctor
38
38
  FCU_BROWSER_CHANNEL=chrome agent ui
39
39
  ```
@@ -47,7 +47,7 @@ Open **http://127.0.0.1:4318**, enter a page URL and one of these goals, then ap
47
47
  | `Extract the first 5 links` | Return a bounded list of the first five links. |
48
48
  | `Extract the table` | Try the synthetic [practice revenue table](https://othmaneblial.github.io/FreeComputerUse/lab/reports.html). |
49
49
 
50
- These narrow workflows use local strategies and make zero model calls. General tasks need a configured provider. Release candidate 0.2.4 passed the full local suite 137/137 on Node.js 25.9.0; 0.2.3 passed 136/136. Runs used macOS 26.6/Apple Silicon with system Chrome 154.0.8037.57. Windows/Linux and other browser builds remain unverified. See the [support matrix](docs/SUPPORT_MATRIX.md).
50
+ These narrow workflows use local strategies and make zero model calls. General tasks need a configured provider. Release validation and platform coverage are recorded in the [support matrix](docs/SUPPORT_MATRIX.md).
51
51
 
52
52
  ## Watch a real run
53
53
 
@@ -77,7 +77,7 @@ Requires Node.js 22.13+, npm and an installed browser. The verified setup select
77
77
  ### Install from npm
78
78
 
79
79
  ```bash
80
- npm install --global free-computer-use@0.2.4
80
+ npm install --global free-computer-use@0.2.6
81
81
  FCU_BROWSER_CHANNEL=chrome agent doctor
82
82
  FCU_BROWSER_CHANNEL=chrome agent ui
83
83
  ```