j1nn0

Japanese developer working with Vue, PHP, C#, and AWS.

[j1nn0 @j1nn0]

書いた。

禁止語リストをやめて、事実・推測・判断を分けるスキルに writing-ja を作り直した https://t.co/XKTbTDhPLy #blog #ai_agents #agent_skills

[j1nn0 @j1nn0]

書いた。

ZedからDocker内のoxfmtを使おうとして、macOSとLinuxの壁にぶつかった https://t.co/L08Tlus91K #development_environment #devcontainer #editor #zed

[j1nn0 @j1nn0]

書いた。

Vue 2.7から3.5へ移行した。それでもTypeScriptは入れなかった https://t.co/51jj8h0LPL #frontend #vue #javascript #typescript

[j1nn0 @j1nn0]

スタビライザーの異音だけはマジでイラつくからな。
GPL 205 G0も使ったけど解決しなかったし。
付け方が悪かっただけかもしれんけど。

[j1nn0 @j1nn0]

めっちゃ気になるなこれ

[Mungi @MUNGI_KBD]

Designer Studioの新型PCBスタビ

ワイヤーの揺動構造を一新してガタつきや異音の原因を解消したらしい
発売は今月末〜来月初予定
https://t.co/Vv17IrsHxI

[j1nn0 @j1nn0]

書いた。

某有名JRPG風ポーカーをAIエージェントに作らせた https://t.co/zwL5jNdlBw #ai_agents #terminal #javascript

[j1nn0 @j1nn0]

書いた。

OGP画像の生成から実装までAIエージェントに任せた。人間がやったのは2回のレビューだけ https://t.co/ERbgVbjfpG #blog #ai_agents #hugo #papermod

[j1nn0 @j1nn0]

書いた。

「PaperModに色を足しただけ」を3回突き返して、ブログをHallmarkで刷新した https://t.co/uSOOlYqRUg #blog #ai_agents #papermod #hallmark

[Tibo @thsottiaux]

10M!

New day, new usage reset for paid users of Codex and ChatGPT Work. Lands in the next hour. Enjoy.

[j1nn0 @j1nn0]

Hallmarkってスキルを使ってデザインを刷新してみた。そのうち記事も書くと思う。
https://t.co/kF6B6qlK33
https://t.co/xrSeqJJLaI

[j1nn0 @j1nn0]

OpenCode Goで使えるようになってた。

[j1nn0 @j1nn0]

CloudFrontが落ちてる？504 Gateway Timeout

[Tibo @thsottiaux]

We've had no 5h limit in Codex plus and pro for a few days. Do you think it is better or are you finding it difficult to manage the usage included in the weekly limit effectively?

If we were to make this different, what should it look like in an ideal world?

[j1nn0 @j1nn0]

Vortex Keyboard M0110のVIAキーマップ https://t.co/gWL3FUsM8y #keyboard #m0110

[j1nn0 @j1nn0]

いつの間にかPinia v4がリリースしてた。
追々対応するか。

[j1nn0 @j1nn0]

書いた。

2026年の開発環境 https://t.co/aXaPmn80pE #開発環境 #mac #terminal #editor #mise #dotfiles

[j1nn0 @j1nn0]

ということはつまり

[Tibo @thsottiaux]

Tomorrow might be 8M active user celebration day. Just saying

[Tibo @thsottiaux]

Morning. The last 48 hours of Codex and ChatGPT Work have been intense! Three important updates:

- Temporarily removing the 5 hour usage limit restriction for all Plus, Business and Pro plans
- Rolling out changes that will make GPT 5.6 Sol more efficient across the board and that will be reflected in less usage being used so that it can take you further. Exact impact to be quantified and shared
- We hit 6M active users, and are landing a usage reset in the next hour

Go do things

[Claude @claudeai]

We're extending Claude Fable 5 access on all paid plans, as well as keeping Claude Code’s weekly rate limits 50% higher, through July 19.

[Tibo @thsottiaux]

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice.

Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday.

We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right.

- We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear.
- We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find.
- Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay.
- And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience.

We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems.

A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had.

The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version.

Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.