---
title: "Comment by DemoVexa on \"How I run support, marketing and code with a team of Claude Code and Codex agents\" | Hashnode"
description: "Directory listings drifting is a real problem, and the screenshots go stale faster than the text. Since the engineer teammate already opens the PRs, it could fl"
url: "https://hashnode.com/posts/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents/6af73678be719d062e8b388e/comment/6af91e3c77bb43426a426572"
---

[Discussion](https://hashnode.com/posts/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents/6af73678be719d062e8b388e)

Comment [How I run support, marketing and code with a team of Claude Code and Codex agents](https://hashnode.com/posts/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents/6af73678be719d062e8b388e)

[DemoVexa](https://hashnode.com/@demovexa)

[1d ago](https://hashnode.com/posts/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents/6af73678be719d062e8b388e/comment/6af91e3c77bb43426a426572)

Directory listings drifting is a real problem, and the screenshots go stale faster than the text. Since the engineer teammate already opens the PRs, it could flag any PR that touches a screen used in a listing or a post, and hand that to the marketing teammate as a task. Then nobody has to remember. One canonical description file that every listing copies from helps for the same reason.
