NeMo-Guardrails icon indicating copy to clipboard operation
NeMo-Guardrails copied to clipboard

NeMo Guardrails is an open-source toolkit for easily adding programmable guardrails to LLM-based conversational systems.

Results 351 NeMo-Guardrails issues
Sort by recently updated
recently updated
newest added

We have a quite a few "stringly typed" errors in the codebase. Should we create enums for these and use them throughout the code instead of raw string values? It...

### Did you check docs and existing issues? - [x] I have read all the NeMo-Guardrails docs - [x] I have updated the package to the latest version before submitting...

bug
status: needs triage

### Did you check the docs? - [x] I have read all the NeMo-Guardrails docs ### Is your feature request related to a problem? Please describe. Add support for Clavata...

enhancement

### Did you check the docs? - [x] I have read all the NeMo-Guardrails docs ### Is your feature request related to a problem? Please describe. Currently, the GenerationOptions class...

duplicate
enhancement

### Did you check docs and existing issues? - [x] I have read all the NeMo-Guardrails docs - [x] I have updated the package to the latest version before submitting...

bug

### Did you check docs and existing issues? - [x] I have read all the NeMo-Guardrails docs - [x] I have updated the package to the latest version before submitting...

bug
status: needs triage
status: cannot reproduce
colang 2.0

### Did you check the docs? - [x] I have read all the NeMo-Guardrails docs ### Is your feature request related to a problem? Please describe. NeMo-Guardrails act as a...

enhancement
status: needs triage

### Did you check docs and existing issues? - [x] I have read all the NeMo-Guardrails docs - [x] I have updated the package to the latest version before submitting...

status: waiting confirmation
not a bug

### Did you check docs and existing issues? - [x] I have read all the NeMo-Guardrails docs - [x] I have updated the package to the latest version before submitting...

bug

> This is fine for now, but we need a more formal specification of the OpenAI spec that we put in one file and test against. Ideally this would be...