Who it is forA developer who wants to change Cozy Clay itself or check its behavior before contributing.
The problemThe npx install runs the packaged build, so changing the studio code needs a source checkout.
The outcomeA local dev server at the studio URL and a passing test run, ready for code changes.
What you need first
- Node.js 22.19 or newer
- A Chromium browser
- An AI video model of your choice for the final render
Steps
- Run
git clone https://github.com/NomaDamas/CozyClay.git && cd CozyClay. - Run
npm install. - Run
npm run devand open http://127.0.0.1:5180/app/. - Run
npm testto check the suite before and after your change. - Read AGENTS.md for the contribution rules before you open a pull request.
Prompt for your agent
Using the NomaDamas/CozyClay repo, clone it, run `npm install`, `npm run dev`, and `npm test`, then report the test result. Expected output is a passing test run and the studio running at http://127.0.0.1:5180/app/. Verify that AGENTS.md has been read before any code change is proposed.
Caveat. The README gives no details on the codebase structure, so contributors should read AGENTS.md and docs/studio-ui-ia.md first.
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