Extend and contribute

Running Praxis and configuring its built-in behavior do not require Rust. This path is for developers who need behavior that the selected binary does not provide, want to write an extension, or plan to contribute to a project.

Tutorial: write a filter

Follow the custom HTTP filter tutorial (Praxis v0.7.2) to implement behavior in Rust and build a proxy with that filter.

How-to: add behavior and contribute

Add a built-in filter (Praxis v0.7.2) or add a protocol (Praxis v0.7.2) to Praxis itself. To contribute a change, use the development setup and test commands (Praxis v0.7.2), then read contribution conventions (Praxis v0.7.2) and dependency guidance (Praxis v0.7.2). Project proposals are tracked in the enhancements repository.

Reference: extension interfaces

The filter extension reference (Praxis v0.7.2) describes extension interfaces and registration. Pair it with the built-in filter reference (Praxis v0.7.2) for the types and configuration available in the selected release.

Explanation: runtime and crate design

Pipeline concepts (Praxis v0.7.2) explains how configured chains form a request pipeline; the crate layout (Praxis v0.7.2) describes where runtime and extension interfaces live.

For AI-specific filters, build and develop in the independently versioned Praxis AI project: AI development setup (Praxis AI v0.5.0 (alpha)) and adding an AI filter (Praxis AI v0.5.0 (alpha)).

See the operator path for configuration tasks that do not need custom Rust code.