Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dynamically infer available shields instead of --disable-safety #110

Open
yanxi0830 opened this issue Nov 8, 2024 · 1 comment · May be fixed by #116
Open

Dynamically infer available shields instead of --disable-safety #110

yanxi0830 opened this issue Nov 8, 2024 · 1 comment · May be fixed by #116
Assignees
@chuenlok
Labels
good first issue Good for newcomers

Comments

@yanxi0830
Copy link
Contributor

🚀 The feature, motivation and pitch

Our agent's client have --disable-safety flag to enable/disable running shields. This is helpful if user do not have shields served on server.

Optimize this flag and dynamically check against available shields for running safety, and use that to determine whether shields should be run.

Alternatives

No response

Additional context

No response
@yanxi0830 yanxi0830 added the good first issue Good for newcomers label Nov 8, 2024
@rabelmervin
Copy link

Hi @yanxi0830 I would like to contribute to this issue could you please assign me ? Any guidance would be appreciated 👍

@chuenlok chuenlok self-assigned this Nov 16, 2024
@chuenlok chuenlok linked a pull request Nov 16, 2024 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chuenlok chuenlok

Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

remove the --disable-safety flag meta-llama/llama-stack-apps
3 participants
@chuenlok @yanxi0830 @rabelmervin