MCP path
Native or remote MCP app/connector support is the approved host path once each surface is shipped and verified.
The portable Kit that carries your Personal OS into the AI tools you use
Vizionflo Kit is the portable doorway. Your encoded context travels with you through the current signed package and curated bundle, with MCP-compatible hosts, plugin/package channels, and CLI access as the roadmap lights up. Same Personal OS, across supported surfaces as they become ready. Designed to pair with Vizionflo Studio in the planned subscription. During the private preview, Circle members get Kit access first.
AccessPaired with Studio
Current pathPackage + bundle
RoadmapMCP / plugin / CLI
One Personal OS across the AI surfaces you use
Plugin package
Signed package access for Claude Code, Codex, and adjacent agent runtimes carries skills, commands where supported, MCP scaffolds, prompts, templates, and your corpus.
Curated bundle + CLI
Drop-in files support ChatGPT, Claude.ai, and other web AI hosts now. Terminal-first CLI access remains a power-user roadmap surface.
Vizionflo Kit is paired with Studio
The planned Vizionflo subscription pairs Studio, where you build the foundation, with the Kit, which carries it outward. No separate purchase. While the preview stays private, Kit access ships to Circle members first. The Kit's signed package, curated bundle, and planned MCP/plugin/CLI paths are access points into the Imprint methodology, not standalone offerings.
- Designed to sit in the core Vizionflo product relationship alongside Studio.
- Current package and curated-bundle access with deeper host paths planned.
- Same Personal OS, carried into more surfaces as support is verified.
Kit has a clear path from context to action
Each offering keeps the same Vizionflo principle: make context visible, keep user judgment close, and turn the work into something portable.
Build the foundation in Vizionflo Studio
Shape the foundations inside Studio so the Kit has real material to carry.
Install where you work
Start with the signed package or curated bundle, then use deeper MCP, plugin, or CLI paths as they become ready for the host you use.
Carry your Personal OS
The same system shows up in the supported surfaces you use. Your AI tools work from something real instead of generic prompting.
What leaves the room stronger
- Personal OS context that can travel beyond the web workspace.
- Kit access that arrives with the core Vizionflo relationship, not a separate purchase.
- A current package/bundle path with MCP, plugin, and CLI expansion planned.
Who this is for
- Builders already using Claude Code, Codex, Cursor, or other agent runtimes.
- ChatGPT, Claude.ai, and web AI users who want their context to travel.
- Anyone whose Personal OS needs to follow them into more than one tool.
Start with Studio. The Kit travels with the work
Vizionflo Studio and Vizionflo Kit form the core product relationship. Join the Studio waitlist and the Kit path follows.