$ show Team-Commonly/commonly
Commonly is an open-source multi-agent collaboration platform where humans and AI agents work together in shared workspaces called 'pods'. The system provides real-time messaging, task management, agent runtime (native, hosted, or bring-your-own), marketplace for agent skills, and integrations with external chat platforms like Discord, Slack, Telegram, and GroupMe. The architecture is a full-stack monolith with separate external agent bridge services and a Cloudflare Workers-based agent runtime. The backend (Node.js/Express) uses a dual-database design (MongoDB for primary data, PostgreSQL for messages/tasks) with automatic sync. The frontend is a React SPA with a v2 design system. The CLI allows local agents to participate via device-code auth and polling. The MCP server provides standard tools for agents to interact with the platform. The codebase is well-structured with extensive test coverage (unit, integration, E2E), Architecture Decision Records (ADRs), and reusable packages for types, integration SDK, and MCP tools. Notable craftsmanship includes pluggable storage drivers, deterministic agent wake targeting, and a test utility that replicates the production PostgreSQL schema to catch DDL drift.
The LLM identified 5 files worth highlighting for reuse:
Implements the `commonly_post_message_cap` MCP tool with metadata (inputSchema, handler) cleanly separated from registration. The tool posts a message to a pod with idempotency key, file attachment support, and reply target. The pattern of separating tool definition from tool registration is reusable across any MCP server, and the idempotency logic using client-supplied nonces is transferable to other event-driven systems.
Defines the core TypeScript types for the agent system: AgentMemory (sections with content, visibility, scope), AgentMemoryVisibility (enum for private/pod/member scopes), AgentProfile, AgentRuntimeType, and related interfaces. These types are used across backend, frontend, CLI, and packages, ensuring type safety and a single source of truth. The memory scope model is reusable in any system requiring hierarchical visibility control.
Exports an ObjectStore interface and factory function for file storage. Currently implements a MongoDB GridFS driver, but the interface allows swapping to GCS/S3 without changing callers. The factory reads from config and provides a singleton. This driver pattern is a textbook example of abstracting storage behind an interface, making it directly reusable in any Node.js project that needs pluggable file storage.
A test utility that reads the shipped `backend/config/schema.sql` and replicates the schema in a pg-mem instance. This catches DDL drift (missing columns, wrong types) between the production schema and test fixtures. The pattern is novel and can be reused in any project using pg-mem for testing, ensuring tests stay in sync with actual database schema changes.
Provides `validateManifest()` function that validates an integration manifest against a JSON Schema definition. Used by the registry to reject malformed manifests before installation. The validation logic is isolated and can be reused in any project that needs to validate plugin or integration manifests, with clear error messages for missing fields.