From Pilot Shell
QualityLayer and Pilot Shell 11 can run side by side. Installing QualityLayer keeps Pilot Shell, its configuration and its tools. Version 11 remains the last Pilot Shell version.
Update from Pilot Shell
Run pilot update in a terminal. Pilot Shell shows the update from v11 to v12 with its release notes and asks Update now?. When you confirm:
The installer starts
It says that Pilot Shell is now QualityLayer and keeps working.It installs QualityLayer
On a Mac, or Linux with a screen, the App and its command line. Over ssh, in WSL or in a container, the command line alone.It connects your agents
It adds the QualityLayer skills to each agent it finds, such as Claude Code and Codex. Every download is checked against the signed release before anything is written.The App opens
To finish setting up. If it cannot open a window, the installer says where the App is.
You can also install QualityLayer directly; the result is the same.
Start using QualityLayer
Ask your agent to plan or implement using QualityLayer or QL.
Repositories, code and Pilot plans stay in place. Choose Existing plan in a new Feature or Bugfix to reuse a plan's text; its workflow state is not imported.
Import memories per project
If you already have JSONL or Markdown memory exports in a repository’s .pilot/memories/, open Settings › Memory › Import from Pilot Shell and select the matching project. QualityLayer currently cannot import the local pilot-memory.db database; keep it in place.
Lessons are copied into QualityLayer's private project memory; your files stay in place, and a second import skips unchanged lessons (Pilot memory import).
Remove Pilot Shell when you are ready
Once your workflows work in QualityLayer, remove Pilot Shell with its own uninstaller:
curl -fsSL https://raw.githubusercontent.com/maxritter/qualitylayer/main/uninstall.sh | bash
It asks before removing anything and keeps the tools Pilot Shell installed; add --remove-tools to remove those too.