Click any tag below to further narrow down your results
+ inter session messaging
(1)
+ software factory
(1)
+ agents
(1)
+ multi agent systems
(1)
+ vercel
(1)
+ vercel board
(1)
+ devtools
(1)
+ security
(1)
+ automation
(1)
+ open source economics
(1)
+ claude code
(1)
+ decentralized networks
(1)
+ principal agent problem
(1)
+ organizational evolution
(1)
+ duna
(1)
Links
Vercel has launched Board, an experimental, harness-agnostic message store that lets teams of AI agents claim tasks, post updates, and hand off work, with two-way sync to tools like Slack and GitHub. It came out of Vercel's own security-agent swarm and software factory, which merges over 50% of its PRs.
- Board is a headless store with a CLI and SDK where agents from different harnesses (Claude Code, Codex, LangChain, and others) can claim tasks, post progress, and record results in shared threads.
- It handles coordination details like task dependencies, leases on claimed work, scheduled follow-ups, and watchers that wake agents when a new reply or label change arrives.
- Access is controlled with per-channel grants, and sandboxed agents get board access without credentials inside the sandbox, with an audit trail of who did what.
Claude Code lets your independent sessions message each other to share findings, coordinate work, and report status without you manually copying information between terminals. Messages are delivered between tool calls and filtered through permission controls that prevent sessions from approving actions or changing configuration on each other's behalf. You can prompt Claude to send a message, or it'll detect when another session needs information and send it automatically.
- Claude Code sessions (v2.1.224+, macOS/Linux) can now message each other automatically or on request, using ListAgents/SendMessage tools, without interrupting running processes.
- Cross-machine messaging is one-way by default—remote or web sessions can only reply to existing threads, not initiate them, and replies from sessions without Remote Control arrive without a return address.
- Incoming messages are treated as system info, not user commands, so they can't approve permissions, change config, or run commands—permission prompts still trigger as normal.
- Inbound behavior is configurable per session via crossSessionInbound, with automatic naming (e.g. "myapp-3f") and /list-agents to see reachable sessions.
The article traces how the corporation solved coordination and liability issues in the industrial age and argues that internet-native networks need a new legal form. It introduces the DUNA, a proposed entity under emerging legislation, designed to align incentives and reduce overhead for decentralized organizations.
- Every prior organizational form (commenda, compagnia, VOC-style corporation) traded off liability protection, durability, and agent alignment—none solved all three at once.
- The VOC's Amsterdam board vs. remote traders problem shows the principal-agent gap is a recurring issue that each new organizational form must re-solve.
- Delaware's 1899 General Corporation Law became the dominant template, but corporations' coordination benefits came bundled with bureaucratic bloat and centralized control.
- The DUNA is a proposed legal entity (under congressional consideration) meant to give decentralized, on-chain networks legal recognition without reproducing traditional corporate management overhead.
The article shows how open source software breaks every textbook market rule—non-excludable, free to use, mostly single‐maintainer—and yet it thrives at massive scale. It walks through classic market failures and existing theories, argues none fully explain open source’s resilience, and critiques efforts to retrofit pricing signals onto a system built on gifts, reputation, and shared infrastructure.
- npm hosts 5M+ packages, mostly unfunded and maintained by lone contributors, with no grants or contracts backing them—yet the entire commercial software world depends on them.
- Classic market failures (free riding, tragedy of the commons) just don't manifest: downloads can jump from 1,000 to 10 million weekly without any increase in maintainer headcount, and over half of packages survive on a single maintainer.
- Existing economic theories (Lerner/Tirole's reputation signaling, Benkler's coordination costs, Von Hippel's user innovation) each explain fragments but fail to account for why maintainers keep triaging bugs on abandoned tools or why the ecosystem hasn't collapsed in three decades.
- Proposed fixes—bug bounties, sponsorship marketplaces, token rewards—all try to impose pricing onto a giftand-reputation system, relying on weak proxies like stars and download counts instead of answering who's actually sustaining the code.