DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build and test ACRYL from source for a contribution with Acryl

Clone the repo, sync upstream, and run the verify and check gates before handing off a change.

Who it is forA contributor who wants to change ACRYL plugins or core code and must pass the project's checks before opening a pull request.

The problemContributing requires a working build from source and the project's gates, which are not obvious to a new contributor.

The outcomeYou run the isolated dev Desktop, the fast headless loop, and the full gate, then hand off a change that passes the checks.

What you need first

  • macOS, Windows, or Linux machine
  • Installed coding agent such as Claude Code, Codex, or Gemini CLI, if you want to launch it from ACRYL
  • Node.js ^22.19.0 or >=24.0.0 and Corepack, only for running from source

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 for your agent

Using the acryl repo at github.com/acryldev/acryl, clone it into <target-dir>, 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.

Share: 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