Skip to content

Releases

Fleet Node 0.1.5

Choose a tag to compare

@bek91 bek91 released this 21 Oct 20:49

Prioritize current evidence during backfill

The rollout canary exposed a delay: unvisited files from earlier recent dates were selected ahead of today's already-active sessions. Long-lived sessions could also receive new output outside the recent-date folders.

The collector now checks known-file metadata and reserves 32 of its 64 read slots for pending or changed files ordered by modification time. Remaining slots continue historical rotation. This changes scheduling only: checkpoints, queued evidence and accepted history are preserved; no replay or schema migration is required.

Includes the native evidence and durable transport changes in 0.1.4, plus preservation of existing Background Codex service repairs. Native evidence remains opt-in. Updates use the maintenance gate and retain current external queues/history.

Fleet Node 0.1.4

Choose a tag to compare

@bek91 bek91 released this 21 Oct 20:38

Native tool evidence for fleet classification

  • Opt-in collection of managed Codex command/tool lifecycle evidence across all agents, using the existing independent five-minute schedule and authenticated telemetry path.
  • Complete best-effort-redacted tool output; no prompts, messages or tool arguments. Other harnesses and compressed archives remain unsupported.
  • Durable checkpoints, replay and outbox delivery; whole-record logs are acknowledged only after persistent enqueue and exported concurrently.
  • Preserve existing Background Codex service repairs during ordinary updates; no fleet-wide service-domain migration.

Validated with Node 24.19, all 56 checks including the pinned real Collector and packed upgrade/rollback, plus evidence collection through the final installed tarball.

Upgrades require the documented maintenance gate, a saved rollback package, and preservation of current external queues/history. Native evidence remains opt-in via config/evidence.enabled containing v1.

Fleet Node 0.1.2: TypeScript agent and node comparison

Choose a tag to compare

@bek91 bek91 released this 12 Oct 04:54

The canonical fleet-node-observability repository now contains the standalone TypeScript/npm agent, replacing the retired Python implementation. Package: @unblocklabs/fleet-node@0.1.2.

The read-only comparison collector reuses the existing five-minute schedule and authenticated telemetry pipeline. It reports serving-root package version, the actual Gateway Node executable version, stored tool configuration, exact-executable permission records, observation timestamps, and section status. Unset, denied, no matching record, unreadable, and stale remain distinct; these observations are not live capability tests.

Compiled runtime JS is unchanged from the already deployed 0.1.2 fleet artifact; source consolidation and packaging documentation do not require redeployment or Gateway restarts. The dedicated fleet-node-v0.1.2 tag preserves the unrelated legacy v0.1.2 tag. Download the npm tarball and verify SHA256SUMS. Existing installations must stop the maintenance gate before any npm replacement and retain external queues, credentials and session history.

Validation: strict TypeScript rebuild and package-content inspection passed. The prior unchanged implementation passed 53 tests; one optional native Collector integration was skipped. Real packed install, upgrade and rollback were validated before consolidation.

v0.3.8: secure release installation

Choose a tag to compare

@bek91 bek91 released this 27 Sep 08:15

Harden remote installation: release archives, redirects, and checksum sidecars must use HTTPS. Build-time version overrides now update the embedded VERSION file. Includes repository guidance and packaging regression tests.

Collection/runtime code is unchanged from v0.3.7. Older module-only installations can retain an older root package VERSION; inspect deployed module hashes before planning a reinstall.

Validation: 113 node tests passed (one opt-in Collector integration skipped), checksummed release build, and whitespace checks. Release assets contain no host configuration or credentials.

Archive SHA-256: 4b272631a42c798c20760a7efd0bbc1d5e4d5fa68e41d5fa7346ce0b6d1b37da.

v0.3.7 — Session calendar trends

Choose a tag to compare

@bek91 bek91 released this 20 Sep 03:40

Retain thirteen calendar months of session starts and export exact daily, Monday-weekly,
and calendar-monthly observed totals in America/New_York. Adds all / cron / noncron choices.
Unknown historical periods remain NaN gaps; current and pre-preservation periods are partial.
No transcript export, new service, or OpenClaw changes.

Validation: 111 node tests (one integration skip), release build, and Bill canary.
All 1,356 current canary period/kind values match independent read-only SQLite aggregation
and central Prometheus ingestion, including unknown values. The staged fleet deployment
replaces only the session collector module, not the entire installed package.

v0.3.6: correct daily session dates

Choose a tag to compare

@bek91 bek91 released this 20 Sep 03:22

Correct daily session counts by recognizing both OpenClaw start-date representations.

  • Prefer identity-matched sessionStartedAt, then started_at. Do not mistake updated_at or an unverified created_at for a session start.
  • Repair existing ledger dates without double-counting; retain observations after source cleanup.
  • Includes all-session and cron-only daily collection through the existing five-minute telemetry schedule.

Validation: 108 node tests (one integration skip), eleven focused session tests, checksummed release build. Bill canary resolved all 740 falsely undated windows; all 60 daily buckets matched an independent read-only source aggregation.

For the managed fleet, deploy the session collector module only; no OpenClaw restart, credential change, or full service reinstall is needed. The archive also supports new/full installations. Installed module hashes are the rollout evidence; do not infer a full package upgrade from this targeted update.

v0.3.5: actionable cron attempt timestamps

Choose a tag to compare

@bek91 bek91 released this 18 Sep 20:37
3f9eadf

Adds latest cron attempt and active-run timestamps; preserves millisecond precision for next schedules. Missing run times remain absent, not epoch zero. Verified with 97 tests (1 skipped) and a real Bill collector canary. PR #16. Node rollout changes only the user-owned cron module and needs no gateway restart; root package upgrade remains a separate sudo installation.

v0.3.4: reliable cron runtime discovery

Choose a tag to compare

@bek91 bek91 released this 18 Sep 19:53
3a780e6

Run the OpenClaw cron CLI from the managed account home so launchd collection can recover a compatible installed Node when an older runtime comes first on PATH. No gateway configuration, credentials, Node defaults, or timeout changes.

Validation: 96 tests run with one opt-in skip; live Rocky trial passed from the launchd root working directory. Scheduled acceptance tracked in #14 and #4.

SHA256: 742408ce954cc7c97ac5298c00d202bbce0f075aeeec53f7b125d4dce412084b

v0.3.3: Codex collection and gateway probe freshness

Choose a tag to compare

@bek91 bek91 released this 18 Sep 16:01
cae319e

Restores account usage on current Codex CLI versions without increasing timeouts. Adds readiness probe occurrence timestamps and removes unused legacy modes/metrics and fixed-layout scaffolding. Verified: 95 unit tests pass (1 opt-in skipped), 20 packaged tests pass on Bill, candidate RPCs succeed on Bill and all seven previously failing nodes. Full root installation and scheduled production verification remain separate rollout steps. See PR #11.

fleet-node-observability 0.3.2

Choose a tag to compare

@bek91 bek91 released this 18 Sep 07:14
c13e965

Fixes

  • Preserve existing backups when exclusive creation fails.
  • Preserve another writer's atomic temporary file on collision.
  • Keep separate private OpenClaw backups for same-second updates.

PR: #10. Resolves #2.

Validation: 95 tests run (94 passed, one opt-in skipped); all 11 targeted tests passed against the checksummed release archive on billsmacmini. Existing captureContent choices remain preserved.

This release publishes the installer/configuration fix; it does not automatically upgrade root-installed fleet node runtimes. Bill's installed runtime is unchanged.