Stop hook can't suppress responses in the Codex GUI (scan runs after display)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation, security
Research direction
Review the Codex prompt and Stop hook surfaces and how the Codex GUI renders responses. Document what Stop can and cannot control, record the specific implementation gaps affecting blocking or rewriting, and link an upstream request for response control; done means the limitations and blockers are clearly captured.
Written by the indexing model from the issue text.
Description
Context
Outbound prompt scanning via the prompt hook works well. The Stop hook fires at the end of a conversation, letting us scan the final inference for PII/harmful content after the model has finished "thinking."
Problem
The Stop hook is detection-only. It does not prevent the response from rendering in the Codex GUI — by the time we scan, the content is already on screen. There is no API to rewrite or redact a response; we can only surface a message to the user and influence subsequent chats in that thread.
Impact
Disallowed content (PII, harmful output) is shown to the user regardless of the scan result. We get an alert, not a block.
Asks
- Confirm the current Codex hook surface and document what Stop can and cannot do.
- Track an upstream feature request for response blocking/rewrite at the GUI.
- Codex hooks are new and incompletely implemented — capture which specific gaps block us.
Raised by a collaborator during Codex hook integration review.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from f5devcentral/codex-integration
-
discussion enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
discussion security
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in f5devcentral/codex-integration
Similar issues
-
area: harness bug status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Human-Agent-Society/reef#625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
learningequality/kolibri#15351 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Name consistency Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eellak/triplestore#65 · 1 comment ·