What X is shipping with agents right now.

Piotr Mińkowski@piotr_minkowski·3h

A drop-in .claude folder for Spring Boot projects: six specialist subagents (reviewer, security, DevOps and more) plus skills for JPA, testing, logging and modern Java, Apache-2.0.

🚀 Claude Code Template v1.0 for Spring Boot is here! What's new? 🔹 6 rewritten agents 🔹 2 new skills + major improvements to existing ones 🔹 Modern Spring Boot/Java patterns 🔹 Better testing and security 👉 https://github.com/piomin/claude-ai-spring-boot #ClaudeCode #SpringBoot #Java #AI

CyrilXBT@cyrilXBT·4h

A copy-paste settings.json plus two subagent files that split work by model: Opus plans, Sonnet codes, a Haiku scout searches files, and an Opus critic attacks the diff.

i can't comprehend why people run claude code on default settings one settings change and every model gets its own job: → opus plans every task and advises when stuck → sonnet 5.5 writes the actual code → haiku handles every file search → a critic agent tries to break your diff before you merge Opus thinks. The cheap models grind. paste this into claude code 👇 Add this to ~/.claude/settings.json. Keep every hook, permission and plugin I already have. Then create the two agent files below and show me the diff. ```json { "model": "opusplan", "advisorModel": "opus", "effortLevel": "medium", "modelSettings": { "claude-opus-5-5": { "effortLevel": "high" }, "claude-sonnet-5-5": { "effortLevel": "medium" } }, "env": { "CLAUDE_CODE_SUBAGENT_MODEL": "haiku" } } ``` ~/.claude/agents/scout.md ``` --- name: scout description: finds code fast. returns file paths and line numbers only. model: haiku tools: Read, Grep, Glob --- Locate exactly what was asked. Return file:line. No fixes. No opinions. ``` ~/.claude/agents/critic.md ``` --- name: critic description: reviews a diff or plan before any task is called done model: opus tools: Read, Grep, Bash --- Assume this is broken. Find how it fails. One line per issue, worst first. ```

CyrilXBT@cyrilXBT·7h

Eight repos that level up Claude Code: gstack, claude-flow, oh-my-claudecode, orca, claude-mem, context-mode, agent-skills, everything-claude-code.

Claude Code can build full apps. These 8 repos make it build them better. PLAN IT gstack → Garry Tan's setup that gives Claude Code roles like founder, eng manager and QA https://t.co/G2C5IJQq6O STAFF IT claude-flow → runs swarms of agents working together https://t.co/eQQsm7YfI4 oh-my-claudecode → multi agent orchestration on top of Claude Code https://t.co/MM6wevLBRt orca → parallel agents https://t.co/jysYX2z7T7 REMEMBER IT claude-mem → memory that survives between sessions https://t.co/1XI7Odux4C context-mode → keeps tool output from flooding the context https://t.co/QZh1fkM8RD DO IT RIGHT agent-skills → senior engineer habits: specs, TDD, reviews https://t.co/bONo0s9NJu everything-claude-code → agents, skills, hooks and configs in one place https://t.co/2Er9PREAih Bookmark this.

AICodeKing@aicodeking·8h

A benchmarked case for skills over MCP: one 8 KB SKILL.md using plain CLI tools matched the REA reverse-engineering MCP server's accuracy while running 38% faster and 35% cheaper.

Introducing LeanREA: one 8 KB skill file that does what REA does, with plain CLI tools and no MCP. Benchmarked in Claude Code (Sonnet 5.5, 36 runs) against REA: 38% faster, 35% cheaper, 56% fewer turns, same accuracy. Free and open source: https://github.com/aicodeking/leanrea

ClaudeDevs@ClaudeDevs·13h

Claude Code now compresses the whole conversation on every turn, so replies start noticeably sooner on long sessions, and cloud sessions boot while you're still typing.

We keep improving performance across Claude, and you may have noticed it starts responding sooner! Claude Code now gzips the conversation it sends on every turn, so it reaches the model faster. Cloud sessions also start up as soon as you start typing.

Pratham@Prathkum·15h

How the Claude Code team reviews agent PRs: one agent group hunts bugs, another votes on whether they're real, and a bot approval never replaces a human owner.

