Public roadmap
Skills first. MCP and CLI package management next.
Fygment's full vision is a package manager and control plane for the agent toolchain. The live product is intentionally narrower: a governed AI Skills registry for controlled pilot users, with Codex, Claude, MCP setup, lockfiles, and team workflows staged behind clear availability labels.
Fygment starts as a governed registry and package manager for AI Skills.
Skills registry
Create, import, package, approve, export, and govern AI Skills inside a workspace.
GitHub and ZIP import
Bring in a real Agent Skill from GitHub or upload a validated package with checksum-backed storage.
Workspace governance
Use proposals, lifecycle states, audit history, ownership, and policies for the Skills pilot.
The app explains state and generates commands while the CLI performs local actions safely.
Codex and Claude install path
Codex and Claude-family harnesses are the first official targets for install, check, and update hardening.
MCP setup
MCP connection setup, metadata, guided CLI setup, and copyable configuration are available as an alpha workflow.
Readiness diagnostics
The CLI and dashboard guide login, import readiness, target harness setup, and next actions.
Team pilot readiness
Small-team dashboards and settings now summarize members, teams, shared Skills, approvals, install risk, harness health, source alerts, a workspace alert queue, delivery readiness, and manual pricing beta boundaries.
Team onboarding discovery
Invite links and verified-domain onboarding prompts now route teammate requests into owner/admin review from Members without exposing private workspace details.
Full control plane
RoadmapThe broader package-manager vision remains visible, but not presented as production-ready.
Skills lockfile and sync
A Skills-only fygment.lock, local inventory, and reproducible sync flow come before arbitrary CLI management.
Notification delivery and billing
External delivery automation, billing automation, commercial account management, and hard plan enforcement wait until pilot workflows are proven.
Enterprise and security depth
Enterprise identity, compliance evidence, advanced deployment, public marketplace, and deep security scanning stay long-term.
Roadmap note: enterprise identity, compliance evidence, advanced deployment, public marketplace, and deep security scanning remain long-term and are not part of the current pilot promise.
Short and midterm sequence
What ships before broad control-plane claims
Each batch keeps the public promise tied to a concrete availability label. Skills stay first; MCP lifecycle management, arbitrary CLI management, marketplace, and enterprise/security depth stay staged.
Batch 1/NowLive
Truthful public positioning
Show the full vision with clear Live now, Alpha, and Roadmap boundaries.
Batch 2/NowIn progress
Skills pilot completion
Polish create/import/share/approval for super-users and vibecoders.
Batch 3/NowAlpha
First writable harness install/check/update
Make the first writable local Skill targets reliable while keeping broader harness support explicit.
Batch 3a/NowAlpha
Team onboarding and invite discovery
Support invite-link onboarding and privacy-safe verified-domain prompts with owner/admin approve or deny from Members.
Batch 4/NextIn progress
Public CLI distribution
Ship npm first, then curl, then Homebrew only after release smoke is repeatable.
Batch 5/NextAlpha
Skills lockfile and local inventory
Make the package-manager claim credible for Skills before expanding to MCP servers or CLIs.
Batch 6/NextAlpha
MCP setup alpha
Manage MCP setup metadata and health for Codex and Claude without overclaiming full lifecycle management.
Batch 7/MidtermAlpha
Team registry, notifications, and pricing beta
Prepare 2-5 person team pilots with team sharing, derived approval/source/install/harness/consistency alerts, on-demand email digest alpha, and truthful manual pricing-beta boundaries.