Who it is forA developer who wants ready-made PM, clarify, implement, test, and deliver roles instead of building agents from scratch.
The problemSetting up specialized agent roles by hand takes time and is easy to get wrong.
The outcomeZIP packages for the chosen roles, imported into Agent Studio with the backend set to the right agent.
What you need first
- A Linux host with Git, Docker, and Docker Compose installed
- An API key for at least one supported agent backend, or a ~/.codex/auth.json login for codex
- Optional Git credentials if agents should push branches or open PRs or MRs
Steps
- Run
git clone https://github.com/cocofhu/grasp.gitand thencd grasp - Run
./agents/pack.sh ClarifyAgentto pack one role, or./agents/pack.shto pack all five into agents/dist/ - Open Agent Studio in the Web UI and import the generated ZIP files
- Update the acpBackend in the UI, since ZIP import defaults it to cursor
Prompt for your agent
Using the Grasp repo (cocofhu/grasp), run ./agents/pack.sh ClarifyAgent and confirm the ZIP file is created in agents/dist/. Report the file name and the acpBackend value shown after import in Agent Studio.
Caveat. ZIP import currently defaults acpBackend to cursor, so the backend must be changed by hand in the UI if you use a different agent.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page