Evaluating Claude Opus 4.7's Memory On Complex Multi-Step Tasks

An experiment assessing within-session constraint memory in Anthropic’s Claude Opus 4.7 used five-step production-style debugging tasks in which later recommendations had to respect rules established earlier, distinguishing memory coherence from context-window capacity. Across two runs at high effort through OpenRouter, Opus 4.7 failed constraint checks on 40% of tasks, compared with 100% for Opus 4.6, while also averaging lower latency and cost; however, Opus 4.7 consistently struggled when required to retain and synthesize three simultaneous constraints. Direct Anthropic API tests found that increasing reasoning effort from standard to high or xhigh substantially raised latency and cost but did not reliably improve memory adherence, with standard effort passing all three tested tasks and higher settings sometimes introducing drift. The evaluation also identified implementation considerations, including that OpenRouter reportedly ignores Anthropic-specific effort and thinking parameters, while Opus 4.7 requires API-setting changes from Opus 4.6. Although the small sample size, single-run effort tests, and incomplete self-correction data limit conclusions, the results suggest that external memory systems may be more dependable than higher effort settings for multi-constraint agent workflows.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.