deployment

Deployment

Prime Agent is a public, self-installing product. The repository owns its own distribution story: a shell installer that turns a plain checkout into a usable install, a bundled web runtime, and a release pipeline that packages and publishes all four packages in lockstep. Every client surfaces (terminal, daemon, web) ship from the same source tree under packages/, while the Qredence web UI under web/ is packaged into the prime-agent artifact at release time.

How it ships

1. A user runs the public installer (install.sh) in an empty directory. It clones or reuses the Qredence/fleet-prime-agent checkout, installs the root npm workspace and the web/ pnpm workspace, builds all packages plus the production web runtime, and links a global prime-agent command. See Installer.
2. prime-agent web launches the packaged web frontend and backend from the installed artifact. See Installer for how the launcher is wired and Getting started for the run commands.
3. A maintainer cuts a release. All packages share one version (lockstep); scripts/release.mjs bumps it, finalizes changelogs, commits and tags, publishes to npm, and reopens [Unreleased]. The release-prime-agent.yml CI workflow also packages branded tarballs and pushes them to Qredence R2 for the public installer flow. See Release pipeline.

Sub-pages

• Installer, how install.sh works: prerequisites, environment overrides, clone-or-reuse logic, dependency install, web build, global link, and the source-installer checks that guard it.
• Release pipeline, lockstep versioning, the scripts/release.mjs flow, packaging and publishing, the web release build, and the current state of the CI release workflows.

Related pages

• Getting started, prerequisites, install, and run commands
• CLI, the prime-agent command surface, including prime-agent web
• Development workflow, the release process summary
• History, the timeline of the installer and release pipeline changes