@liqngliz/browser-coding-agent 0.0.0-ci.8 → 0.1.2

package/README.md

@@ -60,8 +60,9 @@ node scripts/smoke.mjs --npm artifacts/npm/liqngliz-browser-coding-agent-0.0.0-l
 | `ci.yml` | PR, push to `main` | `build.yml` with version `0.0.0-ci.<run>` |
 | `build.yml` | called | tests (ubuntu/windows/macos), packs `.nupkg` + `.tgz` once, smoke-tests both on windows, macOS arm64, macOS x64, plus npm bootstrap in a container without .NET |
 | `release.yml` | tag `v<semver>` | `build.yml`, then publishes the tested artifacts to nuget.org and npm (`latest`, or `next` for prerelease tags) |
+| `post-release-smoke.yml` | after `release`, or manual | waits for nuget.org to serve the version, installs the tool from nuget.org, smoke-tests it with installed Edge on windows, macOS arm64, macOS x64 |
 
-Release: `git tag v0.1.0 && git push origin v0.1.0`. Publish jobs use the `release` environment and OIDC trusted publishing; no API keys are stored.
+Release: `git tag v0.1.0 && git push origin v0.1.0`. Run without installing: `dnx BrowserCodingAgent` (or `dnx BrowserCodingAgent@0.1.0`). Publish jobs use the `release` environment and OIDC trusted publishing; no API keys are stored.
 
 ## Running locally
 
@@ -127,5 +128,6 @@ Persistent profiles default to `~/.browser-coding-agent/profiles/<channel>` outs
 - **Streaming:** `stream: true` -> SSE `chat.completion.chunk` deltas, `data: [DONE]`, `: keep-alive` every 15s; `stream_options.include_usage` -> zero-valued usage chunk (M365 exposes no token counts). Errors after Send arrive as an in-stream `{"error": ...}` event.
 - **Parameters:** `n: 1` only; `response_format` -> HTTP 400; legacy `functions`, `temperature`, and other generation settings are ignored (logged).
 - **Tool calling (emulated):** `tools` are described in the prompt as plain text; fenced call blocks in Copilot's reply come back as `tool_calls` with `finish_reason: "tool_calls"` (streamed as one `tool_calls` delta). `tool_choice`: `none` disables tools, `required` or a named function adds a must-call line. `tool` result messages are sent as `Result of <tool name>:`. Copilot web chat has no native function calling, so calls depend on Copilot following the format.
+- **Long prompts:** some M365 accounts cap the composer at 8000 characters. When the composer keeps only a prefix, or Send stays disabled on a prompt over 8000 characters, nothing is sent and the prompt is resent in parts in the same chat ("Part k of n … reply only with: received k/n"; the last part asks for the answer). Set `--Chat:MaxPromptChars=7000` on such accounts to split up front; default `0` splits only after a refusal. Each extra part uses one Copilot message.
 - **Concurrency:** Single-request gate. Overlapping requests receive HTTP 409 Conflict.
 - **Turn recovery:** Uncertain submissions or timeouts require manual recovery before accepting new prompts.

package/app/BrowserCodingAgent.Api.deps.json

@@ -6,7 +6,7 @@
   "compilationOptions": {},
   "targets": {
     ".NETCoreApp,Version=v10.0": {
-      "BrowserCodingAgent.Api/0.0.0-ci.8": {
+      "BrowserCodingAgent.Api/0.1.2": {
         "dependencies": {
           "Microsoft.AspNetCore.OpenApi": "10.0.13",
           "Microsoft.Playwright": "1.63.0",
@@ -65,7 +65,7 @@
     }
   },
   "libraries": {
-    "BrowserCodingAgent.Api/0.0.0-ci.8": {
+    "BrowserCodingAgent.Api/0.1.2": {
       "type": "project",
       "serviceable": false,
       "sha512": ""

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@liqngliz/browser-coding-agent",
-  "version": "0.0.0-ci.8",
+  "version": "0.1.2",
   "description": "OpenAI-compatible chat completions server backed by Microsoft 365 Copilot web chat via Playwright.",
   "bin": {
     "browser-coding-agent": "browser-coding-agent.cjs"