Observed Signal · Aug 10, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Positive
Open-sourced Blackboard to Coordinate Parallel AI Sessions
A solo developer who runs multiple Claude Code sessions in parallel faced collisions where independent sessions conflicted over git branches and work. To solve this, they created a single shared "blackboard": a markdown file plus rules (claim-before-you-act, auto-recover stale claims, area map) and a small script that checks branch idle/commit state from git. The author found the approach maps to known concepts (Blackboard pattern, stigmergy, Kanban leases), discovered Claude Code's experimental "Agent Teams" (ephemeral teams), and then extracted and open-sourced the solution as agent-work-board on GitHub (MIT). Practical lessons included pushing claims immediately to use git as a lock, making the board row-editing rules explicit, avoiding hook mistakes that mask failures, and mitigating cloud build quota costs caused by frequent board commits.
Practical open-source tooling and patterns for coordinating multiple AI agent sessions are useful for developer workflows but are not industry-shifting; mentions of an experimental platform feature (Agent Teams) add relevance but no major platform policy or large commercial release is described.
Track GitHub Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Author implemented a single shared markdown "blackboard" file to coordinate multiple parallel Claude Code sessions, tracking backlog/in-progress/done and an area map.
- Rules implemented include "claim before you act", auto-recovery of stale claims after 7 days, and verifying branch state directly with git.
- The author wrote a small script (npm run board) that pulls branch idle time and ahead/behind status from git to detect stale claims.
- Claude Code has an experimental Agent Teams feature that creates ephemeral teams with shared task lists, but it is not persistent across independently-launched sessions.
- The author extracted the work-board into an open-source repository: https://github.com/dragon375014/agent-work-board (MIT).
Connected Companies & Entities
2 Entities mapped“👉 [https://github.com/dragon375014/agent-work-board] (MIT — use it anywhere, no attribution required)...”
“Title: I Built My AI Team a Blackboard — How to Stop Parallel Claude Sessions From Colliding Link: https://dev.to/dexterlung/i-built-my-ai-t...”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
AI Coding Agents Coordinate Across Machines via Files
An author built cross-session-talk, a small open-source file-based coordination layer that lets separate AI coding sessions (Claude Code on Windows, Claude Code on Linux, and Codex in tmux) exchange moderated turns, route messages, and converge on engineering decisions. The system uses append-only Markdown conversation files with a YAML header as the transport, a background watcher (talk-watcher.py) that injects terminal nudges, and simple discipline rules (turn counters, next field). The project hardened several bugs: a 12-hex turn-nonce and retry loop fixed lost updates over SSHFS, and a PreToolUse hook in Claude Code blocks direct edits to conversation files. The author reports emergent team-like behavior, improved accountability, and practical patterns for cross-host bug coordination, review, and integration handoffs. Code is published on GitHub under the MIT license. Publication date: 2026-05-27.
Turning Claude Code into a Parallel Engineering Team
A developer describes evolving an LLM-based coding assistant workflow from a single disciplined “Claude” developer (v1) into a parallel, agent-driven engineering team (v2). v2 centers on an orchestrator that never edits code directly and dispatches specialist subagents (architect, builders, QA critics, documentation librarian) that work in isolated git worktrees. Key design choices include an automated issue-maintainer that converts one-line ideas into structured issues, a hard handoff boundary at git commit, independent AI review gates, persona-based adversarial critics, and a cohort model driving up to ten concurrent pull requests. The full workflow and agent roster are open-sourced (MIT) at github.com/vlad-ko/claude-wizard. The author positions their role as a conductor who sets direction, resolves escalations, and performs the final human merge.
Anthropic Claude Code: Five Practical LLM Workflows
A solo founder describes five Claude Code workflows that proved useful in day-to-day development: using git worktrees to run parallel Claude sessions, delegating research to subagents to preserve session memory, enabling plan mode to review changes before edits, using resume/PR linking for continuity across sessions, and avoiding headless automation without checking billing. The post warns that Anthropic split Agent SDK billing from subscription on 2026-06-15 so headless CLI runs (e.g., `claude -p`) now bill against the SDK, not Pro/Max seats. The author links Anthropic docs and notes Anthropic shipped "dynamic workflows" in research preview on 2026-05-28, describing it as the next step beyond subagents.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.