Repository navigation
Firefly Weave 0.1.0a7 — saved platforms, REST actions without code, redesigned Studio
Pre-releaseConnect by address, call REST APIs without code, and a redesigned Studio
Alpha7 lets people connect the CLI, Studio, and desktop app to a platform by its address, sign in through their identity provider, and pick a workspace, without hand-written connection files. It adds REST actions built without writing a connector, and a redesigned Studio editor and shell.
Highlights
- Saved platforms and guided sign-in.
weave auth setup SERVERchecks the server, shows its published sign-in settings for review, signs in through the system browser (PKCE) or a device code, and saves the chosen workspace. Studio and the desktop app share the same saved platforms; tokens stay in the system credential store. - Published sign-in settings.
GET /api/v1/client-configuration, configured withWEAVE_CLIENT_SIGN_INandWEAVE_DISPLAY_NAME. Clients pin what was reviewed and refuse silent changes. - REST actions without code.
weave connector http-action,weave connector import-openapi --target builtin, guidedweave connections create, and the Studio New API action builder, on the built-inweave-http@2.0.0connector. - Redesigned Studio. A usable Call an action step, Decision rule rows with Otherwise, one lifecycle command, readable zoom, an inspector with Apply changes, a docked simulation, Build and Operate navigation, toasts with Undo, and local drafts.
- Runtime fixes found end to end. Port-free Keycloak loopback callbacks, supervised in-process native workers that replay capacity rejections, Studio retries for capacity rejections, and JWKS keys without
alg(Microsoft Entra ID) accepted by key type.
See the changelog for the full list.
Download and install
- CLI:
curl --fail --location https://github.com/fireflyframework/firefly-weave/releases/download/v0.1.0a7/install.sh | sh -s -- --version v0.1.0a7 - Browser Studio: the matching
firefly-weave-studio-0.1.0a7.zipand its.sha256. - Desktop: installers are attached below only for targets whose build succeeded; no filename in the documentation implies an installer was published. macOS bundles are ad-hoc signed, not Developer ID signed and not notarized; Windows publisher signing is not provided.
- Guides: installation, connect the CLI, Studio, desktop.
Verification
Unit and contract tests (3,100+), lint, types, strict documentation build, release preparation, and installed artifact closures passed, together with the Studio unit and browser suites on macOS and Linux and the desktop native tests on all four targets. Against a real local platform with Keycloak 26.7.4 on macOS: CLI sign-in and workspace selection, a no-code HTTP action run, the Studio sign-in journeys with the macOS Keychain, and device-code sign-in, reconnection, and export in a locally built desktop app.
Not verified: Microsoft Entra ID and other identity providers (Entra-shaped keys are covered by unit tests only), Windows and Linux credential stores, browser sign-in inside the desktop app, and the owned release-runner gates.
The database schema remains 0025_run_lifecycle; this release adds no migration. Existing --auth-config connection files keep working.