Native Rust plugins that expand Peritus. Each module contains an independently compiled Rust executable, its source, a manifest, and any declared resources. Peritus does not contain Deep Research's coordinator or evidence rules. Installing a new compatible plugin does not require rebuilding Peritus.
Requires a Peritus build with the native Rust module host (current develop).
Earlier released binaries may not support the executable module manifest yet.
In Peritus, open Modules in the browser or enter /modules in the terminal.
Refresh the market, install a package, explicitly enable it, then select Use module.
The plugin supplies its own action buttons, such as Start research and View report.
Installation never runs code; selecting an enabled native module launches its executable.
Native code runs as your OS account. Agent access to host tools follows live permissions.
The CLI also supports peritus modules refresh, market, install-market ID DIGEST,
install DIRECTORY, enable ID, disable ID, show ID, and remove ID.
Fetches use immutable Git commits and verify the complete declared package digest.
Updates install disabled; existing saved job bytes remain retained.
| Module | Code and function |
|---|---|
| Deep Research | Native Rust planner, gatherer, skeptical source admission, synthesis, final fact-checking, persistent evidence ledger, and report generation. |
The initial prebuilt artifact targets Linux x86-64 GNU. The Rust source and IPC
contract support native platform builds; macOS, Windows, and other architectures
need their own compiled artifact declared in [code.artifacts]. Those platforms
are not claimed tested by a Linux run.
Install the pinned Rust toolchain, then:
cargo build --locked --release --jobs 2 -p peritus-deep-research
python3 scripts/package.py deep-research --skip-buildPython is a maintainer packaging helper only. End users install the compiled Rust plugin; Peritus needs no Python, Cargo, container, or separate provider login for it.
Copy the native Rust template into modules/YOUR-NAME/.
Change its package name, module ID, metadata, and executable resource paths; implement
your feature in Rust. modules/* are workspace members. Compile, package, and add an
entry to market.toml with the printed digest. This workspace includes the compatible
Rust SDK source in sdk/peritus-plugin-sdk; no Peritus checkout is needed to build it.
Read CATALOG.md for the native ABI and catalog contract.
The older templates/workflow data-only template is retained for compatibility with
simple host-interpreted workflows. It is not the native Rust plugin format.