nope! they're releasing something called "Claude Code mods", toted as their "upcoming way to customize the Claude Code harness"

https://x.com/trq212/status/2101009392611278961

AGENTS.md implementation is open sourced as well: https://github.com/anthropics/claude-code/tree/main/mods/age...

Nice. Thanks!

As an individual that 'dozen people beta test' is required. It's not required if you're a business. Also depends on when your account was created.

https://support.google.com/googleplay/android-developer/answ...

Same, but I clicked it, awaited the update, and I'm on iOS 27 proper now-- so just a visual bug.

> just a visual bug.

Out of the gate, that isn't a good sign.

I eval'd this pretty heavily with no audio or just noise, as for us hallucinating a response is very bad. It works great in this scenario. There are some bugs, e.g. randomly exactly 20 seconds of silence will lead to a 403, but I'm sure these aspects will be improved over time. I didn't get any hallucinations though.

Are you in Smart or Verbatim mode?

https://ai.google.dev/gemini-api/docs/transcribe#transcripti...

They mentioned the pixel phone so probably using https://blog.google/products-and-platforms/platforms/android...

Looking at the description I was in Smart mode. I didn't know the model supports both

You can create a PostToolUse hook [0] which will automatically chastise Claude to shrink comments to one line. It's not perfect but better than the sea of prose it tends to generate by default. Bonus is that it would apply to your colleagues as well!

[0] https://github.com/chrisvariety/branch-fiction/blob/deb37f2b...

Good thinking! The multiline paragraph comments drive me up the wall.

No amount of agents.md / commit to memory updates has stopped agents from littering the code base with useless comments.

Think I'll add it to pre-commit hooks getting called by posttooluse

If you have a ACSM (the file type Adobe Digital Editions uses for DRM) I’ve been using https://www.acsm-converter.com to strip the DRM and return a standard epub

If using straight npm (v11.10.0 or higher), you can just add to .npmrc in the project root:

min-release-age=5

I tried it on my codebase. There's a lot of overlap with tools like Oxlint / ESLint, I'm not sure that's too valuable vs. a more focused tool that actually focuses solely on 'slop' signals. These lint rules tend to get very opinionated which is why those tools expose so many configuration options.

One real bug tho:

> [ERROR] Imports "mdast" but it's not declared in package.json

A type-only import like `import type { Blockquote, RootContent } from 'mdast';` is actually acceptable if `"@types/mdast": "^4.0.4"` is included in the package.json.

thanks for this catch, really appreciate. Can you create an issue on GitHub so you can easily track when I resolve this?

Nice ideas! I've been using the `?` shortcut in atuin [0] which accomplishes the same sort of thing, but these days also has access to an Agent-like experience which allows me to prompt something like "Conventional Commit message for unstaged changes" and it will call `git diff` (after asking permission, of course) and then generate the commit message.

[0] https://atuin.sh

Can you use any API like openai or openrouter with atuin?

Not currently, but we've been discussing how best to implement BYOK and BYOM setups