v0.3.4

What's Changed

• Put the install command in the social preview image by @stepandel in #48
• Record cold peek measurements and correct the first-read baseline by @stepandel in #49
• Reduce release queue contention and export sanitized timing reports by @stepandel in #47
• Remove per-account compute caps and upgrade existing policies by @stepandel in #50

Full Changelog: v0.3.3...v0.3.4

v0.3.3

What's Changed

• Deduplicate Git upload and publication bookkeeping by @stepandel in #43
• Bring README features and the review flow to the website by @stepandel in #44
• Speed up release preparation and reconcile promotions immediately by @stepandel in #42
• Reuse Fleet connections to reduce hosted relay latency by @stepandel in #45
• Reduce Git snapshot subprocess overhead by @stepandel in #46

Full Changelog: v0.3.2...v0.3.3

Juiced 0.3.2

Workspace inspection now avoids a separate release-check request and an unnecessary bootstrap wake-up. Git comparisons reuse validated stat entries for ordinary unchanged files while preserving clean filters, ignored-file handling, and private-index isolation.

This release also includes improvements to Git upload throughput, session lookup, and reconnect work.

• Workspace inspection and latency diagnostics (#40)
• CLI contention, repeated work, and pipelined Git uploads (#41)

Built and installer-tested for Linux x64/arm64 and macOS Intel/Apple Silicon. Installed clients receive this release when the managed service switches to its matching runtime.

Juiced 0.3.1

Claude can now request individual files from your connected laptop project.

• Ask Claude to list local files, including hidden files, with list_local_files.
• Use pull_local_files to send selected files or directories, including ignored configuration and fixtures, after laptop approval.
• Approved bytes are pinned in memory and transferred in verified chunks. Pulls preserve Git HEAD and staging and refuse differing existing destinations.

Run juiced update to install 0.3.1. Restart your native Claude process (/exit, then juiced claude) to load the new tools. Keep the laptop client connected to review local access requests.

Includes native archives for macOS Intel/Apple Silicon and Linux x64/arm64, with checksum verification and installer tests on all four platforms.

Juiced 0.3.0

Juiced now uses one account-backed Fleet instance path. Self-managed mode and direct App credentials are removed. Package deployment and rollout belong to the Cantelop CLI.

Operator dependencies: SDK 1.6.0 and Cantelop CLI 0.17.1.

What's Changed

• Polish CLI recovery messages and terminal presentation by @stepandel in #35
• Speed up Claude workspace inspection by @stepandel in #36
• Migrate Juiced to SDK Fleet instances by @stepandel in #38

Full Changelog: v0.2.6...v0.3.0

Juiced 0.2.6

Juiced 0.2.6 improves session recovery, local publication feedback, and sign-in reliability.

• Retry workspace session admission timeouts and explain the wait when another session is finishing. Session listing now allows the full admission retry window.
• Report publication connection failures separately from local conflicts, preserving local Git and filesystem error details.
• Keep current credentials separate from older CLI processes and preserve sign-in during concurrent credential migration.

Install or upgrade

curl -fsSL https://juiced.codes/install.sh | sh -s -- 0.2.6

Archives include Node.js and dependencies for macOS Intel/Apple Silicon and Linux x64/arm64. Each archive is tested on its native platform, including installation without Node or npm on PATH.

Full changelog: v0.2.5...v0.2.6

Juiced 0.2.5

Juiced now reports completed installations and CLI usage through the managed service to help measure adoption and retention.

• Records fresh installs versus updates, first runs, successful sign-ins, working session connections, and throttled session activity.
• Uses random installation and anonymous identifiers; anonymous identity resets on logout.
• Includes a first-use notice and offline controls: juiced telemetry status, juiced telemetry disable, and juiced telemetry enable.
• Honors JUICED_TELEMETRY_DISABLED=1 and DO_NOT_TRACK=1; CI and self-managed mode are excluded.
• Event payloads exclude prompts, code, terminal output, arguments, paths, credentials, and email addresses. Reporting failures cannot fail commands.

The compiled runtime matches 0.2.4. See the telemetry guide for event definitions and privacy details.

Install or update:

curl -fsSL https://juiced.codes/install.sh | sh

Juiced 0.2.4

Juiced 0.2.4 combines private-file CLI sign-ins with a managed-service provisioning fix.

• CLI sign-ins now use private credential files, removing OS keychain prompts and the native keyring dependency. Existing file-based sign-ins continue to work. Users upgrading from OS credential storage sign in once with juiced login; interactive commands can start that flow automatically.
• Provisioning, billing and terminal cleanup continue when usage ingestion encounters an unmapped Fleet settlement. Failed workers retry independently, and usage evidence remains intact for reconciliation.

The compiled Cantelop runtime is unchanged, so this release does not require an installation runtime upgrade.

v0.2.3

What's Changed

• Use shared Fleet packages with SDK 1.5.1 by @stepandel in #26

Full Changelog: v0.2.2...v0.2.3

Juiced 0.2.2

Juiced now updates automatically before managed commands, using the CLI version approved by the service. Updates verify release checksums and activate atomically, preserve piped input and command arguments, and leave running sessions alone.

Runtime incompatibilities trigger update recovery and show an exact manual installation command when recovery cannot complete. Commands that have already started are never replayed automatically. juiced update checks explicitly; help, version and logout remain available without an update check.

Existing installations need one manual update to gain automatic updates:

curl -fsSL https://juiced.codes/install.sh | sh

This release retains the qualified runtime used by 0.2.1. Source and package-manager installations retain their existing update method.