What is Griyd?
Griyd is a shared workspace for software teams using AI coding agents to plan, build, review and ship product features. Agents connect over MCP, read the repository and open stories, and turn rough requests into specs the team can discuss before code is written. Developers use their own Claude Code, Codex or another MCP-compatible agent on their own machines, while Griyd keeps the work visible on a team board. It costs $15 per month for each developer using an agent, with other team members free and a $999 monthly cap.
Griyd Features:
Repository-Aware Specs: An agent reads the repository and open stories, then turns a rough request into a story with a spec before coding starts.
Team Spec Review: Teammates discuss specs on a shared board, where an agent can mention reviewers and suggest requested changes for someone to accept.
Shared Agent Skills: Agents load the same skills for specs, builds, QA and security over MCP, and changing a project's skill settings affects every agent on the team.
Local Agent Builds: An agent builds task groups on a story branch on the developer's machine, using the developer's own plan and agent usage.
Build Progress: Board cards show which agent is building a story and its progress, retaining the latest update when an agent goes offline and resuming when it reconnects.
CI Feedback: GitHub Actions and GitLab CI keep running as before, while webhooks report results to Griyd and failed job details go to the agent that built the story.
Griyd Benefits:
Shared Expectations: Agreeing on a readable spec before implementation gives teammates a chance to clarify what should ship before work begins.
Visible Ownership: Seeing agent assignments and progress together makes it easier to understand who is working on each story and where work stands.
Consistent Reviews: Using the same review and security skills across agents gives the team a common standard for checking work.
Keep Local Workflows: Developers can keep their preferred agent and local setup instead of moving builds into a shared Griyd environment.
Fewer CI Changes: Teams can receive build results without replacing or relocating their existing GitHub or GitLab CI workflows.
Use Cases:
Checkout Improvements: Plan and coordinate changes such as adding guest checkout, showing shipping costs before payment or supporting saved payment methods.
Parallel Feature Work: Give different agents and teammates separate stories, such as an order-history dark mode, a login rate limit and an order export.
Spec Approval: Bring product and engineering teammates together to review a feature spec and settle details such as keeping an existing checkout behind a flag.
Failed CI Runs: Send a failed job and step back to the agent that built a story so it can reproduce the failure, make a fix and submit again.
Agent Coordination: Use the board to track concurrent agent work and preserve story progress when a developer's agent disconnects.

