I’m thinking about banning Claude code at Shopify until they change their mind and read AGENTS.md and .agents/skills etc. Insisting on only reading CLAUDE.md sometimes leads to split brain problems when different team members use different tools. Just unnecessary.

It's intersting (and slightly enjoyable?) to see the amount of doubt about my workflow on Reddit: I don't know what to say other than it's real and you can absolutely be this productive (and I know several other people who are—even outside of Anthropic).

Just FYI. If you are switching models in a session all the time - you are doing it wrong. Every time you switch, your entire prompt cache is invalidated on the new model you switch to, and you have to repay the full input tokens price for all of it. Stop doing this unless those models are free. This is not a hermes thing - this is a fundamentals of inference thing.

Enterprise-managed auth for MCP connectors is now generally available. For Claude Team and Enterprise admins, authorization is centralized through your identity provider. For users, tools and data are connected automatically, without the need for individual OAuth.

Humans are no longer the biggest token consumers Agentic tokens passed human ones on OpenRouter earlier this year. Today: 7.3T vs 1.4T Your AI strategy isn’t training people on a tool. It’s building the paths and guardrails for agents to navigate your data

Quick demo of how I use session to session messaging in Claude Code + Ghostty (Save this and try it in your own workflows) 1- I always start with a regular session and a panel running claude agents 2- The first session becomes the orchestrator. It creates the initial context, then distributes the work across other sessions using forks 3- Each fork starts with that context + a prompt telling it what to work on 4- I rename each session with ctrl + r to keep things organized and make it easy to message them from the main session 5- Using @ I send messages to the sessions that are running and ask them to report their task status back, so the main session always knows what everyone is working on This way, I only need 2 or 3 panels open and can switch between tasks as needed The days of opening endless terminal panels and running Claude Code 100 times just to look productive are over! What we need now is ORCHESTATION one main session coordinating everything through session messaging + Agent View And the key is context, build it in the main session first, then fork from there That’s what makes the entire workflow click

a skill people at Anthropic have been using a lot recently: ELI5 /eli5 <what you want explained> "explain like I'm someone who knows nothing about this topic, using a HTML artifact with big pictures and few words"