Plugins for your workflow

Add one useful behavior to Torana, then make it yours. These are the sources for twelve maintained plugin examples: routing, telemetry, tool policy, checks and optional context experiments.

Get Torana running · Browse plugin listings · Write a plugin

Choose a plugin

Plugin	Use it to…
decision_router	Explore adaptive model choices in shadow mode, without changing your route
pii	Use a local model for contextual checks of tool output
pii_guard	Block recognizable PII and secrets without a model
usage_logger	See usage without saving prompts
tool_governor	Choose the tools your model sees
otel	Add request metrics
schema_translator	Adapt map-shaped tool schemas
intent	Carry the reason for a tool call
keyword_compactor	Trim repeatable tool output without another model
compactor	Summarize selected historical tool results
cache_tier_selector	Choose a cache lifetime for a conversation
cache_warmer	Keep one conversation's cache warm for a bounded gap

Already running Ollama or another OpenAI-compatible local model? Try pii as an extra contextual check and bind its scanner to that endpoint. Test both sensitive and harmless examples: it can catch some accidental exposures, but a local endpoint alone does not make detection reliable. If you do not have a local model ready, start with usage_logger for content-free usage records or the deterministic pii_guard for recognizable secret shapes. For broader protection, run both and place pii_guard first: obvious matches are withheld without a model call, then pii scans the remaining tool output, including failed results.

Every guide includes settings, exact permissions, required resource bindings, and a way to check the result. Start Torana, then install your choice by name with torana on PATH (use ./torana for a source build). No Git or Go is needed to install these published bundles.

Name-based installs require Torana 0.1.1 or newer. Already on 0.1.0? Re-run the Torana installer to upgrade.

torana plugin install pii

Or, without a local model, choose one:

torana plugin install usage_logger
torana plugin install pii_guard

Installation downloads and verifies a release bundle. It never approves or enables a plugin. Source builds remain available through repository URLs or local directories and require the plugin’s toolchain. Open Torana's local control plane and select the plugin you installed. For pii, configure the required scanner binding before reviewing its permissions and model-call limits. pii_guard makes no model or network calls; review its requested tool-result and state permissions before enabling it. Follow the PII guide or the deterministic guard's safe walkthrough. For usage logging, follow the usage logger guide.

Prefer terminal or agent automation? Each plugin guide covers its configuration and lifecycle commands. Other plugins may need their own settings or resource bindings; each listing links to its owning guide.

Combine deliberately

Put tool_governor before intent and schema_translator. Put optional intent before a compactor. Run only one of keyword_compactor or compactor; the host enforces their conflict. Individual guides explain data flow and other ordering considerations.

Torana runs locally, but plugins with approved model or network resources may send data to those destinations. pii_guard uses neither. The model-backed PII scanner and model compactor use the model-service bindings you choose, which may be local or remote.

Share your own

Your plugin can live in its own repository. You do not need a website listing to install it. Go plugins can use Git URLs; Rust projects are cloned and reviewed locally before building, including their dependencies and build scripts.

Use the Go/Rust SDK, then request a website listing if you would like other users to find it. Contributions to this maintained example set are welcome; see CONTRIBUTING.md.

Build and test this repository

./scripts/test.sh
./scripts/build.sh usage_logger

Use a sibling SDK checkout or TORANA_SDK_DIR for coordinated local development. Release builds use the exact SDK pin in SDK_REF and each module. Current maintained sources target ABI v1, contract revision 1. Build output stays in dist/, not source control.

The auth reference is not a listed plugin

plugins/auth is a thirteenth, reference-only capability example. It is excluded from the public listing and is not an authentication boundary: explicit verifier rejection blocks, but unavailable verification and its failure_mode: pass policy can allow traffic. Do not deploy it as access control. The reference remains in the executable release inventory. Its README states what it does today, and why none of it is protection.

Evidence

PII scan memory measurements retain the measured limits of that experiment. Full proxy/plugin-chain CPU and memory results remain public in Edge.