-
Notifications
You must be signed in to change notification settings - Fork 2
lore
This timeline is based on commits and tags in origin/main, with the current
snapshot taken on 2026-09-04.
The first commit landed on 2025-08-09 as an npm-workspaces monorepo with
separate TypeScript configuration. The initial history already included
launcher and Prime Agent integration work. The current web adapter was
introduced on 2026-08-13 by
f3cd0215f, “feat(web): isolate the Qredence UI under a pnpm workspace”.
From 2026-05-14 through 2026-08-26, tags and commits show repeated work on
standalone packaging, native dependencies, R2 downloads, and installer
reliability. fleet-prime.sh first appeared on 2026-08-15 in
e13a1882f, “feat(coding-agent): add fleet-prime command to launch the web
interface”. The current installer and package are the result of those
experiments, rather than a single initial packaging design.
On 2026-08-27, b31d4d8a5 replaced the vendored runtime with the stock Prime
Agent package. The current architecture consumes release tarballs through
PRIME_AGENT_RUNTIME.json and never copies upstream engine source into Fleet.
The same boundary is now enforced by the repository instructions and runtime
check.
On 2026-08-31, 55c4aa4dd unified the repository on one pnpm workspace and
root lockfile. The change removed the old split installation model and moved
the dependency policy into pnpm-workspace.yaml. The minimum release age is
now expressed as 10080 minutes, or seven days. The source installer and
runtime pin were updated to use the unified layout.
The same day, commit 6f3973f13 established CircleCI publication for
@qredence/fleet. The current pipeline later evolved into a package-first
flow, but the important boundary stayed the same: the package is built and
verified before publication, and the Prime Agent engine is not republished by
Fleet.
On 2026-09-02, 7d2d02f8d completed the Fleet chat workspace panels. The
right-rail registry now includes Resources, Workspace, Artifacts, REPL,
Subagents, and Session insights.
On 2026-09-03, 66cc436b1 established package-first npm delivery around
Changesets and CircleCI. The release process now prepares a release pull
request on main, verifies the merged version commit, and publishes the
verified package artifact.
On 2026-09-04, 6f6db1c07 added first-class read-only subagent conversation
tabs. Later that day, f807d2fdf consolidated the guides and reinforced the
browser/server architecture boundaries. The current @qredence/fleet
manifest is at version 0.5.5, while the source runtime pin is prime-agent
0.9.1.
README.md has existed since the initial 2025-08-09 commit, although its
content has been rewritten several times. The Fleet server adapter and
protocol were introduced together on 2026-08-13 and remain the same
cross-package seam: web/server owns runtime access, web/protocol owns
browser-safe types, and web/app owns the browser route.
- Vendored Prime Agent runtime, replaced Aug 27 2026. The repository now consumes a pinned stock runtime instead of carrying an engine source tree.
- Split npm/pnpm installation model, replaced Aug 31 2026. One root pnpm workspace and lockfile replaced the older mixed layout.
-
Former
fleet-primepackage directory, renamed Sep 4 2026. The public package now lives atpackages/fleet-web; the binary name remainsfleet-primefor compatibility andfleet-agentis the primary command. -
Tag-as-release input, replaced by Changesets preparation by Sep 3 2026.
The current CircleCI release jobs are branch-filtered to
main; generated release commits, not tag filters, decide whether publication runs.
The repository has 4,685 commits on origin/main as of 2026-09-04. The
current Fleet-owned production surface contains 446 tracked code files and
74,512 lines, with most code in web/design/src. The recent history is
concentrated around the adapter, panels, package delivery, and architecture
boundary work rather than a gradual expansion of independent services.
For the reasoning behind the major boundary changes, see design decisions.