RAIL-Suite/RAIL: Remote Agent Invocation Layer

One line of code to make any application AI-controllable

RAIL is a universal bridge that connects any application (C#, C++, Python, Node.js) to any LLM (GPT, Claude, Gemini). Instead of rewriting your application, you add one line of code and the AI can call your methods directly.

The Brain – Main application that users interact with.

• WPF desktop application (.NET 9)
• Connects to LLMs (Gemini, OpenAI, Anthropic, Claude)
• ReAct agent loop for multi-step reasoning
• Hosts the Named Pipe server for client connections
• Manages assets (Chips) and tool routing

Key files:

• Services/Host/HostService.cs – Named Pipe server
• Services/LLMService.cs – LLM API integration
• Services/ReAct/ReActOrchestrator.cs – Agent loop

The Bridge – Native DLL that enables cross-language communication.

• Compiled with Native AOT for C-ABI compatibility
• Exposes functions callable from any language:
  • RAIL_Ignite() – Connect to host
• Uses Named Pipes for IPC

Target: Python, C++, Node.js, Rust, Go

The .NET SDK – Client library for C# applications.

• .NET Standard 2.0 (compatible with .NET Framework 4.6.1+)
• Simple API: RailEngine.Ignite(this)
• Auto-discovers methods via reflection
• Loads RailBridge.dll for communication

Usage:

// In App.xaml.cs
RailEngine.Ignite(this);

The Toolkit – Assembly scanning and manifest generation.

Contains:

• RuntimeRegistry – Detect .NET / Native binaries
• AssemblyScanner – Extract methods from DLLs
• CompositeManifest – Multi-module manifest format
• DependencyAnalyzer – Analyze project dependencies
• SolutionScanner – Scan entire .sln solutions

Used by: RailStudio, RailOrchestrator

The C++ SDK – Enable C++ applications to connect.

• CMake-based build system
• Loads RailBridge.dll via LoadLibrary
• Callback-based command execution
• Supports both x64 and x86 builds

Build:

build_x64.bat   # 64-bit
build_x86.bat   # 32-bit (legacy apps)

Usage:

Rail::ignite("MyApp", manifestJson, onCommand);

The Python SDK – Enable Python scripts to connect.

• Uses ctypes to load RailBridge.dll
• Decorator-based method registration
• Simple API matching other SDKs

Usage:

from rail import RailEngine

engine = RailEngine()
engine.ignite([MyService()])

The Node.js SDK – Enable TypeScript/JavaScript apps to connect.

• Uses ffi-napi for native bridge access
• TypeScript types included
• Promise-based API

Usage:

import 💬 from 'rail-sdk';
engine.ignite([new MyService()]);

The Visual Tool – Scan and analyze applications.

• EXE/DLL to analyzer
• Auto-generates rail.manifest.json
• Visualizes dependencies
• Solution-wide scanning

Use case: Preparing legacy apps for Rail integration

Example applications showing SDK integration.

Manifest Here you can find Manifest folder with all the “rail.manifest.json” already created for this example application

When converting your application to be AI-controllable, here’s exactly what you need:

When you add RailSDK.Universal, the native bridge is automatically copied to your output:

📁 bin/Debug/net8.0/
├── YourApp.exe
├── RailSDK.Universal.dll   ← You add this reference
├── RailBridge.dll          ← Copied automatically!
└── rail.manifest.json      ← You create this

How to add:

<PackageReference Include="RailSDK.Universal" Version="2.0.0" />

C++ has two integration modes depending on your codebase:

For new applications or codebases that support C++17:

// Register your classes with RTTR macros
RTTR_REGISTRATION ⚡

// SDK auto-discovers methods
rail::RegisterInstance("OrderManager", &myManager);
rail::Ignite("MyApp");

Files needed:

📁 YourApp/
├── YourApp.exe
├── rail_sdk.dll            ← C++ wrapper (includes RTTR)
├── RailBridge.dll          ← Native IPC bridge
└── rail.manifest.json      ← Auto-generated

For legacy applications that can’t use C++17 or RTTR (e.g., games, old codebases):

#define RAIL_NO_RTTR  // Disable RTTR

// Define your own command router
std::string MyDispatcher(const std::string& json) {
    if (json.find("MovePlayer") != std::string::npos) {
        MovePlayer();
        return "{\"result\": \"success\"}";
    }
    return "{\"error\": \"unknown\"}";
}

// Register and connect
rail::SetCustomDispatcher(MyDispatcher);
rail::Ignite("MyLegacyApp", "1.0", customManifest);

Files needed:

📁 YourApp/
├── YourApp.exe
├── rail_sdk.dll            ← C++ wrapper (no RTTR)
├── RailBridge.dll          ← Native IPC bridge
└── rail.manifest.json      ← You write this manually

Real Examples: Notepad++ and Doom were integrated using Option B (Custom Dispatcher) because their codebases couldn’t support RTTR.

📁 YourProject/
├── main.py (or index.ts)
├── RailBridge.dll          ← Copy manually
└── rail.manifest.json      ← You create this

Install the wrapper package that handles ctypes/ffi calls for you.

┌─────────────────────────────────────────────────────────────┐
│                    RailOrchestrator                       │
│                    (Main AI Application)                    │
│                                                             │
│  ┌─────────────┐    ┌─────────────┐    ┌───────────────┐   │
│  │  LLM APIs   │    │ HostService │    │ AssetService  │   │
│  │  (Gemini,   │    │ (Named Pipe │    │ (Chip/Manifest│   │
│  │   OpenAI)   │    │   Server)   │    │   Discovery)  │   │
│  └──────┬──────┘    └──────┬──────┘    └───────────────┘   │
└─────────┼──────────────────┼────────────────────────────────┘
          │                  │
          │         Named Pipe: "RailHost"
          │                  │
    ┌─────┴──────────────────┴─────────────────────┐
    │               RailBridge.Native            │
    │            (C-ABI Native DLL)                │
    └──────────────────┬───────────────────────────┘
                       │
       ┌───────────────┼───────────────┐
       │               │               │
┌──────▼──────┐ ┌──────▼──────┐ ┌──────▼──────┐
│ RailSDK   │ │ RailSDK   │ │ RailSDK   │
│ .Universal  │ │ -Cpp        │ │ -Python     │
│ (C# Apps)   │ │ (C++ Apps)  │ │ (Python)    │
└──────┬──────┘ └──────┬──────┘ └──────┬──────┘
       │               │               │
┌──────▼──────┐ ┌──────▼──────┐ ┌──────▼──────┐
│  Your C#   │ │  Your C++  │ │ Your Python │
│    App     │ │    App     │ │   Script    │
└─────────────┘ └─────────────┘ └─────────────┘

RailOrchestrator
    └── uses → RailSDK (RailFactory.Core) for manifest parsing
    
RailSDK.Universal
    └── loads → RailBridge.Native (DLL)
    
RailSDK-Cpp / RailSDK-Python / RailSDK-Node
    └── load → RailBridge.Native (DLL)

RailStudio
    └── uses → RailSDK (RailFactory.Core) for scanning

// 1. Create your service
public class CustomerService
{
    public Customer GetCustomer(int id) => Database.Find(id);
    public void CreateCustomer(string name, string email) { ... }
}

// 2. Add one line in App.xaml.cs
protected override void OnStartup(StartupEventArgs e)
{
    base.OnStartup(e);
    RailEngine.Ignite(this);
}

// 3. Create rail.manifest.json (or use RailStudio)

// Define callback
const char* OnCommand(const char* json) {
    auto cmd = ParseJson(json);
    if (cmd.method == "MoveMachine") {
        Machine::Move(cmd.args["x"], cmd.args["y"]);
        return R"({"result": "OK"})";
    }
    return R"({"error": "Unknown"})";
}

// Connect
rail::ignite("CNCController", manifest, OnCommand);

class DataProcessor:
    def analyze_data(self, file_path: str) -> dict:
        return {"rows": 1000, "status": "processed"}

engine = RailEngine()
engine.ignite([DataProcessor()])
engine.wait()

With apps connected, ask in natural language:

"Create a customer named John Smith with email john@example.com"
→ AI calls CustomerService.CreateCustomer("John Smith", "john@example.com")

"Move the machine to position X=100, Y=200"
→ AI calls CNCController.MoveMachine(100, 200)

1. Run RailOrchestrator – The main AI interface
2. Connect your app – Add SDK and call Ignite()
3. Ask AI – Natural language commands execute your code

RAIL Protocol – Bridging Legacy Applications and AI