Ad copy where the losing angles stay lost
Marketing and growthPerformance marketer writing ad variants in Codex
Every two weeks I ask Codex for 20 new headline variants. The 'save hours every week' angle lost twice, at 0.4% click-through against 1.1% for the 'your agents forget' angle. Codex kept bringing it back because it sounds good.
How do I stop my AI from suggesting ad angles that already lost in tests?
Record losing ad angles in ArcRoom with remember_failure and the numbers as the reason, and save winners with arcroom decide. Recall puts both in front of the next 'write variants' prompt, in Codex or Claude Code. You type the results in, because ArcRoom doesn't read the ad platform.
Also asked as: Codex keeps bringing back headlines that tested badly. How do I stop it? · How do I give an AI copywriter the results of past ad tests? · Can an AI agent remember which ad angles won and lost?
After each test, the agent records losing angles with remember_failure, with the numbers as the reason.
- Decision
- Saved decision
- Recall
Recall: failed angle 'save hours every week' (CTR 0.4% vs 1.1%, 2 tests)
Step by step
- After each test, the agent records losing angles with remember_failure, with the numbers as the reason.
- Winning angles are saved with arcroom decide.
- Recall puts both in front of the next 'write variants' prompt.
- When I switch to Claude Code for a batch, it gets the same history.
What the agent sees
Recall: failed angle 'save hours every week' (CTR 0.4% vs 1.1%, 2 tests)
Decision: lead with the problem ('your agents forget'), not time savedCompared with today's tools
Mem0 (OpenMemory MCP)
Connect Codex and Claude Code to OpenMemory and ask the agent to save results.
- Setup
- 1–2 hours
- Ongoing
- Remind the agent to search before each batch
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min (npx arcroom init)
- Ongoing
- None
With OpenMemory the agent has to choose to search before writing, and it often doesn't; ArcRoom recall puts the two losing angles in front of the prompt without being asked.
Where it stops
I type the results in; ArcRoom doesn't read the ad platform. A loser in one audience can win in another, so note the audience.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.