Claude Code Adds /claude-api latency-optimize to Speed Up Your Claude API Code
Claude CodeClaude Code 2.1.319 adds /claude-api latency-optimize. It finds where code that calls the Claude API makes people wait and tries faster settings against the user's own eval. The same release also updates the /claude-api managed-agents-onboard templates.
Key Takeaways
/claude-api latency-optimizetargets where API code makes people wait.- It tries faster settings against the user's own eval, per the release notes.
- It extends the built-in
/claude-apiskill, alongside migration helpers. - The
managed-agents-onboardtemplates now mirror the Console. - Web search and fetch are turned off in five templates whose prompts do not use them.
- The Performance tuner template is removed.
A New /claude-api Task
Claude Code 2.1.319 adds /claude-api latency-optimize. The release notes describe it as finding where a project's Claude API code makes people wait, and trying faster settings against the user's own eval.
Fits the Existing /claude-api Skill
The built-in /claude-api skill already covers other API chores, such as the api-version migration added in October. This adds latency tuning to that set. Eval-backed testing means a faster setting is checked against the user's own measure of quality, per the release notes.
Managed Agents Templates
The release also updates the /claude-api managed-agents-onboard templates to match the Claude Console. It removes the Performance tuner, renames two templates, and turns off web search and fetch in five whose prompts do not use them. A separate fix corrects the skill's statement that Console web settings do not apply to Managed Agents sessions.