Set up Vessica Studio

Install the CLI and Codex plugin

The CLI owns the file contract, builds, local server, exports, and Railway workflow. The plugin gives Codex six deck-aware skills that read the same canonical instructions embedded in vstd.

1. Install the CLI

You need Go 1.26 or newer and Git. The repository’s go.mod pins the supported toolchain.

go install github.com/vessica-labs/vessica-studio/cmd/vstd@latest
vstd version

If your shell cannot find vstd, add Go’s binary directory to PATH:

export PATH="$(go env GOPATH)/bin:$PATH"

To build from source instead:

git clone https://github.com/vessica-labs/vessica-studio.git
cd vessica-studio
make build
./vstd version

2. Install the Codex plugin

Codex desktop or ChatGPT desktop

Open Plugins, add the Vessica Studio marketplace if it is not already configured, install Vessica Studio, then start a new task. Installed plugin skills become available to new Codex tasks.

Codex CLI

codex plugin marketplace add vessica-labs/vessica-studio --ref main
codex plugin add vessica-studio@vessica-studio

Start a new Codex session after installation. In the interactive CLI, /plugins opens the plugin browser if you prefer the visual route.

The repository also includes legacy thin prompt launchers. Use them only if your Codex environment does not support plugins:

git clone https://github.com/vessica-labs/vessica-studio.git
cd vessica-studio
./codex/install.sh

3. Verify the installation

vstd skill
vstd skill conventions
vstd skill slide-edit
codex plugin list

You should see these six workflows:

Skill	Purpose
`deck-new`	Frame, outline, create, and visually review a new deck
`slide-add`	Insert context-aware slides into an existing narrative
`slide-edit`	Change content or layout while preserving the companion contract
`deck-fork`	Tailor a deck for a client, audience, industry, or event
`deck-review`	Run full visual, narrative, and companion QA
`market-refresh`	Re-research dated claims and update time-sensitive slides

4. Optional AI setup

Core file, build, serve, and presentation workflows do not require an API key. Image generation, Vessica voice, transcription, audience chat, and agent tools do.

export OPENAI_API_KEY="sk-..."
vstd key check

Prefer a secret manager for long-lived credentials. Never put an API key in studio.yaml, a slide, a manifest, or Git history.

5. Create a studio

vstd init my-studio
cd my-studio
vstd new product-story --title "Our Product Story"
vstd serve product-story

Next: ask Codex to build the deck or learn the web editor.