Plan each change visually, then let your agents build and verify it.
Work side by side in the App or browser, or stay in your terminal or IDE.
Install • Workflow • Docs • Website • Changelog • Issues
See all seven steps on qualitylayer.dev or try the demo in your browser.
“With QualityLayer, developing software with agents finally feels like doing real engineering again.”
An engineer who uses QualityLayer
| You get | How it works |
|---|---|
| Your own agent and plan | Use Claude Code, Codex, Cursor and more with your existing login or API key. |
| A design you can review | Comment on diagrams and clickable screens, then approve the Plan before code changes. |
| Small, tested changes | Your agent writes tests before code and hands independent parts to other agents when useful. |
| An independent check | With independent review on, a separate agent checks the running change against your request before Review opens. |
| Your own requirements | Add checks, tools or skills to any step. Your agent records what ran, what did not, and why. Required lines. |
| Visible decisions and effort | Read decisions and results in your repository; see time, model usage value and cost estimates in the App. |
- A coding agent, installed and signed in with your subscription or API key: Claude Code, Codex, Cursor, Grok, Antigravity, Pi, OpenCode or GitHub Copilot. Other agents connect through the CLI.
- Git and a repository.
Download the App and open it. Setup automatically installs the qualitylayer command (commands) and connects your agents. On a server, in WSL or in a container:
curl -fsSL https://qualitylayer.dev/install.sh | bash # macOS, Linux, WSL
irm https://qualitylayer.dev/install.ps1 | iex # Windows PowerShellThe App updates itself; without it, run qualitylayer update. Installation guide.
Uninstalling
qualitylayer uninstall undoes what the installer changed; your plans stay. On Windows, even when the App is gone:
& ([scriptblock]::Create((irm https://qualitylayer.dev/install.ps1))) -UninstallComing from Pilot Shell 11
Run pilot update or download the App. An active Pilot Shell licence works with both products; older purchases may need help moving over. Migration and memory import.
In the App or browser, choose +, then Task (Feature or Bugfix) or Chat. Pick your repository and agent, and describe what you need:
Plan retries for failed webhooks and stop after a few tries.
- Answer questions and comment on the Plan.
- Approve the Plan. Your agent builds and verifies the change.
- Review the result and recorded checks, then approve it. Ask your agent to merge, deploy or make further changes.
Prefer your terminal or IDE? Choose In my terminal, or ask there: “Using QualityLayer, plan retries for failed webhooks.” Other agents use the CLI (supported agents). Chat skips the workflow steps (Chat guide). QualityLayer runs only when you ask for it. Your first task.
Setup adds these skills. Ask in plain words, in any language.
| Skill | For | You say |
|---|---|---|
ql-peer |
Agents talking to each other | “Ask Codex to review what you just built.” |
ql-workflow |
Plan, build and review a change | “Using QualityLayer, add rate limits to the export API.” |
ql-chat |
Chat without workflow steps | “Using QualityLayer, chat about the billing refactor.” |
ql-artifact |
Designs, diagrams and pages | “Open the settings design in my browser.” |
ql-quality |
Code health and security scans | “Scan this repository for leaked secrets.” |
ql-manage |
Tasks, sharing, settings, setup | “Share this task with my team.” |
Each step saves readable Markdown in your repository, and existing plans start at Plan. You approve the Plan and the finished change, and you control pushes and merges.
| Step | What happens |
|---|---|
| Discuss | Settles what done means and clarifies a bug report |
| Research | Agents read how your code works today; a bug is reproduced and diagnosed here |
| Plan | Diagrams, clickable artifacts and the acceptance test, approved by you |
| Outline | Your agent splits the approved Plan into small slices |
| Implement | Your agent builds test first, fixes what fails and decides when it is ready |
| Verify | Your project's checks and an independent agent's review |
| Review | The code first, what changed and the acceptance test as it ran, approved by you |
| Pull request | Failing checks and routine review threads fixed; the task stays open until you merge |
Engineering starts with a technical plan. Product starts with a product brief. Choose in Settings › Workflow. How they differ.
Your project's checks, code health and security scans run first. Then a separate agent reviews the change against your request. How Verify works.
| In the App | What you can do |
|---|---|
| Chat or a planned task | Talk directly with your agent or follow the workflow. See agent activity and get notified when one needs you. |
| Conversation and terminal | Read the agent's conversation or its terminal beside the task. Answer questions and pin feedback. |
| Artifacts | Try mockups, diagrams and clickable pages before any code exists. Keep reusable ones in your repository. Artifacts guide. |
| Checks and code review | Read the evidence and file diffs, and comment on any line. |
| Agent controls and usage | Choose model, effort and permissions; track limits and daily costs, including in the macOS menu bar. Settings. |
| Memory and team | Reuse project lessons, ask teammates over Slack or email and share work. |
QualityLayer keeps task files on your computer and encrypts shared tasks first. Your coding agent uses its own provider. Files and privacy.
Quality by design. The software factory with you in the loop.
Made by Max Ritter · License