@vedmalex/ai-connect 0.10.1 → 0.11.0

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 (33) hide show
  1. package/README.md +7 -7
  2. package/dist/browser/index.js +472 -242
  3. package/dist/browser/index.js.map +3 -3
  4. package/dist/bun/index.js +1104 -391
  5. package/dist/bun/index.js.map +4 -4
  6. package/dist/bun/local.js +1100 -391
  7. package/dist/bun/local.js.map +4 -4
  8. package/dist/node/index.js +1104 -391
  9. package/dist/node/index.js.map +4 -4
  10. package/dist/node/local.js +1100 -391
  11. package/dist/node/local.js.map +4 -4
  12. package/dist/types/acp.d.ts.map +1 -1
  13. package/dist/types/cli.d.ts +8 -0
  14. package/dist/types/cli.d.ts.map +1 -1
  15. package/dist/types/client-tools-mcp.d.ts +82 -0
  16. package/dist/types/client-tools-mcp.d.ts.map +1 -0
  17. package/dist/types/client-tools-text-protocol.d.ts +70 -0
  18. package/dist/types/client-tools-text-protocol.d.ts.map +1 -0
  19. package/dist/types/client.d.ts +20 -0
  20. package/dist/types/client.d.ts.map +1 -1
  21. package/dist/types/config.d.ts +8 -1
  22. package/dist/types/config.d.ts.map +1 -1
  23. package/dist/types/index.browser.d.ts +2 -2
  24. package/dist/types/index.browser.d.ts.map +1 -1
  25. package/dist/types/index.d.ts +2 -2
  26. package/dist/types/index.d.ts.map +1 -1
  27. package/dist/types/model-reference.d.ts +25 -10
  28. package/dist/types/model-reference.d.ts.map +1 -1
  29. package/dist/types/router.d.ts.map +1 -1
  30. package/dist/types/server.d.ts.map +1 -1
  31. package/dist/types/types.d.ts +36 -2
  32. package/dist/types/types.d.ts.map +1 -1
  33. package/package.json +1 -1
package/README.md CHANGED
@@ -1207,12 +1207,10 @@ ACP routes are treated as harness-owned connections:
1207
1207
  Tool semantics are intentionally split:
1208
1208
 
1209
1209
  - `api` routes support tool schema passthrough via `parameters.tools`
1210
- - `api` routes also support client-managed tools through `clientTools`
1211
- - `clientTools` are executed locally by `ai-connect` after the provider returns tool calls
1212
1210
  - `parameters.tools` remains the right path for upstream-managed tool schemas that are not executed by `ai-connect`
1213
1211
  - `acp` routes support harness-owned tool execution
1214
1212
  - `acp` routes do not currently forward request-defined tool schema from `parameters.tools`
1215
- - `cli` and current built-in `server` routes do not support tool schema passthrough or tool execution
1213
+ - client-managed tools (`clientTools`) are executed locally by `ai-connect` and work on **all four transports** (since 0.11.0): natively on `api`, via an in-process loopback MCP bridge on `acp` (`session/new.mcpServers`; the agent must advertise HTTP MCP support), and via a shared text-based round protocol on `cli` / `server`
1216
1214
 
1217
1215
  That distinction is also reflected in route capabilities:
1218
1216
 
@@ -1257,11 +1255,13 @@ const result = await client.generate({
1257
1255
  });
1258
1256
  ```
1259
1257
 
1260
- Current limits:
1258
+ `clientTools` semantics (as of 0.11.0 — see `docs/whats-new-0.11.md` for the full matrix):
1261
1259
 
1262
- - `clientTools` are supported only for `generate()`
1263
- - `clientTools` are currently supported only for text requests without attachments/image options
1264
- - built-in local execution of `clientTools` is implemented for built-in API handlers: `openai`, `anthropic`, `gemini`
1260
+ - work in both `generate()` and `stream()` (streaming runs a full multi-round tool loop and emits additive `tool-call` / `tool-result` stream events)
1261
+ - combine with `attachments`/image input on `text`-operation requests: round 1 carries the attachments, follow-up rounds rely on message history; routing is capability-gated (`supportsClientToolExecution` AND `supportsImageInput`/`supportsFileUpload`), an incapable route pool fails fast with `unsupported_capability`
1262
+ - `operation: "image"` / `"file"` combined with `clientTools` is rejected up front with `unsupported_capability` (tool-loop semantics exist only for `text`)
1263
+ - built-in local execution on `api` routes covers the built-in handlers (`openai`, `anthropic`, `gemini`); `acp`/`cli`/`server` execute through their transport bridges (see the tool-semantics list above)
1264
+ - per-model capability hints (curated `MODEL_REFERENCE`) can narrow route capabilities per model — e.g. an embeddings model on a vision-capable provider no longer advertises image input in `listCandidateModels()`
1265
1265
 
1266
1266
  ### Context and MCP Semantics
1267
1267