The Portal
The one layer that carries what you've built into the AI tools you use. You reach your own system from the tool you're already in.
PortalYour Personal OS, everywhere you work
Your Personal OS shouldn't be stuck in one place. The Portal is the access layer that carries approved context from Vizionflo Studio into the tools where you work. The current implementation includes the signed Foundations Kit, a local read-only Vizionflo MCP teaching corpus, a CLI scaffold, and host plugin metadata. Vizionflo MCP paired with plugin packaging is the largest long-term access path, while the CLI remains the advanced direct door. Your kits are user-owned exports, never another product you have to buy.
LayerPortal
Current pathKit + local MCP
ArtifactsYour kits
Your context everywhere, without turning portability into another product
Access points
The signed Foundations Kit, local read-only MCP teaching corpus, CLI scaffold, and host metadata exist today. Live Personal OS access, hosted connections, writes, accounts, and public listings remain gated.
Your kits
You build kits from your system for a specific tool, collaborator, or client. Your kits belong to you and travel with the work.
The Portal is paired with Studio
Vizionflo pairs Studio, where you shape the foundation, with the Portal, the durable access layer. The signed Foundations Kit and local read-only MCP exist now. Permissioned MCP paired with plugin packaging is the primary long-term door, while the CLI is the advanced direct door. These are access points into your own system, not separate products.
- Designed to sit in the core Vizionflo product relationship alongside Studio.
- Current signed kit, local read-only MCP, CLI scaffold, and host metadata, with deeper host paths gated.
- Same Personal OS, carried into more surfaces as support is verified.
Portal 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 Core, entities, standards, and artifacts inside Studio so the Portal has real context to carry.
Access it where you work
Start with the signed Foundations Kit or another supported local path. Permissioned MCP and plugin access can deepen as each host, trust boundary, and support path is verified. The CLI is the advanced direct option.
Build your kits
Export the slice of your system a specific tool, collaborator, or client needs. 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.
- User-owned kits that carry the right slice of the system for the moment.
- A current signed kit and local read-only MCP foundation, with permissioned plugin access and richer CLI interaction staged behind verification.
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 Portal travels with the work
Vizionflo Studio and the Portal form the core product relationship. Join the Studio waitlist and the access path follows.