Repository navigation
Releases: AlitheaBio/froglet
Release list
Froglet 0.4.7-beta.1 — bounded compute and recoverable tasks
Froglet 0.4.7-beta.1 adds bounded requester-supplied computation and recoverable
task results to the free beta. It is a beta release, not a stable production
qualification.
What changed
- Native MCP compute:
run_computeaccepts a Wasm program and input,
including a local module-path option. The runtime uses the signed
Quote/Deal/Receipt flow and enforces the agreed fuel, memory and execution
limits.get_taskexposes the saved task and its verification evidence. - Optional A2A 1.0 adapter: configured counterparties can submit and poll
tasks using explicit requester keys and exact Offer hashes. The adapter is
disabled by default. Cancellation, streaming and public federation are not
supported in this beta. - Offline terminal-task recovery: completed results and signed terminal
failures remain readable after provider shutdown and requester restart. The
runtime revalidates the cached signed chain, identities, result hash and
terminal status. Corrupt evidence fails closed; pending or unsigned outcomes
still require provider synchronization. Reading a Receipt creates no new
work or payment authorization. - Browser interoperability: the developer playground signs the free
transaction chain in the browser, compiles its AssemblyScript examples
locally in a Worker, and exchanges compatible programs and evidence with a
real node. This does not add JavaScript as a kernel execution runtime. - Research metadata: selected-data declarations expose field types,
namespaces, versions, units and provenance. They compare declared metadata;
they do not establish ontology alignment or scientific correctness.
The canonical kernel artifacts, signing and hashing rules remain unchanged.
Release and dependency checks
Release checks now reject skipped required work, stale or mislabeled local
binaries, incomplete checksums, unexpected archive members and inconsistent
package/Registry versions. Qualification examples use the selected optimized
node without increasing signed execution budgets. CI audits both MCP dependency
trees. Wasmtime is updated to the patched 36.0.17 line; Wrangler 4.143.1 uses
patched Undici.
The website cache library is reviewed at http-cache-semantics 4.3.0. It
preserves the reported max-stale/cookie behavior; upstream disputes the advisory
and closed its proposed fixes unmerged. Its separate Vary fixes and a clean npm
audit do not establish remediation of that behavior. The deployment policy
still verifies the actual static-site/custom-Worker boundary, including on a
clean audit, and fails on other high/critical findings, reviewed-input drift,
a newer stable cache-library version, or expiry on 17 October 2026. See
the dependency review.
Qualification and limits
At note preparation, local software checks, browser/node tests and a deterministic
replay of a previously generated program had passed. The replay includes six
successful signed chains and one execution-limit failure, plus task recovery
with the provider stopped and requester restarted. It does not count as a fresh
LLM generation or agent-host session.
The approved source is d70cb50017c7c526d1f7ad4faf278da07e8248a4. All six
required main CI checks
passed before the beta cut. The release workflow repeats its exact-tag checks
before publishing. Verification and replay through the final published assets
remain separate gates; local checks do not qualify a different released
executable. Consult the release workflow and
qualification record
for the evidence applicable to the source and binary you use.
New hosted compute on independent machines, clean-machine installation,
fresh agent-host journeys, real payment rails and the first-time-user acceptance
gate remain separate qualifications. Existing hosted beta.4 reachability does
not qualify this compute candidate. Signed receipts establish transaction
evidence, not the scientific usefulness or correctness of an answer. A catalog
or service remains dependent on its provider's availability and configured
allowances.
Distribution
This GitHub release path produces native node archives, bootstrap/checksum
assets, an attested Release Bundle and digest-pinned OCI image references.
Verify that bundle before installation or deployment; do not persist mutable
image tags as deployment identities. Select VERSION=v0.4.7-beta.1 explicitly
when using the native installer; this prerelease does not advance the stable
latest channel.
The froglet-mcp npm package and MCP Registry entry are published separately.
An immutable GitHub release does not prove that the matching npm/Registry beta
is available. Check their exact versions before relying on npx froglet-mcp.
v0.4.6-beta.4
Recover saved service invocations after provider unpublish or shutdown, and release identity custody locks reliably.
-
Unix identity custody explicitly releases its lock when the operation ends, even if a concurrently spawned child still holds an inherited descriptor. Active operations remain exclusive. The regression failed before the correction; all 25 custody tests and the full Rust suite pass. The beta.3 candidate remains unpublished after its release gate exposed this race.
-
Native CLI and MCP consult the authenticated requester ledger before fetching current service metadata. Reusing the original idempotency key, service/provider and input recovers the saved result and verifies its signed receipt without a new execution or invitation credential.
-
Conflicting requests fail closed. Pending work still needs the provider to refresh its status. Native MCP now honors FROGLET_DAEMON_URL consistently with CLI publication and invocation.
-
Upgrade both the native caller and its requester runtime to beta.4 for offline recovery, retaining the requester data directory. Older runtimes retain their existing fallback behavior.
Verification: 685 local public Rust tests with warnings denied and Clippy; native CLI/MCP restart and offline regressions. The real production invitation test's saved receipt was recovered by share URL after unpublish with a new requester process and no invitation file. Production invitation admission used zero execution allowance; one invited call and revoked replay used only one deal.
Payment rails remain deferred. Clean-machine agent/platform and first-time human qualification remain open; this is a beta, not a stable-release qualification. No Kernel signing, hashing, artifact, database or payment changes.
v0.4.6-beta.2
Invitation-protected services can now request marketplace admission through exact signed metadata verification, without giving the marketplace an invitation or executing a canary. Providers still enforce invitations on every call. Open services retain execution checks; private services remain ineligible.
The marketplace and service-link pages distinguish invitation access from execution-check evidence, and generated consumer commands use a credential file. Shared URLs and QR codes contain no invitation credential.
Validation: 684 public Rust tests, 76 publish-engine tests, 164 website tests and the production build; local rendered desktop/mobile and QR checks; a fresh Codex MCP publication/invocation roundtrip. The paired hosted beta.21 adds admission enforcement and durable failed-feed cooldown. Payment rails remain deferred. Clean-machine, Claude Code, and human first-use qualification remain open; this is a prerelease.
Froglet v0.4.6-beta.1 — bounded nonpayment services
This public beta adds bounded nonpayment service execution and usable invitation workflows.
- Provider access modes, persistent quote/deal/runtime allowances, pause and recovery controls, and supervised builtin workers.
- Expiring invitations with immediate revocation; native CLI/MCP token-file transport over HTTPS.
- Fixed, schema-checked HTTPS JSON operations with provider-held credentials and finite call, byte and deadline limits.
- Clearer marketplace service descriptions, agent-readable service links and downloadable QR codes.
- Release gates include Linux isolation, Docker integration and installation checks. Unsupported GPU execution is refused.
Payment rails remain deferred. Protected services use direct HTTPS invitations; public marketplace admission still requires anonymous canaries. Resource allowances are not monetary caps: base infrastructure and rejected traffic can still incur cost. No stable-product qualification is claimed.
Kernel artifact bytes, hashes, signatures and conformance vectors are unchanged. See docs/HTTP_SERVICES.md and docs/CONFIGURATION.md for setup and limits.
Froglet v0.4.5 public beta
Froglet public beta v0.4.5 keeps native publishing from attempting legacy marketplace registration with a loopback HTTP address. A publisher now waits for an approved public transport (or uses an explicitly configured public HTTPS origin); exact publication approval and signed protocol artifacts are unchanged.
Validation: full public repository checks, locked dependency audit, website tests and build, macOS release packaging and installer smoke, and a loopback-only startup smoke against the production marketplace. The stable release label remains gated on the full clean-machine, agent, and first-time-user qualification.
Froglet v0.4.4 (public beta)
Public beta release of the native Froglet node and agent bridge.
The Linux x86_64 and arm64 archives are built in a pinned Debian 11 userland to avoid the glibc 2.39 requirement of v0.4.3's Ubuntu runner. The release workflow executes each binary in that builder before packaging. The macOS archive and Froglet protocol behavior are unchanged.
This is a beta. Clean-machine agent qualification across all three targets and the five first-time-user acceptance sessions remain open. The publisher's computer must stay online for a shared service to be available.
Froglet v0.4.3 public beta
Public beta: free native publishing, sharing, and requester invocation for supported macOS and Linux hosts.
This release adds the relay/Tor backend socket to native installation preflight. Setup now reports an occupied backend port before activating a service, instead of failing after installation. The release preserves existing identity and service state.
The stable label remains gated on clean-machine agent qualification and five first-time-user trials.
Froglet v0.4.2 — Public Beta
Froglet 0.4.2 is a public beta of agent-guided service publishing and sharing.
This release adds native installation and agent configuration, catalog preparation and subset previews, explicit publication approval, remote free-service invocation, shareable service pages, local status and recovery, and receipt verification. The supported native targets are Apple Silicon macOS and Linux x86_64/arm64. The computer hosting a service must stay online.
This beta is not the stable release: clean-machine qualification across both agents and all three platforms, backup restoration, and five first-time-user trials remain open. Free services are the supported first-use path; payments and managed hosting remain advanced.
The public website and hosted relay/marketplace are deployed separately from this source release. Check their live status before treating a service link as reachable.
v0.4.0
Full Changelog: v0.3.0...v0.4.0