@getenki/ai-darwin-arm64 0.5.41 → 0.5.61

package/README.md

@@ -19,6 +19,7 @@ The package ships prebuilt native binaries for:
 The current package surface is:
 
 - `NativeEnkiAgent`
+- `NativeToolRegistry`
 - `NativeMultiAgentRuntime`
 - `NativeWorkflowRuntime`
 - `JsAgentStatus`
@@ -29,13 +30,22 @@ The current package surface is:
 - `JsAgentRunResult`
 - `JsExecutionStep`
 
-`NativeEnkiAgent` is the main entrypoint. It can be created in four modes:
+`NativeEnkiAgent` is the main entrypoint. It can be created in five modes:
 
 - `new(...)` for a plain agent
 - `NativeEnkiAgent.withTools(...)`
+- `NativeEnkiAgent.withToolRegistry(...)`
 - `NativeEnkiAgent.withMemory(...)`
 - `NativeEnkiAgent.withToolsAndMemory(...)`
 
+`NativeToolRegistry` supports:
+
+- `new(...)`
+- `registerTools(...)`
+- `clear()`
+- `toolNames()`
+- `size`
+
 It also supports two loop customization levels:
 
 - `agenticLoop` constructor arguments for prompt-level loop customization
@@ -290,6 +300,79 @@ Instead of putting `execute` on every tool, you can pass a shared `toolHandler`
 - `workspaceDir`
 - `sessionsDir`
 
+### Reusable Tool Registries
+
+If you want to manage a shared pool of tools and attach it to multiple agents later, create a `NativeToolRegistry` and connect it dynamically:
+
+```js
+const { NativeEnkiAgent, NativeToolRegistry } = require('@getenki/ai')
+
+const registry = new NativeToolRegistry()
+registry.registerTools(
+  [
+    {
+      name: 'lookup_release',
+      description: 'Return a canned release note.',
+      parametersJson: JSON.stringify({
+        type: 'object',
+        properties: {
+          version: { type: 'string' },
+        },
+        required: ['version'],
+      }),
+    },
+  ],
+  (toolName, inputJson) => JSON.stringify({ toolName, inputJson }),
+)
+
+const agent = new NativeEnkiAgent(
+  'Registry Agent',
+  'Use connected tools when they help.',
+  'ollama::qwen3.5:latest',
+  20,
+  process.cwd(),
+)
+
+agent.connectToolRegistry(registry)
+```
+
+You can also construct the agent directly from a registry with `NativeEnkiAgent.withToolRegistry(...)`.
+
+This is the cleanest path when multiple agents should share the same tool catalog or when tools need to be connected after agent construction.
+
+TypeScript uses the same API:
+
+```ts
+import { NativeEnkiAgent, NativeToolRegistry } from '@getenki/ai'
+
+const registry = new NativeToolRegistry()
+registry.registerTools(
+  [
+    {
+      name: 'lookup_release',
+      description: 'Return a canned release note.',
+      parameters: {
+        type: 'object',
+        properties: {
+          version: { type: 'string' },
+        },
+        required: ['version'],
+      },
+    },
+  ],
+  (toolName: string, inputJson: string) => JSON.stringify({ toolName, inputJson }),
+)
+
+const agent = NativeEnkiAgent.withToolRegistry(
+  'Registry Agent',
+  'Use connected tools when they help.',
+  'ollama::qwen3.5:latest',
+  20,
+  process.cwd(),
+  registry,
+)
+```
+
 ## Memory
 
 Memory modules are plain objects:
@@ -608,6 +691,7 @@ JavaScript example:
 cd example/basic-js
 npm install
 npm start
+npm run start:tool-registry
 npm run start:custom-agent-loop
 npm run start:react-custom-agent-loop
 npm run start:multi-agent-tools-memory

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getenki/ai-darwin-arm64",
-  "version": "0.5.41",
+  "version": "0.5.61",
   "cpu": [
     "arm64"
   ],