Run your coding agents as a software factory, each task in its own workspace and tracked from ticket to trace.

Supports Claude Code · Codex · OpenCode · Linear · GitHub · Gitea · Langfuse

🌳 Overview

• Coding is no longer the slow part. Deciding what to build is. Parallel agents hit checkout conflicts and laptop limits. Grove turns your agents into a software factory. Turn tickets into outcomes.
• Give each task its own workspace. Each agent gets a worktree and branch. Agents report phases for their workspace and each attached ticket. See what's planned, built or verified across the fleet.
• Choose how each agent runs. Run agents in their usual host environment or a container defined by your repository's .devcontainer/. Containers provide separate services and ports with resource limits.
• Choose where the work runs. Concurrent tests and builds compete for CPU and memory. Reuse your container configuration on a shared team machine or serverless cloud to free your laptop.
• Let the tracker start the work. Assign an issue and Grove starts its workspace. Progress returns to the same ticket. Follow the task where you defined it.
• Show it instead of describing it. Annotate a screenshot or draw a diagram with your agent. Approve the diagram or mockup and attach it to a ticket to coordinate your fleet.

✨ Features

Terminal UI and CLI Use the terminal UI to see which agents need you. The CLI autocompletes commands and live workspace names. People and agents can launch, pause and resume work from the shell. Docs → · CLI →
The whole fleet in your browser Follow headless agent sessions from any browser. Review the transcript beside the branch and diff. Upload files or annotate screenshots to show what needs changing. Edit a draw.io diagram together without leaving the workspace. Docs →
Containerized agents Run each agent in a containerized sandbox for its task. Separate files and services keep parallel work from colliding. Set CPU and memory limits per task. Scale each agent container independently on serverless cloud platforms as tasks arrive. Docs →
Drive Grove from any agent An orchestrator uses Grove's MCP tools to launch agents, track progress and steer the fleet. Worker agents use the mailbox to discover peers and exchange messages as tasks run in parallel. They can coordinate without sharing a checkout. Docs →
Status lands on the ticket Every ticket a Grove workspace works gets one comment, rewritten in place as the work moves. The phase, the checklist and the latest commit stay current where your team already looks. Nobody has to ask, and there is no second dashboard to check. Docs →
Audit and tune the whole fleet Every agent turn becomes a Langfuse trace. A small local decision model labels each observation, such as why a shell command ran, with a confidence score. Add thumbs up or down from Grove, then calibrate the labels against human judgement. Docs →

Also in the box:

• Branch-aware lifecycle. Create, pause, resume, respawn or kill. Pausing keeps the branch.
• Configuration cascade. A committed .grove/config.json sets team defaults, overridable locally.
• Per-agent model selection. Pick a model per workspace.
• Session recovery. Sessions survive restarts and reattach, and a lost one remaps in a click.
• Feedback and evaluations. Human ratings and decision-model scores in Langfuse.
• Ticket providers. Link Linear, GitHub or Gitea tickets to show workspace phase and status.
• Push notifications. Get pinged when an agent finishes a turn or needs you.
• Attachments and annotation. Attach files for your agent, and draw annotations on images.
• Diagram collaboration. Sketch mockups and specs with your agent in draw.io.
• Subscription windows. Track each plan's usage, reset and burn rate. See which limit comes first.
• Usage trends. Daily tokens, model cost and latency, and where agents spend time across projects.

🚀 Get started

Needs git and tmux. Install with uv:

uv tool install grove-factory

cd path/to/your/repo
grove config init               # scaffold .grove/config.json
grove                           # launch the TUI

• Try it first: uvx --from grove-factory grove
• No uv? pipx install grove-factory, or see every install path.

🤖 Let an AI agent configure Grove for you

Hand this prompt to Claude Code, Codex or any coding agent. It configures Grove with you and checks every field against your installed version.

Read https://raw.githubusercontent.com/bearlike/Grove/current/src/grove/skills/configuring-grove/SKILL.md

It is the skill for configuring Grove, a software factory for coding agents.
It covers the six-layer cascade, agents, init scripts, containers and ticket
providers.

Help me write my Grove user and project config, then verify every field
against my installed version with `grove config schema --stdout`.

---

🤖 Skills for Claude Code

claude plugin marketplace add https://github.com/bearlike/Grove.git

Teach your agent to drive Grove and to configure it for a project

Grove's skills ship from the repository that implements them, so they never drift from the code. They are the same files grove skills install copies into a tool's skills directory; grove skills list --details is the full roster.

Skill	For
using-grove	Driving a fleet from outside. CLI verbs, MCP tool ids, ticket and PR linking
leading-in-grove	Leading a fleet of teammates toward one deliverable. Splitting the work, check-ins, verification, teardown
working-in-grove	The agent inside a workspace, reporting phase and keeping attached tickets current
configuring-grove	The config cascade, agents, init scripts, containers, ticket providers
reinstalling-grove	When an update did not take
collaborating-on-diagrams	Editing a .drawio file together with a person, through managed reads and writes
mocking-up-in-grove	Getting a frontend mockup approved as a picture before any code exists

📚 Documentation

Full documentation lives at https://factory.mewbo.com/.

Section	Covers
Get Started	Install, prerequisites, first run, verify.
Configure	Project setup, agents, init scripts, configuration reference.
Use	TUI tour, CLI, web IDE, authentication, daily workflow.
Capabilities	Lifecycle, branch provenance, live activity, status semantics, configuration cascade.
Develop	Architecture, public API, engineering principles, contributing, design system.
Troubleshooting	Symptom → cause → fix for common failures.

🤝 Contributing

Share bugs and ideas on the issue tracker, or contribute using the contributing guide and CLAUDE.md.

📄 License

MIT © Krishna Alagiri.