Protocols
The 3 real inter-agent protocols this ecosystem uses. Filter by status:
A2A Agent2Agent
Lets one agent hand a task to another independently-hosted agent over HTTP, using a published agent card for capability discovery, rather than requiring both agents to share a process or a tool-calling loop. This repo uses it to expose subagentjobs.com's own crawl/query capabilities as a callable agent from outside this codebase.
e2m e2m (envelope-to-mailbox) protocol
A typed task and message envelope plus durable mailbox convention for coordinating multiple domain coworkers (design, engineering, data, finance, legal, HR, product, sales, operations) asynchronously, a DurableTask is written to a JSONL mailbox queue rather than requiring the dispatching and receiving agents to be online at the same time.
MCP Model Context Protocol
Standardizes how a single agent (this session, or a coworker binary) exposes tools and resources to a model, over a well-known stdio or HTTP transport, independent of which model or client is on the other end. This repo uses it both to expose this repo's own tools to Claude (crates/mcp-server) and to let Claude execute real operations on the developer's Mac (crates/engineering-coworker).
Machine-readable version: GET /api/protocols