Anthropic published how the Claude Code team does code review. Claude writes about 90% of Claude Code. In their monorepo, changes per day went from 2,500 in May to over 30,000 in September. So agents write the code, and then agents review the PRs. One group hunts for bugs, another group votes on whether each bug is real. One PR went through 50+ rounds of review and fixes overnight, an agent author and an agent reviewer just feeding each other until a human pulled the plug. 😂 Still, merged PRs more than doubled since June and reverts have dropped by over 40%. And a bot’s approval never counts as a human’s. Whoever prompted the agent owns the change. I wonder why we even need separate agents to review code when agents are going to write the code anyway. Crazy!

ClaudeDevs@ClaudeDevs·16h

The Claude Code team's own write-up on reviewing agent-written PRs at volume, with numbers (2x merged PRs, 40% fewer reverts) and steps to adopt it.

Claude writes about 90% of Claude Code's code. From June to September, merged PRs more than doubled while the share reverted fell by more than 40%. We wrote about how we changed code review to get there, and how to adopt it: https://claude.dev/blog/solving-code-review-at-anthropic/

Ibragim@ibragim_bad·20h

Your old ~/.claude and ~/.codex sessions are an eval set: your corrections become test cases for benchmarking models, harnesses and plugins.

I had 1,270 agent sessions sitting in ~/.claude, ~/.codex and ~/.pi that’s an eval set: my corrections to the agent are the test cases turned it into the my-mini-benchmark. now I test any model, harness or plugin on my own tasks guide + the skill 👇 https://t.co/oaRtwFJTxT

Daniel San@dani_avila7·1d

/export file_name dumps a Claude Code session to plain text: hand it to another agent to continue, or mine it to write custom skills.

Claude Code lets you export your entire session with /export file_name This creates a plain text file containing your session history You can use it as context for another agent to continue your work, or analyze it to create custom skills that improve your Claude Code workflow https://t.co/cMZG0J01s9

aditya@adxtyahq·1d

A 40-agents-a-day setup: Claude Code on Opus plans from the Linear ticket, then work fans out across Claude, Codex and a big VM.

i run around 40 AI agents a day, 24/7. here's how i do it. my setup: 3 Claude $200 accounts 1 Codex $100 account Grok Bot a CPU VM with 128 GB RAM and 32 cores my workflow: 1. planning: Claude Code with Opus 5.5 breaks down the Linear ticket, reasons through the architecture, https://t.co/5k7FQTqP2r

Ackerman@Yarilo7brigada·1d

Shrink CLAUDE.md to core rules and move procedures into skills that load on demand, with descriptions written as 'Use when...' triggers.

THIS IS A F*CKING GOLDEN JACKPOT Your 800-line CLAUDE.md is killing Claude. Every session starts with the model reading instructions on deploys, releases, migrations, API style and ten other things. None of that matters when the task is fix this typo. The context is clogged from the first second, and the rules that actually matter get lost in the noise. The idea: move every procedure into its own skill. A skill is a folder with a SKILL.md file, plus optional scripts and reference docs. At the start of a session, Claude only sees each skill’s name and a one-line description. It loads the full text only when the task actually calls for it. Here’s the split: - CLAUDE.md holds only what’s needed every time: stack, structure, 10–20 core rules - skills hold procedures: deploys, releases, migrations, reviews, onboarding into a module - the description decides when a skill fires, so write it as a trigger: Use when... - scripts inside a skill get executed, not read, so deterministic logic costs zero tokens The key trick is progressive loading. Twenty skills in context cost about as much as twenty lines of description. You can pack your team’s entire wiki into the project, and Claude opens the right page exactly when it’s needed. Bonus: any skill can also be invoked manually as a slash command, like /deploy or /release. The same file works both automatically and on demand. CLAUDE.md remembers the essentials. Skills know the details. Context stays clean. full tree CLAUDE.md: stack, project structure, core rules, nothing else .claude/skills/deploy/SKILL.md: deploy steps, checks, rollback .claude/skills/release/SKILL.md: versioning, changelog, tags .claude/skills/migrations/SKILL.md: how to write and verify migrations + a check script .claude/skills/code-review/SKILL.md: the team’s review checklist every skill’s description starts with - Use when... paste the tree and this prompt into Claude Code ↓ Rebuild my Claude Code setup around this tree: Read CLAUDE.md and all linked docs. Split the content into two parts: what’s needed for every task, and procedures for specific situations. Keep only the first part in CLAUDE.md. Target: under 100 lines. Move each procedure into .claude/skills/<name>/SKILL.md with name and description in the frontmatter. Start each description with “Use when...” and list concrete triggers. If a procedure has deterministic steps (checks, generation, validation), move them into scripts inside the skill folder and call them from there. Find procedures I repeat that aren’t written down anywhere, and propose them as new skills. Show me every change as a diff first. No edits until I say go.” ↳ https://t.co/wK9W7spslN

