@openenthrium/oe-runtime 1.7.4 → 1.7.5
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.
- package/README.md +22 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -21,6 +21,7 @@ Open Enthrium AI Agent Runtime (OE Runtime) is a standalone, cross-platform bina
|
|
|
21
21
|
- **45+ connector categories.** PostgreSQL, MySQL, MongoDB, S3, Slack, GitHub, SSH, REST API, Kafka, and more — all built in.
|
|
22
22
|
- **Agent chains.** Chain agents together in YAML — auto chains fire in sequence; manual chains pause for human approval in CLI (y/n prompt), HTTP (`/approve-chain`), or any MCP-enabled AI chat (`approve_chain` tool).
|
|
23
23
|
- **HTTP server mode.** `--serve` turns the runtime into a persistent API server any app can call.
|
|
24
|
+
- **SDK.** `@openenthrium/oe-runtime-sdk` lets you embed agent execution directly inside your Node.js app — same engine, no subprocess, no HTTP call. `npm install @openenthrium/oe-runtime-sdk`
|
|
24
25
|
- **Messaging platform integration.** Receive messages from Telegram, Slack, WhatsApp, Teams and run agents in response — same YAML agents, same connectors, universal command language (`/run`, `/agents`, `/approve`, `/status`).
|
|
25
26
|
- **Project system.** `oe-project.json` registers multiple agents by name, sets a default agent, and links projects together — one config, many agents.
|
|
26
27
|
- **Self-hosted.** Runs entirely on your own machine. No call-home. Own your data.
|
|
@@ -365,6 +366,27 @@ curl -X POST http://localhost:3333/command \
|
|
|
365
366
|
|
|
366
367
|
---
|
|
367
368
|
|
|
369
|
+
## Embed in Your App
|
|
370
|
+
|
|
371
|
+
Need to call agents from inside a Node.js application — without spawning a subprocess or making HTTP calls? Use the **OE Runtime SDK**:
|
|
372
|
+
|
|
373
|
+
```bash
|
|
374
|
+
npm install @openenthrium/oe-runtime-sdk pg # install only the connectors you need
|
|
375
|
+
```
|
|
376
|
+
|
|
377
|
+
```js
|
|
378
|
+
const { runAgent } = require("@openenthrium/oe-runtime-sdk");
|
|
379
|
+
|
|
380
|
+
const result = await runAgent("./agent.yaml", "./oe-config.json", { topic: "Q3 sales" });
|
|
381
|
+
console.log(result.output);
|
|
382
|
+
```
|
|
383
|
+
|
|
384
|
+
Same engine. Same `agent.yaml`. Same `oe-config.json`. No subprocess overhead.
|
|
385
|
+
|
|
386
|
+
→ **[`@openenthrium/oe-runtime-sdk` on npm](https://www.npmjs.com/package/@openenthrium/oe-runtime-sdk)**
|
|
387
|
+
|
|
388
|
+
---
|
|
389
|
+
|
|
368
390
|
## Binary vs Node.js Mode
|
|
369
391
|
|
|
370
392
|
Both **`npx @openenthrium/oe-runtime`** and the standalone binary exclude Oracle, MSSQL, SQLite, and Snowflake — these use native C++ addons that cannot be bundled into a single executable. npx downloads the same binary under the hood, so it has the same limitation.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@openenthrium/oe-runtime",
|
|
3
|
-
"version": "1.7.
|
|
3
|
+
"version": "1.7.5",
|
|
4
4
|
"description": "OE Runtime - run AI agents against enterprise data sources. One binary, one YAML agent, one config file.",
|
|
5
5
|
"homepage": "https://www.openenthrium.com/runtime.html",
|
|
6
6
|
"repository": {
|