wayang-ai 0.5.1 → 0.5.2

package/README.md

@@ -90,7 +90,8 @@ Or create `~/.wayang.config.json` manually:
     "my-model": {
       "endpoint": "https://api.anthropic.com",
       "modelName": "claude-sonnet-4-20250514",
-      "apiKey": "xxx"
+      "apiKey": "xxx",
+      "contextWindowTokens": 200000
     }
   },
   "controller": { "provider": "my-model" },
@@ -100,10 +101,12 @@ Or create `~/.wayang.config.json` manually:
 
 API key can be set via config or the `WAYANG_LLM_API_KEY` environment variable.
 
-Workers default to `"toolChoice": "required"` — every step must emit a tool call, so a worker always finishes via its `done`/`fail` tools. Some OpenAI-compatible endpoints (e.g. internal llmproxy proxies) reject `tool_choice: "required"` with HTTP 400; for those, opt out per-endpoint in the `worker` section:
+`contextWindowTokens` (optional, per provider) is the model's context window in tokens: the input budget the prompt must fit into, not the protocol's `max_tokens` output cap. The controller compacts the conversation once it reaches 90% of this budget. It defaults to 256000; set it explicitly for smaller-window models (e.g. `128000`), otherwise the provider rejects requests before compaction triggers. With env-only configuration use `WAYANG_CONTEXT_WINDOW_TOKENS`.
+
+Workers default to `"toolChoice": "auto"` — the model decides whether to call a tool, since thinking endpoints (DeepSeek/GLM) reject `tool_choice: "required"` with HTTP 400. On endpoints that support it, set `"required"` to force a tool call every step, so a worker always finishes via its `done`/`fail` tools:
 
 ```json
-"worker": { "provider": "my-model", "maxConcurrency": 3, "toolChoice": "auto" }
+"worker": { "provider": "my-model", "maxConcurrency": 3, "toolChoice": "required" }
 ```
 
 ### Run