AgentPack 1.5.0

Cross-agent package manager for MCP servers and plugins — Claude Code, Codex and OpenCode.

Download: AgentPack-1.5.0-win-x64.exe (Windows x64, portable, unsigned). Requires Node.js 22.17+ with npm on PATH; the app bundles Electron but launches MCP servers with the machine's Node.

Run AgentPack-1.5.0-win-x64.exe --demo for a sandboxed demo with three sample agent configs and a nested Next.js + Supabase project. Without --demo it reads and writes your real agent configuration.

What changed since 1.4.0

A startup sequence. The device opens on its hinge, its screen lights with the AgentPack wordmark, the camera pushes in, then pulls back and leaves that wordmark sitting in the app's own header. About two and a half seconds, and any click or keypress skips it.

It ships no new assets. The clamshell is two inline SVGs on HTML wrappers, so the hinge is a real 3D rotation and the artwork stays crisp at the zoom peak — a flat image could not have opened without being cut into layers, and would have blurred. The wordmark reuses the pixel typeface already vendored for the interface. No images, no audio.

The hand-off is measured, not hardcoded. The wordmark is positioned at the header's own rect and animated from the device screen, so the final keyframe is transform: none. It lands on the same pixel the header occupies, at any window size.

It costs no startup time. The intro overlays a fully mounted app rather than gating it, so the agent detection and registry load that run on mount resolve while it plays. Verified: three capability cards were already rendered underneath 200ms into the animation.

Motion preferences. The sequence respects prefers-reduced-motion, with one deliberate exception: --demo plays it regardless. Windows reports reduced motion far more often than expected — it does on the machine this was built on, even with the Settings toggle appearing to be on — and without that override the sequence would silently never play on a demo machine. AGENTPACK_BOOT=1 forces it on anywhere; AGENTPACK_NO_BOOT=1 forces it off.

Everything else is unchanged from 1.4.0: 30 capabilities across 12 MCP servers and 18 plugins, four packs, and recommendation rules that close the gap between what the detector recognises and what it can offer.

Verification for this build

Check	Result
TypeScript	clean
Focused regressions	24 / 24
Self-check suite	75 passed
Engine acceptance	14 / 14, configs restored byte-identically
Renderer UI (real preload + IPC)	8 / 8
Smoke	ok, no console errors
Packaged portable launch	exit 0

The animation itself was checked frame by frame rather than asserted: captures at 200 / 800 / 1400 / 1900 / 2300 / 2900ms show the closed device, the panel mid-swing, the lit screen, the camera push, the logo in flight over the revealed app, and a clean finish with the overlay gone. The skip path was verified to leave no stray elements and a still-draggable window.

Known limits

Unchanged. A green tool list proves the server starts and answers, not that a credential is valid. Plugin status reads Configured, never Verified, because a plugin loads inside the agent where we cannot see it. Context figures are tool-schema estimates (characters divided by four), not billed tokens, and apply to an agent's next session. The artifact is unsigned. Full assessment: docs/READINESS.md.

Demo script: docs/DEMO.md.

SHA-256: 130F75D91DFD0F506E51B89300B657FCA7F81ECD1F525E568CA9D054582EB173