feat: add provider Abliteration#67948
Conversation
openclaw-barnacle
bot
added
docs
Greptile SummaryAdds a new bundled Anthropic-compatible provider plugin for abliteration.ai, following the same pattern as other simple provider plugins (Venice, Arcee). The extension includes the plugin entry, static model catalog, onboarding helpers, tests, and full documentation coverage across all relevant docs surfaces. Confidence Score: 5/5Safe to merge — all remaining findings are P2 style/data suggestions that don't block functionality. The implementation closely follows existing provider patterns (Venice, Arcee). Both inline comments are P2: a minor labeler.yml alphabetical ordering issue and a question about whether the cost values reflect real pricing. No logic errors, missing wiring, or boundary violations were found. extensions/abliteration/models.ts — verify the Prompt To Fix All With AIThis is a comment left during a code review.
Path: .github/labeler.yml
Line: 260-263
Comment:
**Labeler entry out of alphabetical order**
The `abliteration` entry is inserted after `acpx` but alphabetically `abl` comes before `acp`, so it should precede the `acpx` block. All other entries in this section appear to be sorted alphabetically.
```suggestion
"extensions: abliteration":
- changed-files:
- any-glob-to-any-file:
- "extensions/abliteration/**"
"extensions: acpx":
```
How can I resolve this? If you propose a fix, please make it concise.
---
This is a comment left during a code review.
Path: extensions/abliteration/models.ts
Line: 7-12
Comment:
**Cost values look like round-integer placeholders**
Other Anthropic-compatible providers in this repo use precise decimal pricing (e.g., Arcee: `input: 0.045`, `output: 0.15`). The values `input: 5, output: 5` are unusually high integers — if these are meant to represent $5/million tokens they should reflect the actual abliteration.ai pricing schedule; if they're stubs, they'll produce inflated cost estimates for users.
How can I resolve this? If you propose a fix, please make it concise.Reviews (1): Last reviewed commit: "Abliteration: add provider plugin" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5c84347344
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7080b9d27b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce2baf3be0
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
abliteration-ai
changed the title
abliteration-ai
force-pushed
the
abliteration-provider
branch
from
52c9718 to
6cc27d8
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6cc27d8525
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Screenshot of it working
|
abliteration-ai
force-pushed
the
abliteration-provider
branch
from
6cc27d8 to
2bc13d0
Compare
|
Hi @obviyus, I have seen you commit new models/providers before, so I'm reaching out in hopes of reviewing/merging ours. |
1 participant
Summary
Describe the problem and fix in 2–5 bullets:
If this PR fixes a plugin beta-release blocker, title it
fix(<plugin-id>): beta blocker - <summary>and link the matchingBeta blocker: <plugin-name> - <summary>issue labeledbeta-blocker. Contributors cannot label PRs, so the title is the PR-side signal for maintainers and automation.Change Type (select all)
Scope (select all touched areas)
Linked Issue/PR
Root Cause (if applicable)
For bug fixes or regressions, explain why this happened, not just what changed. Otherwise write
N/A. If the cause is unclear, writeUnknown.Regression Test Plan (if applicable)
For bug fixes or regressions, name the smallest reliable test coverage that should catch this. Otherwise write
N/A.User-visible / Behavior Changes
List user-visible changes (including defaults/config).
If none, write
None.Added provider
Diagram (if applicable)
For UI changes or non-trivial logic flows, include a small ASCII diagram reviewers can scan quickly. Otherwise write
N/A.Security Impact (required)
Yes/No) NoYes/No) NoYes/No) NoYes/No) NoYes/No) NoYes, explain risk + mitigation:Repro + Verification
Environment
Steps
Expected
Actual
Evidence
Attach at least one:
Human Verification (required)
What you personally verified (not just CI), and how:
Review Conversations
If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.
Compatibility / Migration
Yes/No) YesYes/No) YesYes/No) NoRisks and Mitigations
List only real risks for this PR. Add/remove entries as needed. If none, write
None.