YuK1 retweeted
AIについては、言っていることがコロコロ変わるエンジニアの方が信頼できるな。
ちょっと前まで「コードは今まで通りちゃんと読んで理解すべき」と言っていた先輩エンジニアたちが、今では「自分では全然読んでない」と言っている。
他にもplanモードをめちゃめちゃ周りに勧めていたエンジニアが、今ではその本人が全然使っていなかったり。
その方が当時書いたClaude Codeについての社内ドキュメントを元に質問したところ、「あ、その記事の考えはもう古いんで、見なかったことにしてください」と返ってきたり。
普通なら、一貫した意見を持っている人の方が圧倒的に信頼できる。
だけどこれだけスピーディーに進化している以上、以前の自分の考えをあっさり捨てているエンジニアの方が、むしろ意見を聞きたいなと思ってしまう。
YuK1 retweeted
🌸SHAZNA ・ゲームオープニングソング決定🌸
switchやPlaystationで遊べるゲーム『センチメンタルグラフティ-Re-』のオープニング曲として、Melty Loveが生まれ変わります!
SHAZNAが1997年にリリースし、88万枚の大ヒットを記録した『Melty Love』が
2027年1月1日(元旦)に新たにレコーディングされた音源にて、デジタルシングルとしてリリース決定!
タイトル
『Melty Love -30th Anniversary ver.-』
Music Videoは同日 13:13にYoutube SHAZNAチャン寝ルにて公開決定!
YuK1 retweeted
\ ✨発売決定✨/
『ロマンシング サガ3 デスティニーユナイテッド』
2027年2月16日(火)発売
宿命に導かれた8人の旅が、フルリメイクで甦る
本日より予約開始!
詳しくは公式サイトをチェック👀
jp.square-enix.com/rs3r/?utm…
#ロマサガ3R #ロマサガ3リメイク #デスサガ
『ロマンシング サガ3 デスティニーユナイテッド』 発表トレーラー
『ロマンシング サガ3 デスティニーユナイテッド』 2027年2月16日(火)発売決定&予約受付中!
【サムアルトマンお気持ちツイート】
・Astraもうすぐ出すで!期待しとってや!
・こいつヤバいで!おかげでワイらサマーバケイション返上して安全対策しとったわw かなわんわぁw
・てか、うちらのモデルヤバいレベルまできてもうたw さらに次のモデルすぐ作ったらヤバいし慎重にやるわww
Over the summer, we have been sprinting on safety priorities; it's more important than ever for capabilities and safeguards to advance together. We have more to do but have made a lot of progress. We are also going to be launching our next model soon.
There is an obvious tension here: on one hand, Astra is very good and we are excited to see what people will build with it. We are proud of our work.
On the other hand, we are clearly in a phase of development where we believe caution is warranted, and we are pacing our progress to ensure that we can meet the safety standards required by new capability levels.
Astra has been done training for a while now and is a significant step forward in both capabilities and alignment. For the models after that, we have been slowing things as needed to ensure that we can do sufficient work on safety and alignment.
AI is getting extremely capable; no one fully understands the consequences of this. Managing the transition to a world with abundant and powerful AI to optimize for safety and benefits to people should be one of the highest priorities in the world. It is our highest priority at OpenAI.
We have been living with the tension between being excited and anxious about progress for some time, and it is still discordant for us. We know it is much more discordant for other people. And yet, we believe strongly that the world needs to understand where AI is going and how models perform in the real world. More importantly, we believe the world will need aligned AI to manage the future phases of this transition.
An iterative loop where society and this technology evolve together is what will lead to the highest chance of getting this right.
So we hope you enjoy our new model, and we hope the world continues to take what’s happening in AI extremely seriously.
YuK1 retweeted
We are reseting usage for all paid users of Codex and ChatGPT Work.
Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes.
Depending on how you use Codex, you should see your usage go between 10% and 50% further than before.
We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed:
- Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed.
- Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed.
- Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed.
- Automations. Some custom schedules could run more frequently than configured. Fixed.
- Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed.
- Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed.
- Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this.
- MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed.
We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess.
Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!
YuK1 retweeted
Never slept better and feeling reseted. Brand new me and brand new usage for all ChatGPT Work and Codex users. Regaining my youth one button press at a time.
Happy Thursday
YuK1 retweeted
It's me again. I come bearing great news.
First of all, we have hit 20M active users for Codex some time this week. Second of all, this is cause for celebration and during the day we will credit every Codex and ChatGPT Work user with a BANKED reset that you can use at your own leisure. And we will have some other good news later too!
Now, on usage limits draining faster, while we're not seeing anything abnormal, we do take it incredibly seriously and there is an ongoing investigation. I will share if we do find anything and my below post is really a clarification on a specific pattern that we did see that I wanted to call out.
Go do something amazing today.
We've investigated a few messages about codex usage limits being different. That's not something we change without engaging the community and being transparent.
What we did see is that when talking to affected users many were using sub2api. Converting a subscription into api traffic to then re-serve or share across many users is not something we support and this type of usage gets flagged by our fraud-prevention systems.
You are completely fine if you use your subscription through Sign in With ChatGPT, either through the official clients or through one of the many OSS clients (Pi, OpenCode, ...) that support signing in with your account and using your included usage.


























