Claude Code 2.1.290 released
Added serverToolUses to the result of a mod's turn.step hook: the tool calls the API ran itself (the advisor), each with its id, name, input, start and end; Added agentId to the tool.check event of plugin hooks, so a hook can tell a subagent's permission…
What changed
- Added serverToolUses to the result of a mod's turn.step hook: the tool calls the API ran itself (the advisor), each with its id, name, input, start and end
- Added agentId to the tool.check event of plugin hooks, so a hook can tell a subagent's permission check from the main session's
- Added ceiling to the question and verdict a mod's tool.check hook reads, naming the approval an organization requires for a tool
- Added ThemeKey and Color types to the plugin hooks typings, so an editor lists the theme colors a mod's drawing can name
- Added to claude plugin validate: each hook a mod registers at a gating site is listed with whether it has a .catch (gatingHooks under --json)
- Added a Deny button to the Claude apps gateway's sign-in approval page: it ends the pending sign-in, so the waiting terminal stops within seconds
- Added claude attach and claude logs : part of a session name works in place of the id
- Added /claude-api managed-agents-onboard to set up the Managed Agents pattern a page describes as ant apply files
Generated from AgentGid's daily data on public sources. How we collect it.
The agent in this story
More about Claude Code
-
Claude Code: Elevated errors loading usage data on platform.claude.com
-
Claude Code 2.1.292 released
-
Claude Code: Elevated errors for Claude Opus 5.5
-
Supercharge regulated workloads with Claude Code and Amazon Bedrock
-
New agent skill: Amazon SageMaker optimized generative AI inference for your coding agent