Free code signing provided by SignPath.io, certificate by SignPath Foundation.
Official AgentDock Windows release executables are built from this repository by GitHub Actions. AgentDock-owned Windows executables are Authenticode-signed through SignPath.io when the SignPath Foundation production certificate is active. Third-party binaries, such as cloudflared, keep their upstream signatures and are not re-signed with the AgentDock certificate.
The signing build definition is .github/workflows/release.yml. Production signing is restricted to v* release refs from this repository, uses SignPath trusted-build-system and origin verification, and requires a manual approval before the release certificate can be used.
The release pipeline currently retains the existing AgentDock self-signed Authenticode certificate as a compatibility path until the SignPath Foundation production certificate is active for normal releases. A self-signed certificate is intentionally not added to the Windows trusted-root store.
Desktop self-update therefore verifies a downloaded Windows Setup in this order:
- Prefer the normal Windows
WinVerifyTrustpolicy. A publicly trusted Authenticode signature passes here. - Only when Windows returns
CERT_E_UNTRUSTEDROOT, require the currently installed official AgentDock executable to have the same trust result and require the Setup signer certificate thumbprint to exactly match the installed executable signer thumbprint. - Any unsigned file, signature/hash failure, different signer, or other trust error is rejected.
This compatibility rule does not trust arbitrary self-signed certificates and does not modify the Windows trust store. Once formal releases use a publicly trusted certificate, self-update naturally remains on step 1.
AgentDock is currently maintained by a single trusted maintainer:
- Authors / committers: @uvwt. The maintainer is trusted to modify the project source and build configuration without an additional review.
- Reviewers: @uvwt. Contributions from other authors are reviewed before merge.
- Approvers: @uvwt. Each production SignPath signing request requires manual approval.
AgentDock does not include usage analytics or telemetry.
AgentDock can communicate with networked systems when the user or operator explicitly configures or invokes features that require network access. Examples include configured remote MCP or plugin endpoints, Cloudflare Tunnel, and user-initiated update checks or downloads. Third-party services used by those features are governed by their respective privacy policies.
AgentDock does not silently upload local files or conversation data to a service operated by the AgentDock project.