smithery/quantdiy

quanux-control-plane

Python Control Plane (Client Library for C++ Runtime)

Installation

$ npx skills add smithery/quantdiy --skill quanux-control-plane

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/quantdiy.

npx skills add smithery/quantdiy

Browse all from smithery/quantdiy

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,170 B
  • docs SUMMARY.md 81 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Python Control Plane (quanux.runtime)

Overview

The Control Plane facilitates the "Remote Control" of the C++ organism from Python.

  • Architecture: It is a Client, not a Wrapper. It sends NATS messages to the quanux_supervisor.
  • Philosophy: "Python Agility, C++ Speed". The UI logic remains in flexible Python, while the core runs in native C++.

1. Usage

Agents should use this library to verify system state or command new strategies.

from server.control import RuntimeClient

async with RuntimeClient() as client:
    # 1. Command (Act)
    # Spawns a C++ strategy in the Execution Node
    await client.spawn_strategy("momentum_v1", "ESH5")

    # 2. Telemetry (Listen)
    async for log in client.subscribe_logs():
        print(log)

2. Core Concepts

  • Decoupling: The Python process (e.g. streamlit) never loads libquanux.so. If the Python UI crashes, the C++ trading engine relies on its own Supervisor and keeps running.
  • NATS as API: All communication happens over sys.cmd.* text streams.