TReg Zero-Config Tool Registry & Schema Bridge

@superdesigndev/treg · v1.0.5

A zero-config distributed tool registry and schema gateway for DeepSeek Harness. Features automated RPC binding, JSON Schema reflection, namespace conflict resolution, and circuit breakers.

Tool-RegistryMicroservicesSchema-ReflectionCircuit-Breaker
GitHub Stars
23 K+
+12.4% this month
Monthly Downloads
91 K+
Monthly registry pulls
Reach Score
97.7/ 100
Top Tier Ecosystem
Runtime
Cordis v3+
Node 18+ / Bun / Deno

Installation & Integration

CLI one-click launch, package managers, and Cordis integration

bash
manager:
$ pnpm add @superdesigndev/treg

Architecture

TReg Tool Registry turns heterogeneous microservice fleets into typed agent tools with zero manual boilerplate. In enterprise architectures, engineering teams build services across diverse languages; manually maintaining JSON Schema definitions per endpoint is fragile and unscalable. This plugin implements automated service reflection atop Cordis. Remote gRPC, REST, and GraphQL endpoints announce their signatures to the central registry. TReg compiles parameter signatures into compliant tool schemas, applies namespace routing, and guards downstream services with adaptive rate limiting and circuit breakers.

Architectural Principles & Constraints

01
Strict Type Isolation

Guaranteed by TypeScript compile-time contracts, inter-plugin event bus calls enjoy zero-drift safety.

02
Sub-Millisecond Hot Reload

Supports dynamic runtime mounting and graceful unloading without restarting the primary host process.

03
Deterministic State Machine

Embeds multi-phase execution lifecycle guards, preventing context loss during long-horizon reasoning.

04
Zero Native Build Dependencies

Designed for lightweight cross-platform environments, booting instantly across Node.js, Bun, and Deno.

Core Features

01
Zero-Config Schema Reflection: Compiles TypeScript interfaces or proto files into tool schemas
02
Polyglot Microservice Support: Effortlessly bridges Go, Java, Python, and Rust backends
03
Tool-Level Circuit Breakers: Configures isolated rate limits and concurrency caps per method
04
Multi-Environment Routing: Dynamically routes invocations to local, staging, or production nodes

Core Workflow

01

Endpoint Self-Registration

Microservices announce exported function signatures and auth headers via heartbeat.

02

Schema Reflection & Compile

Reflects typed parameter schemas into compliant LLM tool calling definitions.

03

Namespace Arbitration

Applies team and service prefixes to resolve collisions across sprawling fleets.

04

Proxy Dispatch & Circuit Breaker

Proxies RPC calls with retry policies, tripping circuit breakers on upstream failures.

Configuration Parameters Reference (YAML / JSON)

ParameterTypeDefaultDescription
registryPortnumber9090Tool registry listening port
defaultQPSLimitnumber20Default QPS cap per tool method
strictTypeCheckbooleantrueValidate arguments strictly with Zod

Use Cases

Enterprise Production Agent

Relies on microkernel lifecycle guards and fault-tolerant state machines for continuous reliability.

SWE-bench Benchmark Evaluation

Native integration with SWE-bench workflows, automatically capturing diffs and verification metrics.

Autonomous Code Refactoring

Separates reasoning from tool actions to independently locate and refactor multi-file codebases.

Cross-Tool Workflow Automation

Safely orchestrates events across sandboxes to seamlessly link enterprise developer tooling.

Best Practices

01
Sandbox Permission Guard

Strictly isolate sub-process calls and network scope; deploy within Docker containers in production.

02
Exponential Backoff Retries

Configure adaptive exponential retries with strict timeouts to mitigate upstream model rate limits.

03
Session State Checkpointing

Persist state machine snapshots to survive hardware interruptions and resume instantly without loss.

04
Full Trajectory Audit Logs

Enable full trace logging, aggregating reasoning thought streams and tool I/O into your observability hub.

FAQ

Q1:How to handle timeouts in long-running autonomous tasks?

Increase the timeout parameter inside your YAML configuration and dispatch periodic heartbeat signals across the Cordis event bus. For long-running tool execution and model reasoning, configure persistent session snapshotting so suspended tasks can safely resume their exact context after interruptions, preventing the kernel from recycling active agent sessions prematurely.

Q2:How to capture and stream the model reasoning thought process?

The harness runtime natively provides end-to-end streaming hooks while its state machine automatically intercepts and strips <think> reasoning tags from model responses. Subscribe directly to the onThink event listener to consume live reasoning token streams in real-time, delivering typewriter animation to the user interface while persisting full trajectories for audit compliance.

Q3:How to resolve dependency conflicts across multiple plugins?

Cordis microkernel uses directed acyclic graph topological sorting to dynamically resolve plugin dependencies. When shared services or runtime versions conflict, assign distinct isolated namespaces at the application entrypoint. Leveraging context injection alongside lazy activation ensures dependencies load strictly on-demand when tools are triggered, maintaining system stability and preventing memory bloat.

Q4:How to enforce permissions and sandbox isolation in production?

Combine isolated container sandboxing with fine-grained capability checks to prevent plugins from accessing sensitive files or unauthorized external networks. Enforce explicit runtime system call whitelisting through the microkernel, executing all third-party tool scripts inside isolated ephemeral containers to block arbitrary code execution and eliminate security privilege escalation risks entirely.

Recommended Ecosystem Plugins

Explore related Cordis extensions designed to work synergistically