# AI use cases for Grasp (cocofhu/grasp) Repo: [cocofhu/grasp](https://github.com/cocofhu/grasp) | Use cases: 5 | Page: https://dedupedai.com/use-cases/cocofhu-grasp/ Grasp is a self-hosted workspace that runs coding agents inside Docker sandboxes through visual FSM workflows with human approval gates. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run a coding task from one sentence to a reviewed change: https://dedupedai.com/use-cases/cocofhu-grasp/run-one-project-through-clarify-implement-review/ - Design a custom workflow with fail and rollback paths: https://dedupedai.com/use-cases/cocofhu-grasp/build-custom-fsm-workflow-with-rollback-paths/ - Review agent specs and diffs with an outside reviewer: https://dedupedai.com/use-cases/cocofhu-grasp/review-agent-output-with-share-links/ - Push an agent branch and open a PR or MR: https://dedupedai.com/use-cases/cocofhu-grasp/deliver-agent-branch-as-pull-request/ - Import the bundled role agents into Agent Studio: https://dedupedai.com/use-cases/cocofhu-grasp/import-bundled-role-agents/ ## How to run a coding task from one sentence to a reviewed change with Grasp Repo: [cocofhu/grasp](https://github.com/cocofhu/grasp) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Start a task from one prompt and approve the spec and diff at a human gate. **Who it is for:** A solo developer switching between several projects who wants an agent to clarify, build, and test a feature before reviewing it. **The problem:** Switching between IDEs makes it hard to track which project is running and where it stopped, and long agent chat logs bury the real changes. **The outcome:** A run that clarifies scope, implements and tests the change, then pauses at a gate where the developer approves or rejects it from the inbox. ### Steps 1. Run `git clone https://github.com/cocofhu/grasp.git` and then `cd grasp` 2. Run `./start.sh -d` and open the Web UI 3. Sign in with the demo account, then in the setup wizard select an agent backend and save its API key 4. Start a run from the home page with a single prompt 5. When the run pauses at a human gate, review the spec, preview page, or code diff in the inbox and approve or reject ### Prompt to paste into your agent ```text Using the Grasp repo (cocofhu/grasp), start a run for from the home page of a local Grasp instance. Confirm the run reaches the human gate, then report the spec and the code diff summary the reviewer will see. ``` ### Caveat This release requires a fresh install with an empty database and data directory, and the default login admin / demo1234 is for local evaluation only. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cocofhu-grasp/run-one-project-through-clarify-implement-review/ ## How to design a custom workflow with fail and rollback paths with Grasp Repo: [cocofhu/grasp](https://github.com/cocofhu/grasp) | Difficulty: Advanced | Time: 90 minutes | Basis: From the README Edit the FSM canvas to add nodes, guards, and fail or rollback edges. **Who it is for:** A developer or team lead who wants a repeatable delivery pipeline that retries or rolls back when a step fails. **The problem:** A fixed linear agent pipeline cannot route failed tests or rejected reviews back to the right step. **The outcome:** A published workflow where each node has explicit success, fail, and rollback edges, with when guards controlling transitions. ### Steps 1. Open the workflow canvas after the setup wizard finishes 2. Add agent, input, output, assign, branch, or human gate nodes as needed 3. Connect nodes with success, fail, and rollback edges and add when guards where needed 4. Declare the required artifacts for each node so the engine knows what must be submitted 5. Publish the workflow and start a run from the home page to confirm the path ### Prompt to paste into your agent ```text Using the Grasp repo (cocofhu/grasp), create a workflow in on the FSM canvas that adds a rollback edge from the test node to the implement node. Verify the rollback edge is saved and report the node list and edge list. ``` ### Caveat The README does not document the exact steps for declaring required artifacts on a node, so check the Concepts guide before relying on that step. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cocofhu-grasp/build-custom-fsm-workflow-with-rollback-paths/ ## How to review agent specs and diffs with an outside reviewer with Grasp Repo: [cocofhu/grasp](https://github.com/cocofhu/grasp) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Let a reviewer without an account approve a gate through a one-time share link. **Who it is for:** A developer who needs a client, lead, or teammate without a Grasp account to approve a pending run. **The problem:** Parallel agent output is hard to read, and reviewers outside the workspace cannot easily check the spec or preview. **The outcome:** A reviewer opens a one-time link, inspects the spec or preview, and approves or rejects the gate without signing in. ### Steps 1. Open a run that is paused at a human gate in the inbox 2. Create a one-time share link for the approval 3. If the server runs behind a reverse proxy, preserve the Host header, for example with `proxy_set_header Host $host` in nginx 4. Send the link to the reviewer 5. Confirm the decision appears in the run timeline after the reviewer responds ### Prompt to paste into your agent ```text Using the Grasp repo (cocofhu/grasp), review a paused run in and create a one-time share link for its human gate. Confirm the link uses the expected host and report the gate name and its spec summary. ``` ### Caveat Share links are generated from the Host header, so a misconfigured reverse proxy will produce links that do not work, as the deployment notes explain. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cocofhu-grasp/review-agent-output-with-share-links/ ## How to push an agent branch and open a PR or MR with Grasp Repo: [cocofhu/grasp](https://github.com/cocofhu/grasp) | Difficulty: Advanced | Time: 90 minutes | Basis: From the README Let a run push a branch and open a pull or merge request through gh, glab, or SSH. **Who it is for:** A developer who wants the agent's approved change to reach the repository as a reviewable PR or MR without manual steps. **The problem:** Moving an approved agent change into a pull request is repetitive and easy to forget after review. **The outcome:** A branch pushed by the sandboxed agent and a PR or MR opened after the human confirm step. ### Steps 1. Run `./start.sh -d` and sign in to the Web UI 2. In the setup wizard or Project Credentials, save Git credentials for the repository (optional) 3. Use a workflow that ends with a delivery step after the human confirm gate 4. Start a run and approve the change at the gate 5. Check the repository for the pushed branch and the opened PR or MR ### Prompt to paste into your agent ```text Using the Grasp repo (cocofhu/grasp), run a delivery workflow for that pushes a branch and opens a PR after human confirmation. Verify the branch name and PR link, and report both. ``` ### Caveat The README says agents can open PRs or MRs via gh, glab, or SSH but does not document which CLI must be configured for each Git host, so confirm that before running. Risk, credentials: Git tokens and SSH private keys must be stored only in workspace credentials settings, since they are injected per run and must never be committed to the repository. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cocofhu-grasp/deliver-agent-branch-as-pull-request/ ## How to import the bundled role agents into Agent Studio with Grasp Repo: [cocofhu/grasp](https://github.com/cocofhu/grasp) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Pack the five role agents as ZIP files and import them into Agent Studio. **Who it is for:** A developer who wants ready-made PM, clarify, implement, test, and deliver roles instead of building agents from scratch. **The problem:** Setting up specialized agent roles by hand takes time and is easy to get wrong. **The outcome:** ZIP packages for the chosen roles, imported into Agent Studio with the backend set to the right agent. ### Steps 1. Run `git clone https://github.com/cocofhu/grasp.git` and then `cd grasp` 2. Run `./agents/pack.sh ClarifyAgent` to pack one role, or `./agents/pack.sh` to pack all five into agents/dist/ 3. Open Agent Studio in the Web UI and import the generated ZIP files 4. Update the acpBackend in the UI, since ZIP import defaults it to cursor ### Prompt to paste into your agent ```text 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cocofhu-grasp/import-bundled-role-agents/