FyAgent v0.4.0
Important
FyAgent remains under active development. Back up important configuration
before upgrading, and review the trust and verification boundaries below
before installing.
The v0.4.0 publication contract requires exactly eight non-empty attachments:
four installers, three release-evidence JSON files, and one Sigstore bundle.
The workflow verifies that exact set before publication. This document does
not by itself claim that an independent post-publication re-download review
has been completed.
Warning
Do not infer Windows installer signing from the Release title or file name.
The formal workflow appends an evidence-backed signing table to the end of
these notes from the published signing-status.json.
If an installer row reports NotSigned, expect Windows SmartScreen to warn
and do not treat the file as Authenticode-signed. If it reports a verified
signature, confirm the publisher and timestamp status in the appended table,
then inspect signing-status.json for the signer- and timestamp-certificate
evidence. Verify the SHA-256 digest, source SHA, and attestation as well. Do
not disable SmartScreen or weaken organization-managed security policy.
Highlights
- V2 desktop shell: the production UI is a local desktop control center
with six primary pages: Agent directory, Models, Skills, MCP, Prompts, and
Memory. The previous leftover V1 renderer is not the shipped shell. - Agent catalog v4: QoderWork CN, TRAE Work CN, WorkBuddy, Grok Build,
Codex, Claude Code, and OpenCode share one product directory. Agent detail
keeps official links and direct capability jumps; it does not impersonate
each product's native settings UI. - Models by product contract: WorkBuddy and OpenCode use dedicated model
configuration. Claude Code, Codex, and Grok Build keep bounded Provider
quick setup. QoderWork CN states that third-party model configuration is
unsupported. TRAE Work CN observes vendor state and does not write custom
models into TRAE sqlite. - Skill 市场: Skills discovery pages the official Skill Hub catalog by
category, shows full card copy from 详情, and asks which target app should
receive the install. GitHub repository browsing is not part of this path. - MCP discovery: a curated catalog, including China-region connectors,
splits discover / configure / install. After a WorkBuddy connector is
written, the UI tells the user to trust it inside WorkBuddy. - Prompts and Memory: Prompts cover the existing native prompt
applications; Memory manages the current OpenClaw and Hermes long-term
resources. Browser preview remains native-only and does not seed business
data. - Shipped platforms: formal installers are Windows (x64 and ARM64 NSIS)
and macOS Universal (DMG and ZIP). Current-host development checks are not a
substitute for those installers.
Download and trust guidance
Windows
Choose the setup executable matching the machine architecture:
FyAgent-0.4.0-Windows-x64-setup.exe
FyAgent-0.4.0-Windows-arm64-setup.exe
Read the Windows installer signing status table appended to these notes and
verify the matching signing-status.json, SHA-256 digest, source SHA, and
attestation before installing.
macOS
Choose the DMG or ZIP; both contain the Universal application:
FyAgent-0.4.0-macOS.dmg
FyAgent-0.4.0-macOS.zip
The universal app is ad-hoc signed with no certificate identity and that
signature is verified before packaging. It is not signed with an Apple
Developer ID and is not notarized. The DMG container is unsigned. Gatekeeper
may therefore block the first launch. After first attempting to open FyAgent,
use System Settings → Privacy & Security → Open Anyway only after checking
the Release evidence. Do not disable Gatekeeper or remove quarantine metadata.
Exact Release attachment contract
The formal Release must contain exactly these four installer assets:
FyAgent-0.4.0-macOS.dmg
FyAgent-0.4.0-macOS.zip
FyAgent-0.4.0-Windows-x64-setup.exe
FyAgent-0.4.0-Windows-arm64-setup.exe
It must also contain exactly these four evidence attachments:
download-manifest.json
build-metadata.json
signing-status.json
artifact-attestation.sigstore.json
That is eight attachments total. The attestation has seven subjects: the four
installers plus download-manifest.json, build-metadata.json, and
signing-status.json. The copied Sigstore bundle is the eighth attachment and
does not attest itself. A missing, duplicate, renamed, empty, stale, or extra
attachment blocks publication.
Compatibility and upgrade notes
- The database schema version is 19. Existing FyAgent databases migrate forward
on first launch. Back up~/.fyagentbefore upgrading. - Existing provider, settings, Skills, backup,
fyagent://v1/import, and
third-party/v1contracts remain owned by their current implementation. - Installers from earlier 0.3.x Releases for operating systems outside this
shipped pair are not part of this version and are not a supported upgrade
path. - The known v0.3.0 MSI product is still removed synchronously before the NSIS
payload is written; unexpected migration results abort instead of continuing
with a partially replaced installation.
See the
installation guide
for platform-specific installation steps.
Known verification and security boundaries
- No Windows HIL was run for this delivery. Available evidence covers
executable contracts, portable tests, Windows-target compilation, native
x64/ARM64 build and packaging, signing or unsigned proof, exact-asset
verification, and review. It does not prove setup/uninstall behavior,
Explorer/UAC token handling, WebView2 user-data paths, Windows registry
behavior, PackageManager file-URI behavior, effective ACL enforcement or
mutation denial, terminal cleanup, or orphan recovery on a real Windows
10/11 x64 or ARM64 machine. - The current-user helper is not a protected process. Code already running as
the same Shell user can attempt memory, handle, or process manipulation within
that user's existing PackageManager authority. - The NSIS process lookup is a point-in-time safety check, not an atomic
interlock against a new process launch immediately before filesystem
mutation. Setup never force-terminates FyAgent or its helper. - A
NotSignedWindows result can trigger SmartScreen warnings. SHA-256,
source-SHA binding, and attestation are not a substitute for Authenticode
publisher trust. - The macOS application has only an identity-free ad-hoc signature; the DMG is
unsigned, and neither is Developer ID signed or notarized. - This Release does not claim independent post-publication re-download
verification, administrator-enforced repository rulesets, or a separate Main
Provenance attestation.
Version provenance
The annotated v0.3.0 through v0.3.4 tags remain at their original commits
and are not moved, deleted, or reused. FyAgent v0.4.0 is a new annotated tag
on the exact main commit whose push CI / Required result succeeded. A
failed Release workflow does not move that tag; a later source fix requires a
new stable version.
Source and licensing
FyAgent-owned components and modifications remain under the repository's
published PolyForm Noncommercial terms. Upstream-derived material retains its
original notices and license ancestry.
See
LICENSE,
LICENSING.md,
and
THIRD_PARTY_NOTICES.md.
Windows installer signing status
Mode: unsigned; source: 520ddb78fe5415377bd4222c926cda840fdbdbdb. The installer rows below are backed by the published signing-status.json and artifact-attestation.sigstore.json evidence.
| Architecture | Installer | Authenticode | Publisher | Timestamp | SHA-256 | Source SHA | Attestation |
|---|---|---|---|---|---|---|---|
| x64 | FyAgent-0.4.0-Windows-x64-setup.exe |
NotSigned |
Not signed | None | 6e56e405957e7bee79d6bd933490190069d308a8786f802a4feff25c8af27e19 |
520ddb78fe5415377bd4222c926cda840fdbdbdb |
artifact-attestation.sigstore.json subject FyAgent-0.4.0-Windows-x64-setup.exe digest sha256:6e56e405957e7bee79d6bd933490190069d308a8786f802a4feff25c8af27e19 |
| arm64 | FyAgent-0.4.0-Windows-arm64-setup.exe |
NotSigned |
Not signed | None | fd44d2a314a642f88b818428e34c1e155f081089bd8aa94c2f7dddfa040265ca |
520ddb78fe5415377bd4222c926cda840fdbdbdb |
artifact-attestation.sigstore.json subject FyAgent-0.4.0-Windows-arm64-setup.exe digest sha256:fd44d2a314a642f88b818428e34c1e155f081089bd8aa94c2f7dddfa040265ca |