Local AI executor with a CLI, local API server, and web UI.
A TypeScript SDK for building executors that wire together tool sources, secrets, and policies across MCP, OpenAPI, GraphQL, and custom plugins.
QuickJS sandbox runtime for @executor-js/execution . Runs untrusted TypeScript/JavaScript in a WASM-backed interpreter with configurable timeout, memory limit, and stack size — safe enough to execute LLM-
Core primitives for "code mode" — the pattern where an LLM writes TypeScript/JavaScript that calls into a pre-registered set of tools, executed in a sandbox. This package provides the shared type surface ( Tool , SandboxToolInvoker , CodeExecutor ), JSO
Load OpenAPI specifications into an executor. Every operation in the spec becomes an invokable tool with a JSON-Schema input, automatic request building, and optional secret-backed auth.
Sandboxed JavaScript execution for an executor. Hands a tools.<namespace>.<name>(...) proxy into a code sandbox so an agent (or any caller) can run generated TypeScript/JavaScript that invokes the executor's registered tools.
TS-first story/given/when/then helpers for Vitest with Markdown user-story doc generation.
CLI for the executor SDK — schema generation, migrations
TypeScript SDK for the Kortix Executor — one typed client for every connector (Pipedream / MCP / OpenAPI / GraphQL / HTTP). Calls run server-side through the Kortix Executor gateway; no third-party secret ever touches your code.
Universal subprocess executor for plurnk-service's exec scheme — one package exposing the shell + node + python floor plus whichever host interpreters (perl, ruby, php, lua, awk, bc, …) are present.
MCP-bridge runtime executor for plurnk-service's exec scheme — exposes each configured MCP server as its own EXEC tag, its tools called from the body, output contained behind the server's address.
AllexJS lib for a Base SQL Executor
ky-based executor for routar — transport adapter using ky
Axios-based executor for routar — transport adapter using Axios
WebAssembly runtime executor for plurnk-service's exec scheme — in-process sandboxed execution of WAT (text) and wasm (binary) modules.