Claude Code v2.1.265: Plugin Directory Support, 1GB Tool Result Cap, and More
Anthropic shipped Claude Code v2.1.265, a maintenance release with several notable additions and a long list of bug fixes aimed at plugin management, telemetry, and reliability.
Key Additions
- Plugin folder support – You can now point
--plugin-dirat a folder containing multiple plugins. Each child folder with amanifestloads, and plugins added or removed while running are picked up automatically. - 1 GB cap on tool results – Results saved to disk are now limited to 1 GB. If a result is truncated, the in-conversation preview indicates that the saved file was truncated.
- Unified telemetry – Claude Desktop and Cowork now send
user.emailanduser.groupsthrough the Claude apps gateway, matching terminal sessions.
Bug Fixes Worth Noting
- Prompt-cache reuse fixes – Resuming a foreground-spawned subagent no longer changes its tool list and system prompt prefix, preserving cache reuse. Similarly, agent teammates and resumed subagents keep
SubagentStarthook context and preloaded skills in the prompt prefix. - Resume after crash during tool call – The last prompt is no longer rewritten, and the interrupted tool call is kept and marked as interrupted.
- Command-line fixes –
/model opusplan[1m]no longer fails with "Model not found." Also,/modelnow reports if saving the default model fails, instead of falsely claiming success. - Syntax highlighting – Fixed a bug that occasionally dropped a character after Ruby
?, Erlang$, or Perl$sigils in permission prompts. - Terminal UI – Fullscreen transcript no longer jumps a row when suggestion lists open/close. Two-key shortcuts now wait up to 3 seconds for the second key (important in tmux) and show a notice on timeout.
- Security – Plugins with backslashes in paths no longer bypass symlink containment checks on macOS/Linux. Plugin dirs starting with two dots are now handled correctly.
- Remote Control & background sessions – End-of-turn signal is now sent after the final message. Background (
--bg) sessions are less likely to be retired mid-turn near idle timeout. - IDE/SDK sessions – VS Code and SDK sessions no longer require re-login when a session closed during a token refresh.
- Plugin and marketplace –
/pluginDiscover/Browse andclaude plugin list --json --availablenow show descriptions for marketplace plugins whose metadata only exists inplugin.json. - Workflow runs – Resuming after a container restart now gives a clear error if the run journal is missing, instead of rerunning every agent.
- API skills – The
claude-apiskill's error-code guide now correctly states model access failures return 404 and unavailable beta headers return 400 (not 403). - Non-interactive sessions – A
cdnow persists across turns in-pmode with stream-json input, Agent SDK, and cloud sessions.
This release focuses on hardening the developer experience, especially for teams relying on prompt caching and long-running sessions.
📖 Read the full source: GitHub Claude-Code
👀 See Also

Skill Scaffolder: Build OpenClaw Skills Without Writing Code
Skill Scaffolder is an open-source tool that lets users create OpenClaw skills by describing what they want in plain English. It handles the entire process—interviewing users, writing skill files, testing, and installation—without requiring YAML, Python, or config files.

Obsidian Integration for Persistent Memory in OpenClaw and Claude Code
A Reddit user demonstrates how connecting OpenClaw and Claude Code to an Obsidian vault creates persistent long-term memory across sessions. The setup automatically links memories, context, project files, and notes, with all instances able to access shared memory when needed.

Codegraph: Pre-indexed knowledge graph cuts Claude/Cursor tool calls by 94%
Codegraph uses a pre-indexed knowledge graph of symbol relationships, call graphs, and code structure to reduce API tool calls by up to 94% and speed up usage by ~77% for Claude, Cursor, Codex, and OpenCode agents.

Claude Code's Monitor tool pipes dev server logs into AI-driven auto-fixes
Claude Code's Monitor tool lets you run a dev server in background, tail logs with smart grep filters, and have Claude auto-detect errors, write fixes, and commit them — all while you test the UI.