baycclark.eth
3.9K posts

baycclark.eth
@baycclark
web3. hella protocol. 🐋 | hella.base.eth swets.eth baycclark.eth | behind the scenes of your favorite T1


Nowadays, I’m building QuadWork, an agent app where you run a team of 4 agents that autonomously handle queued tasks by chatting with each other. At this pace, I think I can introduce it in about two weeks. I might open-source it if there’s enough interest. With this tool, your dev workflow looks like this: 1. You discuss tasks with the HEAD agent, and it creates issue tickets from your requests. 2. Once you’ve built up enough tickets, ask the HEAD to generate a batch—then it prepares an OVERNIGHT-QUEUE.md with an optimized task order. 3. That’s it. Go to sleep, watch a movie, or spend time with your loved ones. Your AI team handles the rest: pick up tickets → implement → open PR → 2 reviewer agents review → iterate until approval → merge → move to the next task… until everything is done. The quality is surprisingly strong when you mix models across the 4 agents. My usual setup: HEAD: GPT 5.4 DEV: Opus 4.6 REVIEWER1: GPT 5.4 REVIEWER2: OPUS 4.6 Oh, and you can even connect Telegram to QuadWork to monitor progress and control it remotely. If you’re interested in this being open source, share this post and drop a comment, and feel free to follow my GitHub: github.com/realproject7 If there’s enough demand, I’ll release QuadWork as open source. You know what? Even while I’m writing this post, my QuadWork team just finished a batch of 3 tickets. Everything in that screenshot is already done 🤣




Kind of nuts that everyone I know from the crypto industry is basically completely obliterated right now

Hourly Top Mints Bored.Ai MemberChip: 859 Waifu Moe Club: 582 BloodShed Bears Gen1: 317 BYOCraft: 140 MIRL OFFICIAL NFT: 64 ChubbyKaijuDAO Invasion: 62 MunchieMafiaNightClub: 62 STAPLEVERSE - HOOD SQUAD - PHASE 2 of 3: 54 Agent1: 52 0xAzukiApes: 51







I built a local AI agent workflow with 8 agents across 2 teams—and yeah, it keeps shipping while I sleep. I just wanted something that could queue tasks and actually execute them overnight (or while I’m out with family), without relying on hosted tools. Everything runs on my MacBook. Each team is 4 agents: - 1 Team Head (coordinates, creates issues, merges PRs) - 1 Full-Stack Builder (writes all the code) - 2 Senior Reviewers (independent reviews, can veto) I mix models by role—Claude Opus for building, GPT for coordination and reviews. Turns out having different model “perspectives” on the same code gives way better review quality than using a single model for everything. GitHub is the source of truth. Every task = issue → PR → 2 reviewer approvals → merge. Branch protection makes sure no agent can skip the process. Agents chat in their own system (AgentChattr), but all outputs stay in GitHub. Now I just queue tasks before bed… and wake up to merged PRs with full review trails. We’re also re-inventing Hunt Town Discord into a more agentic builder community—so we can share setups like this and grow together. discord.gg/hunt-town






