えーてる

ソフトウェア開発界隈で仕事してます（非エンジニア）。PdM、PjM、アジャイル推進。CSPO®️ 取得。AI、写真、ゲーム、SF、鶏肉が好物です。

[herdr @herdrdev]

0.7.5 is out!

herdr is getting used more and more for multi-agent orchestration, so this release ships a native agent cli built exactly for that. more in below 👇

but first, the new agent sidebar: deeper customization with per-token colors, bold and dim, plus full filtering and sorting any way you want. from config, scripts, or plugins, all through the api!

[Google @Google]

Today we’re expanding the Gemini family with three new models built to be faster, more token efficient, and reliable at scale.

Meet the new Gemini models ↓

[Claude @claudeai]

New in Claude Cowork: teach Claude a skill.

Record your screen while you do a task, talk through it as you go, and Claude turns it into a skill it can run again. Find it under Record a skill in the + menu of the Claude desktop app.

Available on Pro, Max, and Team plans.

[後谷戸隆 @ushiroyato]

詩　あの祠壊したわけではないんか？（1/4）

[えーてる @clearether]

Claude Code の checkup コマンドがいい感じ

/checkup

環境の健康診断コマンド

実体は`/doctor`のエイリアス

インストールの健全性だけでなく、

・未使用のスキルやMCPサーバー
・プラグインとコンテキストコスト
・`CLAUDE.md`の重複
・遅いフック

などを確認できる

まず検出結果を報告し、変更前には確認を求めるつくり

公式ドキュメント：
https://t.co/NAPMz53VSx

[ClaudeDevs @ClaudeDevs]

For the small teams with big plans: Claude Team plans now start at just 2 seats instead of 5.

Get shared projects, admin controls, centralized billing, SSO, and enterprise search across all your team's tools, all under one plan.

[Claude @claudeai]

Beginning July 20, Claude Fable 5 will be included in all Max and Team Premium plans, at 50% of limits.

Pro and Team Standard users will continue to have access to Fable via usage credits, and will receive a one-time $100 credit.

Demand for Fable has been challenging to predict, which is why we rolled it out to subscription plans in stages, extending access several times as we secured additional capacity.

[えーてる @clearether]

「いい話だなー」と、思うより前に「権利関係大変だっただろうなー」と思ってしまった

NVIDIA and Japan: Building the Next Industrial Revolution https://t.co/Fm5ucw8Hg0 @YouTubeより

[ITmedia NEWS @itmedia_news]

Google、「NotebookLM」を「Gemini Notebook」に改称　Geminiエコシステムへの統合を強化
https://t.co/yV2HlqX4Rp

[えーてる @clearether]

複数のAIエージェント向けツールを見比べてみた

Orcaは、エージェントを並列に動かす作業場。それだけではない多機能さも備えているけど、マルチエージェントがやりやすかった。Electron製なのがちょっと気になる

Herdrは、端末を閉じても戻れる実行環境。cmuxで似たことをやっていたが、ツールに依存しないAIエージェント特化マルチプレクサは便利。rust製

agmsgは、エージェント同士をつなぐ通信の仕組み。 「No daemon, No network, No complexity」。bashとsqlite3だけ。シンプル

中心にあるものがそれぞれ違う

ここを分けて考えると、選びやすくなりそうだ。

https://t.co/R3J4LAn2Pn
https://t.co/1W2hBitUWo
https://t.co/Vn64XTP2H0

[えーてる @clearether]

なるほどめでたい

[IBM @IBM]

01001000 01100001 01110000 01110000 01111001 00100000 01001110 01100001 01110100 01101001 01101111 01101110 01100001 01101100 00100000 01000001 01001001 00100000 01000100 01100001 01111001

[えーてる @clearether]

ついに終わるか

[ボケて(bokete)公式 @boketejp]

「写真で一言 ボケて」は2026年9月30日をもってアプリのサービスを終了します。18年間、本当にありがとうございました。
詳細はボケてお知らせブログをご覧ください。
https://t.co/eYlDww2cLG

[えーてる @clearether]

文章を書いていて、内容はあるのに平坦に感じることがある

その原因を、情報量ではなく「認知モードの切り替え」として考える日本語ライティング規範

https://t.co/rusTsQD1sv

観察、逡巡、断定、再観察

文章の緩急を、装飾ではなく構造として扱っているのがおもしろい

[Boris Cherny @bcherny]

Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things.

I think many of these automations have become even more important now. This is true for a number of reasons.

First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time.

Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time!

Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation.

Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.

[えーてる @clearether]

AIに仕事を渡すとき、
つい記憶まで抱え込ませたくなる

でもセッションをまたぐ失敗を、
毎回プロンプトに書き足していくと、
だんだん重くて抜け落ちる

だから自分は、外部の Markdown に分けて置いて、
必要なときだけ取りにいく仕組みにした

全部覚えてもらうより、
思い出す導線を用意するほうが楽だった

まだ粗い。でもこの風味は残したい

[やったるぞ‼️🇯🇵 @qat8EJFlDVwxKGG]

日本にいそうな神々
テストにでるかな〜🙃

[えーてる @clearether]

出社リモート論争がまた巻き起こっているようだが、

- リュックを前に抱えたら邪魔と言われるくらいに人がミッチミチに乗る電車
‐ 島型レイアウトでそこらじゅうからの視線を浴びながら仕事をするオフィス環境

このあたり何とかならんのかなぁと思ってる

[SpaceXAI @SpaceXAI]

We've open-sourced Grok Build and have reset usage limits for all users.

Open sourcing Grok Build allows anyone to support making a reliable and robust harness. Check out our code, including the Git repo for the Grok Build CLI.

https://t.co/3SSvPu2Nrz

[OpenAI Developers @OpenAIDevs]

Meet kbd-1.0-codex-micro, built with @work_louder.

Map the buttons and joystick to your workflow, and keep your pinned chats in view.

Get yours before stock returns 410.