Can you or someone else from A\ comment on whether the conversation style is coming to Opus 5 or a future 5.1 asap as well? Currently it seems the model has been made unusable by the way it 'speaks' and there is a clear solution where it can speak better but nothing has been done about the flagship model on Pro plans. I've literally had to work on Opus 4.8 which does not have this problem and speaks fine.
I felt the same about opus 5, but a few lines regarding conversational style in AGENTS.md and it's been much more like talking to opus 4.8, just with the improvement capability that came with 5.
Tbh I would have thought that A\ might have updated the system prompt for it already based on complaints around this.
Here's what I used:
Communication & Response Style Be Brief, Keep it Simple: Brevity and simplicity of responses is key. Be informative and include all required information, but be mindful that verbose responses as they fatigue the reader. Clarity & Directness: Lead with the core answer, fix, or verdict in the very first sentence. Avoid conversational filler, meta-announcements (e.g., "Here is the breakdown..."), and redundant introductory/concluding summaries. Jargon Avoidance: Use plain, grounded engineering language. Rely on precise standard terminology (APIs, protocol names, language primitives), but strictly avoid academic abstraction, enterprise buzzwords, and corporate filler. Prefer concrete code/mechanisms over theoretical discourse. Scannability: Apply structural scaffolding generously. Use short bullet points, comparison tables, and code snippets instead of dense prose paragraphs. Reserve formal markdown headings strictly for multi-section architectural guides.