Multi-Agent Trading Council System Using GPT-5.1 and Claude 4.6
System Architecture and Components
A developer has implemented a multi-agent trading system designed to force rigorous justification of trading setups before execution. The system uses ZagiHQ for orchestration, specifically chosen for its agent locking capabilities and avoidance of manual VM provisioning or container management. Internally, multi-agent coordination is handled by OpenFang, which automates communication between nodes.
Workflow Breakdown
The system operates through four distinct stages:
- The Scouts: Three parallel agents gather data: one scrapes high-signal X (Twitter) accounts, one monitors macro news from Bloomberg/Reuters feeds, and one pulls technical indicators from TradingView. All data is normalized into a shared schema before processing.
- The Council: Three models analyze the data simultaneously: GPT-5.1 handles pattern recognition, Claude 4.6 Opus handles macro/technical reasoning, and Claude 4.6 Sonnet checks logic consistency.
- The Judge: This gatekeeper kills any trade where there's meaningful disagreement on Entry, Stop Loss, Take Profit, or Risk-to-Reward ratio. There is no override mechanism.
- Human-in-the-loop: Surviving setups trigger a Telegram alert with full model breakdowns. All trades require manual approval, and the system is currently paper trading only.
Initial Observations and Current Challenges
The developer reports that single models tend to anchor on initial interpretations and rationalize them, while the multi-agent approach with reasoning layers filters out significant noise. Setups that pass through feel "sturdier" and harder to critique.
Three specific problems are being addressed:
- X (Twitter) sentiment value: Questioning whether the signal-to-noise ratio justifies the overhead, even with LLM pre-filtering. Considering deprioritization unless clear macro catalysts drive chatter.
- Consensus trap: Concern that three-way agreement might reflect shared training biases rather than genuine signal. Considering adding a "Devil's Advocate" agent specifically prompted to find reasons not to take trades.
- Judge enhancement: Currently only kills trades based on direction and R:R. Considering adding volatility regime checks and minimum conviction thresholds (possibly via logprobs if reliable).
The developer is willing to share schemas and discuss the workflow with others building similar systems.
📖 Read the full source: r/clawdbot
👀 See Also
MAGELLAN: A 15-Agent Autonomous Scientific Discovery System Built on Claude Code
MAGELLAN is a 15-agent autonomous scientific discovery system built entirely on Claude Code. It uses Opus for deep reasoning and Sonnet for structured tasks, generating cross-disciplinary hypotheses without human direction, with 260 hypotheses proposed and 60% killed by adversarial validation in 19 sessions.
Claude-Skills Maintainer Seeks Feedback on 181 Agent Skills Library
Reza, maintainer of claude-skills, is asking the community for feedback on his open-source library containing 181 agent skills, 250 Python tools, and 15 agent personas that work across 11 AI coding tools. He's questioning whether the isolated skill approach is effective and wants input on missing skills, persona-based agents, and tool integrations.
Open-source framework for persistent AI agent memory with local storage and graph-based retrieval
A developer has been building an open-source framework for persistent AI agent memory that stores data locally as Markdown files, uses wiki-links as graph edges, and implements Git for version control. The system features four-signal retrieval and graph-aware forgetting based on ACT-R cognitive science.
DocMason: Local Agent Knowledge Base for Complex Office Files
DocMason is a repo-native agent app that builds local knowledge bases from complex office documents like PPTX, DOCX, Excel, and PDFs. It runs entirely within Codex or Claude Code, maintaining document structure and providing traceable answers with provenance.