ZacharyZhang-NY
9f2c3fee29
The 1.4.0 Windows build carries everything since 1.3.0: Kimi and Kimi CN as OpenAI-compatible providers, Kimi Code plan sign-in via the official RFC 8628 device flow with token refresh, and official provider logos bundled into the app for onboarding and Settings. Shipping steps, each verified: unit suite green on the release tree -> signed NSIS build (both humanizer skill variants bundled) -> uploaded to R2 and probed 200 at full size (102,605,596 bytes) -> manifest bumped (Windows v1.4.0; macOS stays on its live v1.3.0 DMGs) -> landing e2e 12/12 (PW_CHROME fallback) -> Pages deployed -> production /api/download 302s to the 1.4.0 exe and download-stats serves -> superseded 1.3.0 exe deleted (404 confirmed) -> nine orphaned 0.4.182-era objects (installer, mac zips, blockmaps, stale electron-updater latest*.yml) purged; publish: null means nothing consumes them. Bucket now holds exactly the three assets the site links.
AgentCompany Landing
Next.js landing page for the AgentCompany desktop release lane.
Copy Sources
| Surface | Source |
|---|---|
| Download cards | landing/lib/release-links.generated.ts |
| Platform FAQ | landing/lib/platform-support.ts |
| Hero, How It Works, software JSON-LD features | landing/lib/product-narrative.ts |
| Runtime download URLs | generated from scripts/generate-landing-release-links.mjs |
The public story mirrors the first-run desktop flow: Welcome, Requirements, Providers, Company, Team Models, Mode, Mission, Launch.