everycli v0.4.0

Studio media coverage

• H3 Max image, video and audio references, including audio-only guidance. Video reference estimates bind the measured source frame count, not guessed FPS.
• Seven Studio image models: Ideogram 4.5, Grok Imagine Image, Flux 3, Nano Banana 2.1, GPT Image 2.5 Sunburst, Gemini 3.1 Flash Lite Image, and Gemini 3 Pro Image.
• Ordered image references and Ideogram precision masks.
• ElevenLabs v4 voice-over, MiniMax Music 3, Stable Audio 2.5 scores, and ElevenLabs sound effects.
• Native image/audio formats, hash-verified reference inputs, fixed provider endpoints, and no automatic repeat submission after uncertain provider acceptance.

Upgrade

everycli update
everycli worker-update
everycli doctor
everycli offers

update replaces the local CLI. worker-update applies a compatible signed package to the existing workload; do not create a second VM to upgrade. The coordinator must publish a compatible package for your workload.

The new studio/media/ contracts require matching provider credentials and their own explicit offers. Existing bids/discounts are preserved, not copied to new models. The displayed settings-specific work-value estimates are not actual provider invoices or profit guarantees.

Backend/coordinator media routing is deployed, but traffic still requires an updated attested worker, current accepted offers, capacity, and budget. This release does not mean every Director transformation or every app request is miner-served. Paid end-to-end verification awaits the tester's worker update and new offers.

Merged via PR #23.

everycli v0.3.9

What's Changed

• feat: Studio video contracts and worker balance reporting (v0.3.9) by @everyframebuilder in #22

Full Changelog: v0.3.8...v0.3.9

everycli v0.3.8

everycli v0.3.8

Worker updates

• Fix Phala preparation of signed worker updates that change permitted environment variables, including Vivix credentials. Exact compose-hash verification is preserved.
• Safely recover a v0.3.7 update_provision_intent when the exact existing VM is still running its original signed configuration. Keep the original profile and journal; do not redeploy.
• Allow safe shutdown after reconciling an uncommitted preparation. Uncertain commits and key activation remain fail-closed and are not blindly repeated.

Automatic CLI updates

• Eligible native user installations check stable releases in the background after successful interactive commands, at most once every six hours.
• Downloads are checksum-verified and atomically installed for the next invocation. The current command result is unaffected.
• everycli auto-update shows settings and the last attempt. Use --disable or --enable to control the preference; --json returns structured output. EVERYCLI_DISABLE_AUTO_UPDATE=1 disables background updates for that environment.
• JSON, CI, non-interactive, help, version and explicit update commands do not launch background updates. Package-manager paths and custom symlink installations stay manual.
• Only the CLI executable changes. Workers, keys, bids, discounts and running jobs are not updated automatically.

Upgrade

everycli update
everycli worker-update --check
everycli worker-update
everycli health

Existing users need one manual CLI update to obtain this feature. The worker commands require the original management profile and a compatible signed package. They update the same VM after confirmation, wait for attestation, reactivate previously enabled keys and restore the previous accepting/paused state. They do not create offers or submit a generation.

The release candidate was verified through the one-command worker update on a real SN117 miner against the balance-reporting image. Same-VM upgrade, attestation, key reactivation, accepting-state restoration, unchanged offer, health checks, a fresh attested balance-status report and one 5-second 720p Vivix generation passed. The temporary test VM was deleted. Vivix W credits remain explicitly unsupported as a USD balance; this is not a generation failure.

This CLI release does not by itself broaden a miner's signed provider/model permissions or migrate public onboarding to a different worker image.

everycli v0.3.7

What's Changed

• feat(cli): one-command signed worker updates (v0.3.7) by @everyframebuilder in #20

Full Changelog: v0.3.6...v0.3.7

everycli v0.3.6

What's new

• everycli health: read-only, color-coded readiness tables with PASS, WARN and FAIL states. Checks include the local profile, release permissions, coordinator, cloud workload, fresh heartbeat and attestation session, routing, and worker support for active model offers.
• everycli status now shows human-readable deployment, routing, offers and job-activity tables by default. everycli status --json retains the existing structured fields.
• everycli health --json provides structured checks. Health exits with code 0 only when every readiness check passes; otherwise code 2.
• Terminal colors respect NO_COLOR; piped output stays plain text.
• README and command-specific help document the new commands.

