OWASP / OWASP/OpenCRE

Later: filter chat RAG by saved standards selection

Open
#1,085 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement not ready for development P3 untriaged
Dominant language
Python
Stars
180
Forks
137
Avg merge
3d 23h
Merged PRs (30d)
21

Description

Parent: #1079 · Not a November blocker · Project: https://github.com/orgs/OWASP/projects/60

What

Product choice, tracked so it does not get silently skipped or silently done.

Chat (/rest/v1/completion) already requires login (spend control). Retrieval is not limited by user_resource_selection. A user who filtered the site to ASVS+CWE can still get answers citing NIST, cheat sheets, etc.

Decide then implement

  • Decide: should chat respect the profile view, always use the full corpus, or offer a toggle?
  • If yes: pass selected standard names into PromptHandler retrieval and drop/hide out-of-view citations
  • Empty selection = current behaviour (full corpus)
  • Do not weaken login on /completion (Nest Agent service contract is #1074, unrelated)

Why later

Roadmap “user profiles with persistent standards filter” is the site view. Chat corpus filtering is a separate UX (users often want the chatbot to see everything). Ship CRE/search/explorer first.

Related

  • application/web/web_main.py chat_cre
  • Nest cited-ask: #1074

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with application/web/web_main.py and the chat_cre entry point for /rest/v1/completion, then trace how PromptHandler performs retrieval. Resolve whether chat should use the saved standards selection, the full corpus, or a toggle before implementing; preserve full-corpus behavior for an empty selection and keep the existing login requirement.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.