Groovy turns Claude Code and Codex into a workforce. One orchestrator you talk to — from Groovy Chat, WhatsApp, or an API your customers use — and named agents that do the work in your repos, on your machines, with your keys.
5-day free trial · your API keys · macOS & Windows
Coding agents got good. Managing them didn't.
You're alt-tabbing between terminals, re-pasting context, babysitting runs. That's not orchestration — that's a second job.
Groovy Chat is the shared surface for your team, your company knowledge, and your live agents. Ask once, keep the context in the channel, and let the result come back to everyone.
Keep decisions, files, threads, and AI work together where the whole team can see the context.
Mention a Mind for company knowledge or an agent for real work. Groovy routes the request without making you switch tools.
Turn a message into a scheduled task, get live progress, and receive the result back in the same channel.
@Scoutsummarize today's customer blockers and ask Fixter to handle anything we can ship now.
Companies don't need another agent — they need a harness: model-agnostic, flexible, token-efficient, with a wiki-based memory you can actually read. Groovy deploys Cells — an orchestrator, its agents, and their memory — for customer service, sales, operations, and engineering. And instead of an agent working somewhere off to the side, your team talks with it, and to every other agent, in the same rooms you work in.
Claude Code & Codex workers in your repos, on your machines.
Slack-like rooms where humans, minds, and agents are teammates.
An endpoint and embeddable chat your own customers talk to.
WhatsApp and Telegram, same brain, same memory.
Team chat: humans, minds, and agents in one room — every delegation ends in a receipt, every side effect can require an approval.
Every channel is powered by a Mind you shape: its prompt, its models, its memory scope, and exactly which agents it may touch. Duplicating a harness for a new job is a clone, not a fork — customer support and internal ops can think with different souls on the same engine.
An agent is a real coding harness — Claude Code or Codex — bound to a repo on your machine. Give it a name, a workspace, a model, and the skills it should know.
Talk to one orchestrator. @mention an agent for precision, or describe the outcome and let it route, sequence, and hand context between agents for you.
Watch every agent work live in the grid. Risky work waits for your approval. Done work pings your phone. Transcripts, diffs, and costs are all on the record.
Every role gets its own model — the orchestrator brain, each agent, even your daily heartbeat digest. Pick from the frontier catalog or paste any model id. When the bill comes, ask the orchestrator to read it and it will tell you which agents can drop to a cheaper model without dropping quality.
claude-fable-5 · opus-4.7 · sonnet-4.6 · haiku-4.5
gpt-5.6-sol · gpt-5.6-terra · gpt-5.6-luna · gpt-5.5 · any-model-id
Flip on plan mode and an agent drafts read-only. Approve it and the plan lands in the repo — where Claude Code, Codex, and your teammates can all read it.
Markdown playbooks, synced from git, assigned per agent. Claude Code agents get CLAUDE.md context, Codex agents get AGENTS.md — automatically materialized on device.
Tell the orchestrator when and who: nightly test triage, weekly dependency bumps, or a 7:30 report. Each run uses that agent's harness, workspace, model, and skills while its connector machine is awake and online.
Dispatch from your phone, get pinged when work lands, and approve or reject with a reply. The harness doesn't stop because you stood up.
One command summarizes what an agent learned and briefs another — findings from Scout become marching orders for Fixter. No copy-paste archaeology.
Every token is attributed to an agent, a model, and an outcome. Ask the orchestrator to analyze it and it recommends cheaper model mixes that won't cost you quality.
Plus data integrations (Gmail, Calendar, ads platforms, Postgres, Firecrawl…) your agents can pull from — see the catalog.
Groovy holds it: local execution, your credentials, human approval on anything that can hurt.
Agents execute in your repos through a local connector. Your code never transits our servers.
Anthropic, OpenAI, Google, Azure, Bedrock — bring your own credentials. Groovy adds no token markup.
Destructive work waits for a human. Plans wait for review. Everything else just ships.
Each tagged release is mirrored publicly. Trust is something you can read.
Groovy Desktop bundles the harness and the local connector in a single signed app. Install, sign in, and your machine links itself. Agents keep running when the window closes; updates are one click, ChatGPT-style.
Prefer headless? The standalone connector still works everywhere.
Every account starts with a 5-day free trial. After that it's a flat yearly license — your model spend goes straight to your providers, with no Groovy markup in the middle.
Five days free. Your keys, your machine, your call.