DEDUPEDWhat do you want to do?
4 use cases
-
Start a governed agent job from a chat plan
Describe a change in chat, confirm the proposed plan, and let agents run it in sandboxes.
View prompt
In the wicked-studio repo, use the Start with chat flow to describe a small change to <target repo>, then confirm the proposed plan. Expected output: a session URL under /s/ with at least one gate row. Verify that the session header shows the assurance state before you approve any gate.
-
Approve agent changes using the assurance receipt
Check who built, evaluated and judged a change before you accept the delivery.
View prompt
In the wicked-studio repo, open the session for <run id> and review its assurance receipt and gate rows. Expected output: a short note stating the assurance label, whether the builder and evaluator were separate seats, and any skipped checks. Verify that the note names the QE acceptance state exactly as the UI shows it.
-
Map a symbol's blast radius before changing code
Onboard a repo, then check what a change to one symbol would touch.
- REPO
mikeparcewski/wicked-studio - Software and DevOps
- Intermediate
View prompt
Using wicked-studio, onboard the repo at <repo path> and open the blast radius for the symbol <symbol name>. Expected output: a list of affected files and the hotspots in the same area. Verify that every file in the list appears in the graph view before you start any run.
- REPO
-
Draft epics from a project's requirements
Pick requirements across repos and launch a governed draft run that opens in its session.
View prompt
In wicked-studio, open the Product view for project <project id>, select the requirements that mention <topic>, and choose Draft epics. Expected output: a session with a plan and a pending gate. Verify that the session lists only the requirements you selected.
Quick start with Wicked Studio
- Check you have what it needs: Node.js 22 or newer and npm 10 or newer; A container runtime for jobs: Rancher Desktop, Docker, Podman, Colima or OrbStack; At least one coding-agent CLI you already use, such as Claude Code or Codex.
- Open mikeparcewski/wicked-studio on GitHub and read the README and license.
- Run
npx wicked-crew serveand open the URL it prints, by default http://127.0.0.1:7701. - Open the Agents tab and sign in each coding agent you want to use.
- Choose New job, then Start with chat, and describe the change you want.
- Read the plan the chat proposes and confirm it; nothing starts before you confirm.
These steps come from our top use case, Start a governed agent job from a chat plan, which also has a copy-paste agent prompt.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for mikeparcewski/wicked-studio
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeWicked Studio alternatives · Best AI repos for Software and DevOps
About this repo
- Who it is forDevelopers and engineering leads who already use coding-agent CLIs and want to start, supervise and approve agent work on their repos from a browser.
- Why it is hot160 stars, launched 75 days ago
- LanguageTypeScript
- Sourcegithub.com/mikeparcewski/wicked-studio · Back to Hot repos
Requirements
- Node.js 22 or newer and npm 10 or newer
- A container runtime for jobs: Rancher Desktop, Docker, Podman, Colima or OrbStack
- At least one coding-agent CLI you already use, such as Claude Code or Codex
- A modern browser such as Chrome, Edge, Firefox or Safari on macOS
Add this badge to your README
Maintain Wicked Studio? Show readers where to find these use cases. 
Markdown
[](https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/?utm_source=github&utm_medium=badge&utm_campaign=mikeparcewski-wicked-studio)
HTML
<a href="https://dedupedai.com/use-cases/mikeparcewski-wicked-studio/?utm_source=github&utm_medium=badge&utm_campaign=mikeparcewski-wicked-studio"><img src="https://dedupedai.com/badge/mikeparcewski/wicked-studio.svg" alt="Use cases on Deduped" height="20"></a>
A static image, no tracking script. About the badge
Questions about Wicked Studio
What is Wicked Studio?
wicked-studio is a browser UI for directing coding-agent CLIs (Claude Code, Codex, GitHub Copilot, OpenCode, Pi) as checked workers that run jobs in sandboxes behind verification gates. It is an open-source project on GitHub: https://github.com/mikeparcewski/wicked-studio.
How do I use Wicked Studio?
Run npx wicked-crew serve and open the URL it prints, by default http://127.0.0.1:7701; then open the Agents tab and sign in each coding agent you want to use; choose New job, then Start with chat, and describe the change you want. The use cases on this page give the full steps and a copy-paste agent prompt for each job.
Who is Wicked Studio for?
Developers and engineering leads who already use coding-agent CLIs and want to start, supervise and approve agent work on their repos from a browser.
What can I do with Wicked Studio?
4 use cases so far, for example: Start a governed agent job from a chat plan; Approve agent changes using the assurance receipt; Map a symbol's blast radius before changing code. Each has steps and a copy-paste agent prompt.
What do I need to run Wicked Studio?
Node.js 22 or newer and npm 10 or newer; A container runtime for jobs: Rancher Desktop, Docker, Podman, Colima or OrbStack; At least one coding-agent CLI you already use, such as Claude Code or Codex; A modern browser such as Chrome, Edge, Firefox or Safari on macOS.
What are alternatives to Wicked Studio?
Other hot AI repos in Software and DevOps: Deep Infer, Harness2, Orca, Opencode, Graphify.
Is Wicked Studio safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.