fastctx 0.2.0 → 0.2.2

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.
Files changed (2) hide show
  1. package/README.md +26 -9
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -4,12 +4,26 @@
4
4
 
5
5
  FastCtx gives coding agents structured repository tools — `read`, `grep`,
6
6
  `glob`, `replace`, and an optional bash terminal — served by one local Rust
7
- binary over MCP.
7
+ binary over MCP. `read` can pack 1–32 known text files into one request-ordered
8
+ call with exact per-file continuation parameters, while images, PDFs, and hex
9
+ view remain single-file reads.
8
10
 
9
11
  The optional terminal publishes `run`, `run_background`, `job_output`,
10
12
  `job_kill`, and `job_list`. Background jobs have no automatic timeout and
11
- survive MCP server and Codex restarts; their rolling output and exit status
12
- remain addressable by job id under `~/.fastctx/jobs/`.
13
+ survive MCP server and Codex restarts. Current-format jobs keep their complete
14
+ output log and exit status addressable by job id under `~/.fastctx/jobs/`.
15
+ `job_output` is a query with a caller-chosen delay: it returns when the job
16
+ ends or when `wait_ms` (0–240000 ms, default 30000) elapses, showing the newest
17
+ output not yet seen, and names the log path and exact line numbers for anything
18
+ it leaves out. Intermediate output does not end the wait. `Complete` appears
19
+ only after a job ends; servers and watchers may never reach it. Records from
20
+ the preceding segmented format remain readable but do not claim direct log
21
+ coordinates or recover output their original rolling window evicted.
22
+ While one server tracks jobs it started or queried, each successful text result
23
+ also carries a one-line background readout of their current state and elapsed
24
+ time. It refreshes only on tool calls; it is not a push notification, and
25
+ nothing arrives if the caller stops. Finished entries remain until that server
26
+ handles them with `job_output` or `job_kill`.
13
27
 
14
28
  On Windows, all FastCtx-owned non-interactive children run without allocating
15
29
  a console window; no caller flag is required. Commands that explicitly launch
@@ -22,7 +36,7 @@ for that user (default 128). `job_list` shows running jobs by default; explicit
22
36
  `status="finished"` exposes retained history, while `fastshell.job_list_limit`
23
37
  sets the default page size (20, valid range 1–100). All three settings take
24
38
  effect immediately when saved.
25
- Job commands, working directories, rolling output, and exit status stay in the
39
+ Job commands, working directories, output logs, and exit status stay in the
26
40
  current user's private local directory and are never uploaded by FastCtx.
27
41
 
28
42
  grep/glob keeps its existing automatic CPU parallelism by default. The TUI can
@@ -54,11 +68,14 @@ npm install --global fastctx --registry=https://registry.npmjs.org/
54
68
  This package is the launcher: it selects the matching scoped platform package
55
69
  (`@fastctx/win32-x64`, `@fastctx/linux-x64`, or the corresponding macOS
56
70
  package) locally and starts the complete binary. There is no postinstall script
57
- and no telemetry. The interactive TUI opens immediately while FastCtx checks
58
- this exact npm package in the background; successful results are cached for 24
59
- hours in machine-private storage. Transient failures stay quiet and remain
60
- available under Status. If GitHub is newer while npm is still propagating, the
61
- UI says so and offers retry. Updates require confirmation, install an exact
71
+ and no telemetry. The interactive TUI checks this exact
72
+ npm package for updates before the main menu opens; the wait is strictly
73
+ bounded, and a failed or timed-out check enters silently. When a newer version
74
+ is installable, the update screen opens directly and asks whether to update or
75
+ continue. Successful results are cached for 24 hours in machine-private
76
+ storage. Transient failures stay quiet and remain available under Status. If
77
+ GitHub is newer while npm is still propagating, the Update screen says so and
78
+ offers retry. Updates require confirmation, install an exact
62
79
  version with lifecycle scripts disabled, and restart through a copied helper.
63
80
  A failed update restores and reopens the previous version with a warning.
64
81
  `fastctx serve` and MCP tool calls do not perform update traffic; commands run
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "fastctx",
3
- "version": "0.2.0",
3
+ "version": "0.2.2",
4
4
  "description": "FastCtx — fast, context-efficient repository tools for AI agents.",
5
5
  "author": "yc-duan <dy2958830371@gmail.com>",
6
6
  "license": "MIT OR Apache-2.0",
@@ -22,10 +22,10 @@
22
22
  "licenses/**"
23
23
  ],
24
24
  "optionalDependencies": {
25
- "@fastctx/win32-x64": "0.2.0",
26
- "@fastctx/linux-x64": "0.2.0",
27
- "@fastctx/darwin-x64": "0.2.0",
28
- "@fastctx/darwin-arm64": "0.2.0"
25
+ "@fastctx/win32-x64": "0.2.2",
26
+ "@fastctx/linux-x64": "0.2.2",
27
+ "@fastctx/darwin-x64": "0.2.2",
28
+ "@fastctx/darwin-arm64": "0.2.2"
29
29
  },
30
30
  "publishConfig": {
31
31
  "access": "public"