INSTALL CREWLO

Start your first crew.

Prepare the app, connect one agent and try a small request. These steps run on your computer; this website cannot start an agent.

Early preview. Windows x64 and macOS previews are available below. Windows is unsigned; macOS has no Apple Developer ID certification or notarization. Full installation tests on personal computers remain open. Linux installers are not available.

WINDOWS X64 / PREVIEW 0.4.6

Download. Install. Open your studio.

Download for Windows Release notes & checksum →

129 MB · Windows x64 · French / English setup · Unsigned preview

Download the setup file and open it.
Follow the installer, then launch Crewlo from the Start menu or desktop shortcut.
Connect your own authenticated agent CLI and choose a project folder.

You do not need the source build tools below to install the packaged app. Your agent CLI may have its own requirements.

The preview is not code-signed, so Windows may show an unknown-publisher warning. Check that the file comes from the linked Crewlo release. No automatic updates are enabled; download future versions manually.

Verify the download (SHA-256)

Download the checksum file. In PowerShell, run Get-FileHash .\Crewlo-0.4.6-win-x64-preview-setup.exe -Algorithm SHA256 and compare the result with the checksum.

Prefer building the app yourself? Continue with the source prerequisites below.

MACOS / PREVIEW 0.4.6

A studio for your Mac.

Choose the chip shown in Apple menu > About This Mac.

Download for Apple Silicon Download for Intel Mac

DMG installers · Apple Silicon (M-series) or Intel · No automatic updates

Open the DMG and drag Crewlo into Applications.
Launch Crewlo from Applications.
Connect your own authenticated agent CLI and choose a project folder.

Preview without Apple Developer ID certification or notarization. macOS may block opening the app. Review Apple's guidance for apps from unidentified developers before deciding whether to open it. Do not disable Gatekeeper globally.

Both architectures passed packaged SQLite and terminal checks on macOS 15 CI runners. Mounted-DMG installation, onboarding, studio and settings persistence also pass on both CI architectures. Personal permissions, live agents and installation on a personal Mac still need validation.

Release notes and SHA-256 checksums →

Verify your download

Download the checksum for Apple Silicon or Intel. Run shasum -a 256 Crewlo-0.4.6-mac-arm64.dmg in Terminal (use x64 for Intel) and compare the result.

01 / PREPARE

Check your tools.

Git, Node.js 22.22 or newer, and npm.
Python 3 compatible with node-gyp for native dependency rebuilds.
On Windows: Visual Studio C++ build tools, Windows SDK, and matching MSVC Spectre-mitigated libraries.
Your chosen agent CLI, its account or credentials, and a project folder you are comfortable letting it access.

Clone the repository, then run the read-only diagnostic. If you already have a checkout, skip the first two lines.

PREPARE & CHECK

git clone https://github.com/HafidIdrissi/crewlo.git
cd crewlo
npm run doctor

Review these commands before running them.

Resolve diagnostic failures before proceeding. The doctor does not install anything, check Python compatibility or prove that a clean native rebuild will succeed. Missing dependencies before the first installation are expected. Detailed diagnostic notes (French).

02 / BUILD FROM SOURCE

Open the desktop app.

Once the prerequisites are ready, install dependencies and launch Crewlo. npm ci downloads dependencies and rebuilds native modules through the project’s postinstall script.

INSTALL & RUN

npm ci
npm run doctor
npm run dev

Run these from your Crewlo checkout after fixing prerequisites.

npm run dev opens the Electron app. npm run site only previews the website; it cannot run your agents.

Installation fails or the app will not open?

Node not found or too old: check node --version in a new terminal. Make sure the correct Node version is on PATH.
MSB8040: add the Spectre libraries matching your MSVC toolset version and architecture in Visual Studio Installer.
Missing SDK or compiler: install the Windows desktop C++ tools and SDK, then rerun the doctor.
Native module error: after correcting prerequisites, run npm run postinstall, then npm run doctor.

Existing native binaries passing a runtime check do not prove a clean rebuild. See known verification limits.

03 / CONNECT AN AGENT

Bring your own tools.

Complete onboarding. Install and authenticate the agent CLI you intend to use, then choose Add agent, give it a name, select the corresponding provider preset and choose its project folder.

Confirm the session is available before sending work. Provider presets and automated contracts do not certify every provider’s live behavior. Read the validation scope.

Your provider’s account, usage costs and permissions still apply. Review the CLI’s approval and automation settings before giving it access to a project.

04 / A SMALL FIRST MISSION

Ask. Watch. Read.

Open a familiar project and send a small request from the mission composer:

Read this project and explain what it does. Suggest one small improvement before changing any files.

Check the delivery state. If it says Message delivery paused, use Resume on the desktop when ready.
Follow the activity, then open the agent’s Conversation or terminal for context.
Review any permission request in the app or CLI; behavior depends on your settings.
Read the actual response. A queued or accepted message is not a completed task.

Pausing delivery does not stop a tool that is already running. Keep your computer and the agent session available.

Add messaging later ↗Back to the demo ↗