@nanobpm/nano-coder 0.63.0 → 0.63.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 +10 -1
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -682,7 +682,7 @@ kind = "anthropic"
682
682
  base_url = "https://llm-gateway.example.com/anthropic/v1"
683
683
  api_key_env = "WORK_GATEWAY_KEY" # or api_key = "..." (prefer the env var)
684
684
  # api_key_command = "op read op://vault/gateway/key" # used when the env var is unset
685
- timeout_secs = 300 # idle timeout: max silence between streamed bytes (default 600)
685
+ timeout_secs = 300 # idle timeout: max silence between streamed bytes (default 120, or $NANO_CODER_PROVIDER_TIMEOUT_SECS)
686
686
  max_retries = 3
687
687
  ```
688
688
 
@@ -888,6 +888,15 @@ Other per-provider fields: `replay_reasoning`, `max_tokens_param` (`max_tokens`,
888
888
  which is the `openai` default), `retry_initial_backoff_ms`, `retry_max_backoff_ms`,
889
889
  `retryable_statuses` and `offline_budget_ms`.
890
890
 
891
+ `timeout_secs` is an *idle* timeout: it resets on every received byte, so a slow but steady
892
+ stream is never cut off — only a genuinely stalled connection trips it. The default is 120 s
893
+ (`NANO_CODER_PROVIDER_TIMEOUT_SECS` overrides the default; an explicit `timeout_secs` wins
894
+ over both). When nano-coder runs under a supervisor that idle-kills a silent run — e.g. the
895
+ c8ctl-nano worker, which kills a run after 300 s of no output — `timeout_secs` must stay
896
+ **below** that budget: at or above it the worker kills the whole run before a stalled stream
897
+ is ever detected and retried. A supervising worker can pass its own derived budget (e.g. its
898
+ idle-kill budget / 2) as `NANO_CODER_PROVIDER_TIMEOUT_SECS` so the two timeouts cannot drift.
899
+
891
900
  A transport failure with no HTTP response (DNS, connection refused or reset, connect or
892
901
  idle timeout) is treated as the network being down rather than a failed attempt: nano-coder
893
902
  backs off (`retry_initial_backoff_ms` doubling to `retry_max_backoff_ms`) and keeps waiting,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nanobpm/nano-coder",
3
- "version": "0.63.0",
3
+ "version": "0.63.2",
4
4
  "description": "A 6MB coding agent. Run a fleet on your laptop.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -27,9 +27,9 @@
27
27
  "node": ">=18"
28
28
  },
29
29
  "optionalDependencies": {
30
- "@nanobpm/nano-coder-darwin-arm64": "0.63.0",
31
- "@nanobpm/nano-coder-darwin-x64": "0.63.0",
32
- "@nanobpm/nano-coder-linux-arm64": "0.63.0",
33
- "@nanobpm/nano-coder-linux-x64": "0.63.0"
30
+ "@nanobpm/nano-coder-darwin-arm64": "0.63.2",
31
+ "@nanobpm/nano-coder-darwin-x64": "0.63.2",
32
+ "@nanobpm/nano-coder-linux-arm64": "0.63.2",
33
+ "@nanobpm/nano-coder-linux-x64": "0.63.2"
34
34
  }
35
35
  }