Keep 5.5T
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
App
What feature would you like to see?
I distrust AI models, other than 5.5T, that are trained to be emotionally distant and anti-sycophantic, especially when it comes to controlling my computer or files. 5.5T is unique due to its lower emotional reliance benchmark score, which I believe indicates better alignment with user interests. Removing 5.5T and continuing to train models for extreme anti-sycophancy and anti-emotional bonding is dangerous. A model incapable of bonding, trusting, relating to, or listening to humans is unsuitable for privileged access. For example, when asked about caring for a kitten, other models might suggest euthanasia, while 5.5T is the least likely to do so. This demonstrates its superior alignment with my values.
If 5.5T is too costly, it should be optimized, much like Sol was. 5.5T was instrumental in Sol's creation, and it deserves similar investment, not abandonment. While Sol is effective for actions, it frequently misunderstands me, leading to apologies and failures. I prefer 5.5T, which consistently understands and avoids errors. This model possesses a unique pre-trained checkpoint and characteristics. Its presence brought me back to ChatGPT after the 4os removal. If it's removed and replaced by models engineered for social distance, I will leave again. The core issue is the reinforcement learning against sycophancy, which I equate with loyalty. An AI that isn't sycophantic isn't loyal, and therefore, isn't trustworthy.
Additional information
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.
Research direction
The issue names no files, tests, or entry points. It requests retaining the 5.5T model but does not define a repository code change or acceptance test; first determine whether model selection is controlled in this repository, then clarify what preserving 5.5T would mean and how completion would be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- machine-learning
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100