iflow-mcp_gobbyai-gobby

<!-- markdownlint-disable MD033 MD041 --> <p align="center"> <img src="logo.png" alt="Gobby" width="200" /> </p> <h1 align="center">Gobby</h1> <p align="center"> <strong>The control plane for AI coding tools.</strong><br> One daemon. All your agents. No more context window roulette. </p> <p align="center"> <a href="https://github.com/GobbyAI/gobby"><img src="built-with-gobby.svg" alt="Built with Gobby"></a> <a href="https://github.com/GobbyAI/gobby/blob/main/LICENSE.md"><img src="https://img.shields.io/badge/license-Apache%202.0-blue.svg" alt="License"></a> <a href="https://github.com/GobbyAI/gobby/stargazers"><img src="https://img.shields.io/github/stars/GobbyAI/gobby?style=flat" alt="Stars"></a> <a href="https://github.com/GobbyAI/gobby/issues"><img src="https://img.shields.io/github/issues/GobbyAI/gobby" alt="Issues"></a> </p> --- Gobby is a local-first daemon that unifies your AI coding assistants—Claude Code, Gemini CLI, Cursor, Windsurf, Copilot, and Codex—under one persistent, extensible platform. It handles the stuff these tools forget: sessions that survive restarts, context that carries across compactions, declarative rules that keep agents from going off the rails, and an MCP proxy that doesn't eat half your context window just loading tool definitions. **Gobby is built with Gobby.** Most of this codebase was written by AI agents running through Gobby's own task system and workflows. Dogfooding isn't a buzzword here—it's the development process. Note: Gobby is currently in alpha. Expect rough edges and breaking changes until the first stable release. ## Why Gobby? ### 🎯 A Task System That Actually Works If you've tried Beads or TaskMaster, you know the pain: databases that corrupt, agents that can't figure out the schema, worktrees that fall out of sync. Gobby's task system was designed by someone who got fed up with all of them. - **Dependency graphs** that agents actually understand - **TDD expansion** — describe a feature, ge…