Expand description
§Cortex SDK
The official Rust SDK for Cortex’s trusted native plugin boundary.
This crate defines the public plugin surface with zero dependency on Cortex internals. The runtime loads trusted native plugins through a stable C-compatible ABI and bridges these traits to its own turn runtime, command surface, and transport layer.
Process-isolated JSON plugins do not need this crate. They are defined
through manifest.toml plus a child-process command. Use cortex-sdk when
you are building a trusted in-process native plugin that exports
cortex_plugin_init.
§Architecture
┌──────────────┐ dlopen ┌──────────────────┐
│ cortex-runtime│ ──────────────▶ │ your plugin.so │
│ (daemon) │ │ cortex-sdk only │
└──────┬───────┘ FFI call └────────┬─────────┘
│ cortex_plugin_init() │
▼ ▼
ToolRegistry ◀─── register ─── MultiToolPlugin
├─ plugin_info()
└─ create_tools()
├─ Tool A
└─ Tool BPlugins are compiled as cdylib shared libraries. The runtime calls
cortex_plugin_init, receives a C-compatible function table, then asks that
table for plugin metadata, tool descriptors, and tool execution results.
Rust trait objects stay inside the plugin; they never cross the
dynamic-library boundary.
The SDK now exposes a runtime-aware execution surface as well:
InvocationContextgives tools stable metadata such as session id, canonical actor, transport/source, and foreground/background scopeToolRuntimelets tools emit progress updates and observer text back to the parent turnToolCapabilitieslets tools declare whether they emit runtime signals and whether they are background-safeAttachmentandToolResult::with_medialet tools return structured image, audio, video, or file outputs without depending on Cortex internals
§Quick Start
Cargo.toml:
[lib]
crate-type = ["cdylib"]
[dependencies]
cortex-sdk = "1.2"
serde_json = "1"src/lib.rs:
use cortex_sdk::prelude::*;
// 1. Define the plugin entry point.
#[derive(Default)]
struct MyPlugin;
impl MultiToolPlugin for MyPlugin {
fn plugin_info(&self) -> PluginInfo {
PluginInfo {
name: "my-plugin".into(),
version: env!("CARGO_PKG_VERSION").into(),
description: "My custom tools for Cortex".into(),
}
}
fn create_tools(&self) -> Vec<Box<dyn Tool>> {
vec![Box::new(WordCountTool)]
}
}
// 2. Implement one or more tools.
struct WordCountTool;
impl Tool for WordCountTool {
fn name(&self) -> &'static str { "word_count" }
fn description(&self) -> &'static str {
"Count words in a text string. Use when the user asks for word \
counts, statistics, or text length metrics."
}
fn input_schema(&self) -> serde_json::Value {
serde_json::json!({
"type": "object",
"properties": {
"text": {
"type": "string",
"description": "The text to count words in"
}
},
"required": ["text"]
})
}
fn execute(&self, input: serde_json::Value) -> Result<ToolResult, ToolError> {
let text = input["text"]
.as_str()
.ok_or_else(|| ToolError::InvalidInput("missing 'text' field".into()))?;
let count = text.split_whitespace().count();
Ok(ToolResult::success(format!("{count} words")))
}
}
// 3. Export the FFI entry point.
cortex_sdk::export_plugin!(MyPlugin);Tools that need runtime context can override
Tool::execute_with_runtime instead of only Tool::execute.
§Build & Install
cargo build --release
cortex plugin install ./my-plugin/If my-plugin/manifest.toml declares [native].library = "lib/libmy_plugin.so"
(or .dylib on macOS), Cortex copies the built library from
target/release/ into the installed plugin’s lib/ directory
automatically when you install from a local folder.
For versioned distribution:
cargo build --release
cortex plugin pack ./my-plugin
cortex plugin install ./my-plugin-v0.1.0-linux-amd64.cpxInstalling or replacing a trusted native shared library still requires a daemon restart so the new code is loaded. Process-isolated plugin manifest changes hot-apply without that restart.
§Plugin Lifecycle
- Load —
dlopenat daemon startup - Create — runtime calls
export_plugin!-generated stable ABI init - Register —
MultiToolPlugin::create_toolsis called once; eachToolis registered in the global tool registry - Execute — the LLM invokes tools by name during turns; the runtime
calls
Tool::executewith JSON parameters - Retain — the library handle is held for the daemon’s lifetime;
Dropruns only at shutdown
§Tool Design Guidelines
name: lowercase with underscores (word_count, notWordCount). Must be unique across all tools in the registry.description: written for the LLM — explain what the tool does, when to use it, and when not to use it. The LLM reads this to decide whether to call the tool.input_schema: a JSON Schema object describing the parameters. The LLM generates JSON matching this schema.execute: receives the LLM-generated JSON. ReturnToolResult::successfor normal output orToolResult::errorfor recoverable errors the LLM should see. ReturnToolErroronly for unrecoverable failures (invalid input, missing deps).- Media output: attach files with
ToolResult::with_media. Cortex delivers attachments through the active transport; plugins should not call channel-specific APIs directly. execute_with_runtime: use this when the tool needs invocation metadata or wants to emit progress / observer updates during execution.timeout_secs: optional per-tool timeout override. IfNone, the global[turn].tool_timeout_secsapplies.
Re-exports§
pub use serde_json;
Modules§
- prelude
- Convenience re-exports for plugin development.
Macros§
- export_
plugin - Generate the stable native ABI entry point for a
MultiToolPlugin.
Structs§
- Attachment
- Stable multimedia attachment DTO exposed to plugins.
- Cortex
Buffer - Native ABI-owned byte buffer.
- Cortex
Host Api - Host table supplied to a native plugin during initialization.
- Cortex
Plugin Api - Function table exported by a native plugin.
- Invocation
Context - Stable runtime metadata exposed to plugin tools during execution.
- Plugin
Info - Plugin metadata returned to the runtime at load time.
- Tool
Capabilities - Declarative hints about how a tool participates in the runtime.
- Tool
Result - Result of a tool execution returned to the LLM.
Enums§
- Execution
Scope - Whether a tool invocation belongs to a user-visible foreground turn or a background maintenance execution.
- Tool
Error - Error from tool execution.
Constants§
- NATIVE_
ABI_ VERSION - Stable native ABI version for trusted in-process plugins.
- SDK_
VERSION - Version of the SDK crate used by native plugin builds.
Traits§
- Multi
Tool Plugin - A plugin that provides multiple tools from a single shared library.
- Tool
- A tool that the LLM can invoke during conversation.
- Tool
Runtime - Runtime bridge presented to tools during execution.
Functions§
- cortex_
buffer_ ⚠free - Free a buffer allocated by this SDK.