A lively Reddit thread from r/ClaudeAI (https://www.reddit.com/r/ClaudeAI/comments/1qxessv/workflow_since_morning_with_opus_46/) captures a pragmatic, recurring lesson: no matter how capable the model looks, you still have to check the AI’s work.
Main takeaway
“yes, you still have to check the AI’s work, you animals.”
That frankness frames the debate: Opus 4.6 shows improvements in long-session context and code quality for many users, but practical risks remain: security issues, instruction drift mid-session, and occasional destructive refactors.
Why this matters
Teams are already experimenting with giving LLMs responsibility for multi-file refactors, feature branches, and even test generation. If models are producing 50+ files per session, the verification strategy determines whether you get velocity with safety or a pile of fragile tech debt.
Recommended tactics
- Treat the model as a junior engineer
- Have it write behavior specs and tests before implementation (TDD-style prompting). As one commenter put it: make it write the tests first, then implement. This shifts failures from manual scanning to test results.
- Automate verification via CI
- Wire generated outputs into existing CI so tests run after each agent session or PR. Review failing tests and iterate.
- Use a project-level system prompt (CLAUDE.md)
- Create a canonical instruction file with project conventions, file structure, and constraints. Users report this reduces style drift and accidental removals.
- Phase work and commit frequently
- Work in discrete phases, review each phase, and have the model analyze prior commits for regressions. This reduces long-session surprises.
- Don’t trust the model on security
- Multiple users noted Opus 4.6 still bakes in obvious security vulnerabilities. Keep security reviews and static analysis in your pipeline.
Performance notes on Opus 4.6
- Positive: Several users reported improved context retention in long refactors and better alignment with existing code patterns.
- Negative: Some saw regressions where the model removed necessary bespoke fixes or introduced new bugs; token usage can be higher (bigger context windows burn tokens faster).
Context and broader trends
This thread echoes a persistent pattern in practical LLM adoption: generative models accelerate work but shift the risk profile rather than eliminate it. Teams that succeed are the ones building verification and automation around models: tests, CI, prompt manifests, and human-in-the-loop checkpoints, rather than treating outputs as production-ready by default.
My takeaways
- Automation + tests are the multiplier. Ask the model to produce tests first and run them automatically.
- Systematize prompt instructions (CLAUDE.md or equivalent) so the model follows your project’s norms.
- Keep security and code review gates; models still make dangerous, confident mistakes.
- Treat improvements (like better context retention) as productivity gains that require equal investment in guardrails.
Remember that there is often another side to the story: some users report smooth experiences and meaningful productivity wins with Opus 4.6, but those wins come from embedding the model into a disciplined workflow, not ignoring verification.
Leave a Reply