The planned first-run flow is still private
Riposte is intended to read the toolchain on your machine and use only the model provider you configure. Public installation instructions will appear after signed artifacts and the first-run experience are ready.
Planned launch command
ripostePreview only · no public binary is availableQuestions about the product design
How is this different from a coding agent?
Security work is evidence driven: you scope, gather, corroborate, and hand off proof. Riposte's planned tools, memory, and output artifacts are designed around that shape.
Where is data intended to go?
The TUI is designed to run locally. Model calls would go only to the provider endpoint an operator configures, with context labelled and minimized first. Exact tested profiles will be published with a release.
Can it act without asking?
The design separates passive work from actions that touch a target or change state. Those effects sit behind readable scope and explicit approval policy. This is a design commitment, not a public implementation guarantee yet.
Does it replace existing security tools?
No. Riposte is being designed to drive tools the operator already trusts and to support additional typed tool definitions.
Is there a free tier?
No pricing or public tier structure has been announced.
Is the source available?
The implementation is private and no public source or binary distribution is currently offered.