Update

everycli update
everycli health
everycli status

What green means

All green means the current readiness checks passed. It does not guarantee traffic, provider funds, successful future generations or earnings. Historical accepted jobs are shown separately; zero active jobs is normal when idle. No paid generation or API balance check is submitted by these commands.

This is a CLI-only release. It does not restart or update deployed workers, release provider keys, change model allowlists, activate a miner, resume routing or modify offers. Adding a saved Vivix key or upgrading the CLI alone does not install Vivix support on an existing worker.

Downloads

Prebuilt binaries for Linux x86-64/ARM64 and macOS Intel/Apple Silicon, with SHA-256 checksums and a version-pinned installer.

everycli v0.3.5

What changed

• everycli offers can display the coordinator-signed Studio catalog with provider and readiness columns. Pending integrations are visible, not silently enabled. Existing bids and older coordinators remain supported.
• everycli doctor explains when a key is saved locally but excluded by the signed deployment. This is not an API authentication verdict.
• The worker accepts Vivix results from its reviewed clipgen-us.vivi-x.ai CDN, without forwarding credentials or allowing arbitrary hosts/redirects.

Updating

Run everycli update for the CLI.

A CLI update does not update a deployed worker or grant new provider permissions. Existing workers need their signed app-specific worker update, fresh attestation and activation before using a newly permitted key. Do not create a second VM to resolve this check.

Catalog visibility does not mean all Studio models are routable: implementation, pricing, deployment permissions, provider capabilities and active miner offers still apply.

Verification

Linux x86_64/ARM64 and macOS Intel/Apple Silicon builds passed. Five- and fifteen-second direct-provider Vivix smoke tests passed media validation and visual review. Live TEE rollout remains a separate deployment step.

everycli v0.3.4

What's Changed

• fix(cli): consistent v-prefixed update messages; release v0.3.4 by @everyframebuilder in #17

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

everycli v0.3.3

everycli v0.3.3

Six onboarding and output improvements:

• Short API keys now explain: “That key looks too short (minimum 10 characters).” Invalid input does not replace an existing key.
• A missing wallet is named explicitly, with available local wallet names. Discovery reads directory names, never private key contents.
• Registration prints its fee/transaction notice once and shows placeholder instructions only when placeholders remain.
• remove-api-key --yes skips the already-approved question and prints one removal summary. With --json, the result stays structured and stderr is empty.
• Installed, latest and updated version numbers use the same readable format. Machine-readable version fields are unchanged.
• Deployment is step 4 of 11, not completed miner setup. The wizard prints steps 5–11 for readiness, activation, fresh attestation, resume, model offers and final diagnosis. Replay them with everycli setup --continue.

Setup does not automatically activate credentials, resume paid work or choose a bid. Existing safety checks and confirmations remain in place.

Upgrade

everycli update
everycli --version

The already-installed CLI performs this upgrade; the new wording appears once v0.3.3 is installed. Download progress remains the default, with JSON only when --json is requested.

This updates only the CLI, not miner profiles, credentials, deployed workers or cloud resources.

See installation, guided setup and the command reference.

everycli v0.3.2

everycli v0.3.2

Updates now show readable progress by default:

• Checking, downloading, checksum verification and installation stages.
• Download percentage and transferred size when the server supplies a total; downloaded size otherwise.
• A single updating line in terminals, or plain-text milestones in redirected logs.
• everycli update --json and everycli update --check --json suppress progress and return one structured result or error.

Checksum verification, bounded downloads and atomic binary replacement remain in place. Failed or truncated downloads do not replace the installed executable.

Upgrade

everycli update
everycli --version

The already-installed CLI performs the upgrade. An older version still uses its older output during that one upgrade; the new progress display is available once v0.3.2 is installed.

This updates only the local CLI, not profiles, credentials, deployed workers or cloud resources.

See the installation guide and command reference.

Public binaries are provided for Linux and macOS, on x86-64 and ARM64, with SHA-256 checksums and the one-command installer.

everycli v0.3.1

What's Changed

• fix(cli): polish key management, errors and setup for v0.3.1 by @everyframebuilder in #13

Full Changelog: v0.3.0...v0.3.1