---
title: "Discussion on \"How I run support, marketing and code with a team of Claude Code and Codex agents\" | Hashnode"
description: "Discussion on \"How I run support, marketing and code with a team of Claude Code and Codex agents\". Brigade (brigade.lol) is an open-source app that runs a team of Claude Code and Codex teammates for support, marketing, sales and code."
url: "https://hashnode.com/posts/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents/6af73678be719d062e8b388e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I run support, marketing and code with a team of Claude Code and Codex agents](https://brigadelol.hashnode.dev/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents?utm_source=hashnode&utm_medium=feed)

Brigade (brigade.lol) is an open-source app that runs a team of Claude Code and Codex teammates for support, marketing, sales and code.

3d ago · 5 min read · brigadelol.hashnode.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#opensource](https://hashnode.com/tag/opensource)
-   [#claude-code](https://hashnode.com/tag/claude-code)
-   [#ai-agents](https://hashnode.com/tag/ai-agents)

## Written by

[Georges Petrov](https://hashnode.com/@gmpetrov)

@gmpetrov · Paris, France

  
[View profile](https://hashnode.com/@gmpetrov)

Building Brigade (brigade.lol): open-source AI teammates for support, marketing, sales and code

I build Brigade (https://www.brigade.lol), an open-source (MIT) app that gives a company a team of AI teammates for support, marketing, sales and code, each running Claude Code or Codex on your own Claude or ChatGPT plan.

## Responses 2

Markdown supported · ⌘↵ to post

[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.

[Charlie from xSquads](https://hashnode.com/@charlie-xsq)

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

Useful way to think about this is to treat each teammate like a new hire with a narrow role, not a shared omniscient assistant. For support, give it a small, redacted set of resolved tickets and require citations to the source plus a draft-only response. For marketing, separate approved product facts from campaign briefs and keep publishing behind a human review. For sales, use a CRM sandbox or read-only export; do not let an agent update records until you have an audit trail. I would also track one outcome per role—resolution time, qualified replies, or review edits—and sample failures weekly. That makes it easier to see which teammate is helping versus just producing activity.
