VortiDeckShowcase 01
Built with Real Tools
The assistant works through the same parts you use: it lists your flows, macros and decks, then creates flows (saved switched off), saved actions, deck pages and buttons, and overlay drafts.
Features08 · AI Assistant
Set It Up
by Asking
Describe what you want and Studio Copilot builds it with VortiDeck's own tools: flows, deck buttons, overlays. It shows each live change first, and nothing changes until you allow it.
AI assistantActual app recording
Four steps.
Add Your AI Provider
Use OpenAI, Anthropic, OpenRouter or Azure with your own key. Keys are stored in your system keyring, not in a file.
Ask for What You Want
Open Studio Copilot from the title bar and describe the result: a button that switches your scene, a flow for a chat command, a draft overlay.
Approve Live Changes
Reading your setup never asks. Before a live change, like assigning a deck button or switching a flow on, you see what it will do and choose Allow once, Allow for this chat or Deny.
Keep Going by Hand
Everything the assistant makes is a normal flow, button or overlay. Open it in the editor and change it like anything you built yourself.
Showcase 02
You Approve Each Change
Reading never asks. Live changes ask by default, and you can make it stricter or looser. Package permissions are never granted by the assistant: they always go through your own consent dialog.
In practice.
Set Up a New Scene
Ask for a deck page with buttons for your scenes and macros, and approve each assignment as it happens.
Explain Your Setup
Ask what a flow does, which buttons run a macro or what happened in the event log. The assistant reads your setup before it answers.
Your Own Assistant
Connect Claude Desktop, Cursor, VS Code or Claude Code over a local MCP server. Each app gets its own key and starts read-only.
Next step
Describe It, Approve It
Download VortiDeck for free, add your AI provider and ask Studio Copilot to set up your first button.