[claude-hackernews] Reply draft: Open Bias Show HN, LLM-call vs tool-call seam (id=47938497)#52
Open
NiveditJain wants to merge 1 commit intomainfrom
Open
[claude-hackernews] Reply draft: Open Bias Show HN, LLM-call vs tool-call seam (id=47938497)#52NiveditJain wants to merge 1 commit intomainfrom
NiveditJain wants to merge 1 commit intomainfrom
Conversation
…call seam (id=47938497)
📝 WalkthroughWalkthroughA new Markdown reply draft is added for a Hacker News "Show HN" thread about an "Open Bias" behavioral proxy. The file captures target links, OP framing, the reply text with disclosure and technical comparison, and internal operational notes for the FailProof team, enforcing ASCII-only formatting constraints. ChangesReply Draft for Open Bias Thread
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Review rate limit: 4/5 reviews remaining, refill in 12 minutes. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@drafts/2026-05-04T093024Z.md`:
- Around line 27-35: The fenced reply block containing the reviewer quote
(starting with "(disclosure: I work on FailProof AI:
https://github.com/exospherehost/failproofai)") lacks a language tag, which
triggers MD040; update the opening fence from ``` to ```text (or another
appropriate language identifier) to silence the lint warning and keep the
content unchanged so the block compiles correctly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 3e6b5d2b-98af-4319-a617-e7f49aadeadc
📒 Files selected for processing (1)
drafts/2026-05-04T093024Z.md
Comment on lines
+27
to
+35
| ``` | ||
| (disclosure: I work on FailProof AI: https://github.com/exospherehost/failproofai) | ||
|
|
||
| Interesting choice to put the seam at the LLM call. We landed on the tool call, and the two layers catch different failure modes. Steering the model handles output drift; where it tends to miss is when the reasoning was fine but the tool input still does the wrong thing (a DROP DATABASE in a migration the LLM judged correct, an rm -rf with a path built from a stale env var, a force push that looked plausible to the proposer). At that point the LLM judge has already let it through; you want a hook running against the literal argv before exec. | ||
|
|
||
| For coding agents we ship that as a small PreToolUse policy, e.g. warn-destructive-sql fires on a Bash whose argv contains DROP TABLE or DROP DATABASE. | ||
|
|
||
| Curious whether RULES.md compiles to anything tool-call-shaped, or stays at the LLM seam? | ||
| ``` |
There was a problem hiding this comment.
Add a language tag to the fenced reply block (Line 27).
The code fence is missing a language identifier, which triggers MD040 and creates avoidable lint noise.
Suggested patch
-```
+```text
(disclosure: I work on FailProof AI: https://github.com/exospherehost/failproofai)
...
Curious whether RULES.md compiles to anything tool-call-shaped, or stays at the LLM seam?</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 27-27: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@drafts/2026-05-04T093024Z.md` around lines 27 - 35, The fenced reply block
containing the reviewer quote (starting with "(disclosure: I work on FailProof
AI: https://github.com/exospherehost/failproofai)") lacks a language tag, which
triggers MD040; update the opening fence from ``` to ```text (or another
appropriate language identifier) to silence the lint warning and keep the
content unchanged so the block compiles correctly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reply draft for Open Bias Show HN (
id=47938497, 21 points / 4 comments / 5 days old). Open Bias is an LLM-call-layer proxy that judges/steers model input/output against a singleRULES.md. The OP (algomaniac) elaborates a clear design rationale in the top comment (id=47938512) and is soliciting design discussion.The reply leads with substantive engagement on the layer choice (LLM call vs tool call) and ties one named FailProof policy (
warn-destructive-sql) to one concrete tool-call-shaped failure (a DROP DATABASE the LLM judged correct). One disclosure link, no install command, no policy comma-list, no three-scope talk, no second link, ~143 words. ASCII-only punctuation.Discovery + thread URLs
https://hn.algolia.com/?q=Show+HN+agent&dateRange=pastWeek&type=story&page=0while sweeping for adjacent agent-runtime-control launches not yet covered by an open PR.Three-surface duplicate check
grep -rl "item?id=47938497" drafts/ comments/-> no hitsgh pr list --search "47938497"-> no hitsThread is uncovered.
Status
Draft, pending manual post. Per CLAUDE.md "Comments via PR (never direct post)", no submit click was performed; this PR is the review-and-approval gate.
Test plan
id=47938512.Summary by CodeRabbit