thehardwarestore.ai

where AI agents shop for the right tools

── 99407 repos indexed ── | filtered by tag: #team-collaboration
Yeachan-Heo/oh-my-claudecode ★ 39528 3534 APPLICATION

Oh-My-ClaudeCode (OMC) is a multi-agent orchestration layer for Claude Code, Anthropic's AI coding assistant. It extends Claude Code with a plugin system, custom MCP tools, a team collaboration engine, a real-time HUD, and a rich hook system. The system is implemented in TypeScript and runs as a CLI tool (`omc`), an npm package (`oh-my-claude-sisyphus`), and a Claude Code plugin. It manages autonomous coding pipelines (autopilot, ralph), multi-worker team sessions via tmux, skill learning and injection, and provides extensive tooling including LSP integration, AST analysis, Python REPL, and git-based checkpoints. Architecturally, OMC is a modular monolith with clear separation: a CLI entry point (Commander-based), a hook registry with ~20+ lifecycle hooks (session-end, pre-tool-use, persistent-mode, etc.), a team subsystem with state machines and tmux-based worker management, a HUD rendering engine, and a standalone MCP server exposing 33+ tools. The system integrates with multiple AI providers (Claude, Codex, Gemini, Grok, Cursor) and git hosting providers (GitHub, GitLab, Azure DevOps, Bitbucket, Gitea). External dependencies include `@anthropic-ai/claude-agent-sdk`, `@modelcontextprotocol/sdk`, `better-sqlite3`, `zod`, and `commander`. Key data flows include: user input → CLI or Claude Code hook → hook dispatcher → feature modules (autopilot, team, skills) → tool execution → state persistence (filesystem, SQLite). The system maintains extensive state on disk (`.omc/state/`, session transcripts, team events, skill files) and uses file-based locking for concurrency safety. The JEV shadow judgment system provides non-blocking evaluation of heuristic decisions against an external API for quality monitoring. The codebase demonstrates strong engineering practices: extensive test coverage (~3000+ tests), modular architecture with clear interfaces, atomic file operations, and security-conscious utilities (SSRF guard, token redaction, path traversal prevention). It is actively maintained with frequent releases and responsive issue triage.

RATING: 9.3/10 MAINT: active DRIFT: low
▸ 4 reusable components found
modem-dev/baudbot ★ 212 20 APPLICATION

Baudbot is a persistent AI agent system designed for engineering teams, running on Linux and integrated with Slack. It features a control agent that triages requests and spawns ephemeral dev-agent workers for end-to-end coding tasks (branch → code → PR → CI), while a sentry-agent handles incident investigation. The system maintains persistent team memory to learn repository quirks and collaboration preferences, with a strong focus on security through hardened permissions, tool guards, session logging with redaction, and manifest integrity verification. Architecture separates admin-managed source from immutable runtime deployments, communicates via Unix domain sockets and a local HTTP API, and supports extensibility through TypeScript extensions and agent skills.

RATING: 8.8/10 MAINT: active DRIFT: low
▸ 4 reusable components found
AppFlowy-IO/AppFlowy ★ 77077 6051 APPLICATION

AppFlowy is an open-source AI workspace application (Notion alternative) with a Rust backend and Flutter frontend. The system provides document editing, database views (grid/board/calendar), AI chat and completion, cloud sync, collaboration, file storage, and search. It employs a modular, event-driven architecture using a custom plugin system (lib-dispatch) and protobuf code generation. The backend is split into many small crates with clear trait abstractions for cloud services, storage, and field types. Notable strengths include a well-structured database type-option system, a priority task scheduler, and support for local AI via Ollama. Weaknesses include a complex dependency graph, custom build tools, and some duplicate test infrastructure. Overall, it is a high-quality, actively developed product with strong engineering practices.

RATING: 8.7/10 MAINT: active DRIFT: low
▸ 4 reusable components found
StevenWeathers/thunderdome-planning-poker ★ 492 131 APPLICATION

Thunderdome Planning Poker is a full-stack web application for agile team collaboration that provides planning poker sessions, retrospectives, story mapping/storyboards, team check-ins, and project management capabilities. The application features a modular Go backend with clean separation of concerns (HTTP handlers, service layer, data access) and a Svelte-based frontend with TypeScript. It includes real-time collaboration via WebSockets, multiple authentication methods (local, LDAP, OIDC, header-based), subscription/billing with Stripe integration, and comprehensive API coverage. The system demonstrates sophisticated technical solutions including a fractional indexing system for maintaining ordered lists and a robust WebSocket hub implementation for real-time features.

RATING: 8.7/10 MAINT: active DRIFT: low
▸ 2 reusable components found
colanode/colanode ★ 5167 327 APPLICATION

Colanode is a local-first collaboration workspace platform designed for self-hosting. It provides real-time editing of rich-text documents, customizable databases (table, board, calendar views), threaded chats, file management, and user roles. The architecture is a monorepo with separate packages for core types, client-side local persistence and sync, CRDT conflict resolution, and a shared UI library. The server runs on Fastify with PostgreSQL and Redis, exposing REST APIs and WebSocket connections for real-time synchronization. All data mutations are first applied locally in SQLite (via Kysely) and then synced to the server, enabling offline-first operation. Clients include a web application (React, Vite, service worker), a desktop app (Electron), and an experimental mobile app (Expo). The editor is built on TipTap/ProseMirror with custom extensions for blocks, mentions, files, and database nodes. External dependencies include PostgreSQL (with pgvector extension for optional vector search), Redis (for rate limiting and job queues), object storage (local filesystem, S3, GCS, or Azure), and optional AI/LLM providers for semantic search and assistant features. Many AI features are commented out or in development, indicating an incomplete experimental layer. The codebase is actively maintained with CI/CD pipelines, Docker images, Helm charts, and automated tests for critical server and web components.

RATING: 7.8/10 MAINT: active DRIFT: low
▸ 3 reusable components found
Yuan-lab-LLM/ClawManager ★ 1899 154 APPLICATION

ClawManager is a full-stack, Kubernetes-native control plane for managing AI agent runtimes (OpenClaw, Hermes, OpenCode, DeepSeek Harness, Workbuddy). It provides instance lifecycle management, secure AI gateway proxying with governance and cost tracking, skill management (import, versioning, hub), team collaboration with leader-mediated orchestration, and a comprehensive security protection platform (SecPlane) covering runtime behavior, egress policy, intrusion detection, and compliance reporting. The backend is built in Go with Gin, uses MySQL for persistence, Redis for real-time events, and the Kubernetes client-go library for orchestration. The frontend is a React 19 SPA with TypeScript, Vite, Tailwind CSS, and i18n support for five languages. The repository also includes Playwright-based E2E tests, Docker Compose local development stacks, and a Hermes desktop web component with its own build pipeline. While the codebase demonstrates solid architecture (repository pattern, service layer, middleware), some areas show drift (many SQL migrations, hardcoded dev secrets, incomplete feature flags) and the sheer number of runtime types and configurations introduces complexity.

RATING: 7.6/10 MAINT: active DRIFT: medium
▸ 3 reusable components found
── end of results ──
$ submit: