Runs OpenAI's Codex coding agent locally on your computer from the command line.
Groove Dev
groove-ai · Agent
Groove sits between you and your AI coding agents and coordinates them from a dashboard on your own machine. It launches the AI coding tools you choose, which use their own subscription or API key, or run local models. Describe a project to a planner, launch the team it recommends, and each agent gets a role, a scope and a prompt. Agents signal before shared or destructive actions, and in Auto mode a project manager agent approves or rejects risky operations with reasons. It can also run on a VPS and be reached over an SSH tunnel or Tailscale.
Written by ooruby from the README of groove-dev 0.27.220.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Several coding agents share a project map and keep to their own areas of the code, so each new agent starts with the context it needs.
What you could do with it
- Describe a project to a planner agent and launch the team of agents it recommends with one click.
- Have the project manager agent approve or reject risky file operations before your agents carry them out.
- Run Groove on a VPS and manage your agents from a browser on your laptop through an SSH tunnel.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- python subprocess (AUTONOMOUS_AGENT_FRAMEWORK.md:110)
- node child_process (packages/daemon/src/api.js:8)
- node child_process (packages/daemon/src/axom-install.js:13)
- node child_process (packages/daemon/src/axom-remote.js:13)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Corrected after a reading by hand on 2026-10-10
- No shipped credentials: the automated note “The scan matched 1 credential-shaped string in the published files. Location withheld pending disclosure to the maker.” was withdrawn. AWS's documented example key, in a documentation table of redaction examples.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Open-source agent orchestration layer — the AI company OS. Local model agent engine (GGUF/Ollama/llama-server), HuggingFace model browser, MCP integrations (Slack, Gmail, Stripe, 15+), agent scheduling (cron), business roles (CMO, CFO, EA). GUI dashboard,
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.27.220, the file with digest sha512-yJOnXO6H2cD8CbxgUxx5IXcr+pf03FHNfHekkq7l7hSKI2wJ6u+F95VpYVot6CZ+zMkXXtxC0LDTQq52pFalvw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y groove-dev@0.27.220Pinned to 0.27.220, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- groove-dev
- Version read
- 0.27.220
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/groove-dev)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-05
Similar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.