# AI use cases for Acryl (acryldev/acryl) Repo: [acryldev/acryl](https://github.com/acryldev/acryl) | Use cases: 5 | Page: https://dedupedai.com/use-cases/acryldev-acryl/ ACRYL is an open source agentic development environment where one persistent workspace holds the project context while any coding agent can plug in and be swapped out. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Keep one project context across coding agents: https://dedupedai.com/use-cases/acryldev-acryl/keep-one-project-across-coding-agents/ - Run several agents and act only when one needs you: https://dedupedai.com/use-cases/acryldev-acryl/run-several-agents-without-babysitting-terminals/ - Review agent diffs line by line and send comments back: https://dedupedai.com/use-cases/acryldev-acryl/review-agent-diffs-and-send-comments-back/ - Diagnose and repair an ACRYL install that will not boot: https://dedupedai.com/use-cases/acryldev-acryl/diagnose-and-repair-a-broken-acryl-install/ - Build and test ACRYL from source for a contribution: https://dedupedai.com/use-cases/acryldev-acryl/build-and-test-acryl-from-source/ ## How to keep one project context across coding agents with Acryl Repo: [acryldev/acryl](https://github.com/acryldev/acryl) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Move between Claude Code, Codex, and Gemini CLI on the same project without re-setting context. **Who it is for:** A developer who uses several coding agents for different tasks and loses the thread of the work every time they switch agents. **The problem:** Each agent keeps its own chat, so switching agents means rebuilding setup, context, and task history from scratch. **The outcome:** One ACRYL workspace holds the project, its tasks, and its handoffs, and each agent enters and leaves that same workspace. ### Steps 1. Run `curl -fsSL https://acryl.dev/install | bash` to install the CLI and add `acryl` to your PATH. 2. Run `acryl` to open the terminal surface. 3. Add your project as a project in the left panel, then open a git worktree for the task if needed. 4. Launch an agent such as Claude Code, Codex, or Gemini CLI from the built-in catalog into that project. 5. When you want a different agent, launch another one from the same roster in the same project and keep working in the same canvas. ### Prompt to paste into your agent ```text Using the acryl repo at github.com/acryldev/acryl, set up ACRYL on this machine and open the project at as a project. Report the project name shown in ACRYL and list which agents from the roster are available; verify the project appears in the left panel before you finish. ``` ### Caveat The README says ACRYL is in active early development and interfaces may change, so check the current release before relying on a workflow. 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/acryldev-acryl/keep-one-project-across-coding-agents/ ## How to run several agents and act only when one needs you with Acryl Repo: [acryldev/acryl](https://github.com/acryldev/acryl) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Use the attention queue to see the moment an agent needs input across parallel sessions. **Who it is for:** A developer running multiple agents on separate tasks who keeps checking terminals to see which agent is waiting. **The problem:** Parallel agent sessions each wait silently for input, so you lose time checking every terminal. **The outcome:** An attention queue tells you when an agent needs you, so you can answer that session and leave the others running. ### Steps 1. Install ACRYL from the Desktop release table or with `curl -fsSL https://acryl.dev/install | bash`. 2. Open a project and launch two or more agents from the built-in roster. 3. Set up the Claude Code hooks, which the README says ship today, so the attention queue receives agent prompts. 4. Leave the agents running and watch the attention queue for the session that needs you. 5. Open that session tile on the canvas, respond, and return to the queue. ### Prompt to paste into your agent ```text Using the acryl repo at github.com/acryldev/acryl, launch two Claude Code sessions in the project at inside ACRYL. Report which session the attention queue flagged first and verify that the queue updates when one session asks for input. ``` ### Caveat The README states the attention queue currently works with Claude Code hooks only, so other agents may not raise alerts yet. 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/acryldev-acryl/run-several-agents-without-babysitting-terminals/ ## How to review agent diffs line by line and send comments back with Acryl Repo: [acryldev/acryl](https://github.com/acryldev/acryl) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Comment on an agent's diff in ACRYL and send those comments straight back to the agent. **Who it is for:** A developer who lets an agent edit code and wants to review the changes before accepting them, without copying notes into a separate chat. **The problem:** Feedback on agent changes usually lives in a separate chat or an external review tool, so the agent often misses the exact lines you flagged. **The outcome:** You review diffs inside the canvas, attach line-by-line comments, and send them to the agent in the same session. ### Steps 1. Open the project in ACRYL and let an agent session make changes in a git worktree. 2. Open the diff for the changed files in a canvas tab. 3. Add review comments on the specific lines that need work. 4. Send the comments back to the agent from the diff view. 5. Check the updated diff and repeat until the changes are accepted. ### Prompt to paste into your agent ```text Using the acryl repo at github.com/acryldev/acryl, open the diff for the worktree at in ACRYL, add a review comment on one changed line, and send it to the agent. Report the line number and the agent's reply, and verify the comment appears in the session. ``` ### Caveat The README describes the diff review feature in general terms only, so confirm the exact send-back behavior in the documentation for your release. 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/acryldev-acryl/review-agent-diffs-and-send-comments-back/ ## How to diagnose and repair an ACRYL install that will not boot with Acryl Repo: [acryldev/acryl](https://github.com/acryldev/acryl) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Use Acryl doctor and Acryl repair to find and fix a broken install, with backups and undo. **Who it is for:** A user whose ACRYL install fails to start after an update or a partial install and who needs to recover without reinstalling everything. **The problem:** A broken install blocks the workspace and agents, and reinstalling may lose settings. **The outcome:** The install is diagnosed, repaired with backups kept, and can be undone if the repair causes problems. ### Steps 1. Run `acryl doctor` to diagnose the install. 2. Read the findings and confirm which problems the report lists. 3. Run `acryl repair` to fix the install. 4. Run `acryl` to confirm ACRYL boots. 5. If the repair causes a problem, use the undo option that the README says comes with repair. ### Prompt to paste into your agent ```text Using the acryl repo at github.com/acryldev/acryl, run the ACRYL diagnostic on this machine, then run the repair if problems are found. Report the list of issues found and whether ACRYL boots afterward, and verify with `acryl` that the app starts. ``` ### Caveat The README does not describe the undo command syntax, so check the documentation before relying on it. 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/acryldev-acryl/diagnose-and-repair-a-broken-acryl-install/ ## How to build and test ACRYL from source for a contribution with Acryl Repo: [acryldev/acryl](https://github.com/acryldev/acryl) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README Clone the repo, sync upstream, and run the verify and check gates before handing off a change. **Who it is for:** A contributor who wants to change ACRYL plugins or core code and must pass the project's checks before opening a pull request. **The problem:** Contributing requires a working build from source and the project's gates, which are not obvious to a new contributor. **The outcome:** You run the isolated dev Desktop, the fast headless loop, and the full gate, then hand off a change that passes the checks. ### Steps 1. Clone the repository from github.com/acryldev/acryl and change into it. 2. Run `corepack pnpm run upstream:sync`. 3. Run `corepack pnpm install --frozen-lockfile`. 4. Run `corepack pnpm run verify` for the fast typecheck and test loop, then `corepack pnpm dev` to launch the isolated Desktop. 5. Run `corepack pnpm run check` before handoff and read AGENTS.md and the orientation spec first. ### Prompt to paste into your agent ```text Using the acryl repo at github.com/acryldev/acryl, clone it into , sync upstream, install with the frozen lockfile, and run the verify script. Report the pass or fail result of the typecheck and tests, and verify that `corepack pnpm run check` completes before you finish. ``` ### Caveat The README says the deepseek-harness folder is a pinned upstream that must not be edited from a feature branch, so keep changes out of that folder. 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/acryldev-acryl/build-and-test-acryl-from-source/