Microcompact: Clear old tool calls to extend session length
Subagents: @-mention support + model selection for agents
PDF support: Read PDFs directly from your file system
Microcompact automatically clears old tool calls to free context when your session gets long.
This means you can work longer before needing a full context compaction, maintaining your most critical project context.
We’re also upgrading subagents and giving you the ability to call them directly.
@-mention a subagent in your prompt to ensure it gets called (e.g. @.code-reviewer).
You can now select which model you want each subagent to use. Choose Opus 4 for complex planning subagents, or Haiku 3.5 for simpler operations.
This lets you balance performance and token usage based on each agent's role.
Lastly, we’re adding PDF support.
Claude Code can now read PDFs from your file system. No conversion needed - just reference them like any other file.
Useful for working with documentation, specs, or research papers.
All features available now! Restart Claude Code to update.
We've recently shipped a fresh batch of Claude Code features to improve your workflow! These updates make Claude Code faster, more visual, and easier to control.
Here's what's new:
1/ Improved multimodal support
You can now drag and drop images directly into Claude Code. Great for:
- Debugging UI issues
- Discussing design mockups
- Working with visual assets
Claude Code sees what you see.
2/ Check-in permissions
Teams can manage which tools Claude Code can use across a codebase by checking permissions into git.
Set up auto-allowed tools for speed, or define security policies with never-allowed tools.
Up first: Vim mode. This gives you the familiar insert/command modes for editing your prompts in Claude Code. Turn it on by typing the slash command /vim.
But that's not all:
Custom slash commands. You can create personalized workflows that can be invoked anytime as slash commands.
Make them by adding Markdown files to your .claude/commands/ or ~/.claude/commands/ directories. The contents of those files will become new commands.
You can build commands for common workflows like "triage GitHub issues," "spellcheck the code," and "query Sentry logs then bisect to a git commit."
Think of them as saved workflows for tasks you want to run more often.