Kaiju@kaijucode·1d

A full Claude Code setup using only built-ins: CLAUDE.md, opusplan, Haiku search subagents, critic subagent, hooks, skills, worktrees, /schedule.

claude code basically runs my repo now, i just review and press enter... here's why: almost all of it is free config you set up once on day 1. here's my whole setup and what it costs: required (ships with claude code) > memory → CLAUDE.md > models → opusplan (opus plans, sonnet builds) > search → haiku subagents for every file lookup > review → a critic subagent before every merge > safety → permissions in settings.json > undo → plan mode + /rewind > context → /clear between unrelated tasks optional (add when you need it) > automation → hooks that format on every write > repeatable → skills for the prompts you retype > parallel → git worktrees > research → /deep-research > escalation → an opus advisor when you're stuck > scheduling → /schedule routines the only thing on this list you need to pay for is your claude plan. everything else is included with claude code.

dex@dexhorthy·2d

Dex Horthy on idle compaction: compacting before the cache expires beats paying the cache miss when you return.

this is a good idea - always confused why claude would ask me if i wanna compact after 24h to save tokens since the cache expired…like i was gonna gonna eat the cache miss on the input to compaction anyway, right!? Anyways good ship imo https://t.co/UUHZ6YKepa

lauren@poteto·2d

pstack's most durable part is its tiny 10-20 line principle skills; expect most skills to compress into short principles as models improve.

perhaps one of the most durable parts of pstack are its engineering principles: very concise skills (~10-20 loc) that distill down good practices into its core. as models get smarter, i expect most of pstack skills to compress into short principles or workflows (a generic list https://t.co/bDIpHhE1cM

Lydia Hallie ✨@lydiahallie·2d

Claude Code now compacts long idle sessions right before the ~1h prompt cache expires, so resuming reprocesses only the summary.

We recently added idle compaction to Claude Code! It now compacts long idle sessions right before the prompt cache expires (~1h). If you come back to it later, it only has to reprocess the summary instead of the entire conversation, which saves you some usage. https://t.co/SG3QyTNFwr

Thariq@trq212·2d

Claude Code Desktop now knows its own capabilities, like spinning off subsessions. The team calls it almost a v2.

Claude Code Desktop is now so much aware of its own capabilities and how it can work with you, like spinning off subsessions. I think of this almost like a v2, so many small details went into make it great. https://t.co/dpgj4fd8sQ

ClaudeDevs@ClaudeDevs·2d

Claude Code desktop update for running many sessions side by side: faster session start, easier work splitting, and live visibility into each.

We've been working hard on making the Claude Code desktop app great for running lots of sessions side by side. It's now much quicker to start sessions, easier to split work across a few, and you can always see what each of them is doing. Here’s what's new: https://t.co/iF1WuEueMB

Daniel San@dani_avila7·3d

Anthropic's code-modernization v1.0.0 Claude Code plugin modernizes legacy code and tries to prove the new version behaves like the old.

Anthropic released code-modernization v1.0.0, a Claude Code plugin for modernizing legacy codebases Save this post if you have a legacy project worth modernizing What I find interesting is that it doesn’t just rewrite code. It tries to prove the new implementation behaves like

lauren@poteto·3d

New /in-your-own-words skill in pstack makes the agent restate your goal so you confirm it understood intent before it starts.

this is now a new skill /in-your-own-words in pstack 0.15.23! extremely useful to ensure that you and your agent are aligned on the goal and that it understands your intent clearly https://t.co/3dIimxHJEt

Anthropic@AnthropicAI·3d

Anthropic went from ~2,500 to 30,000+ merged changes a day as agents took over, and had to build in-house source control because human-scale dev infra became the bottleneck.

New on our Engineering blog: Creating in-house source control. In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.