CLI v0 is live: Bring Versuno into your local workflow

Public API v0 opened the door to automation. CLI v0 is the next step.

We built CLI v0 after API v0 for one reason. Many developers do their best work in the terminal, inside real projects, with files they can review and version.

Now you can manage Versuno assets from your local filesystem, not only from the web app.

Why this matters

Most teams want the same workflow for AI context that they already use for code.

They want to:

pull assets into a repo
edit in their own editor
review changes before shipping
push updates with clear version history

Without a CLI, this workflow is slower and more manual. People copy text between tools, lose track of what changed, and spend extra time on coordination.

CLI v0 makes this simple. It gives your team a clean, scriptable path between local files and the Versuno cloud.

What CLI v0 gives you

CLI v0 includes the core commands you need for daily work:

versuno init to scaffold a .versuno/ workspace in your project
versuno login to connect with your API key
versuno teams list and versuno switch to select workspace context
versuno assets list and versuno assets get to browse and inspect assets
versuno pull to sync cloud assets to local markdown files
versuno push to create new versions from local edits
versuno status and versuno diff to inspect changes before pushing

How it works

After versuno init, the CLI creates a .versuno/ folder with directories for prompts, contexts, personas, system prompts, and skills.

When you pull assets, each one is written as a markdown file with YAML frontmatter.

When you push changes, the CLI compares content hashes so only modified files are sent.

That gives you a Git-like workflow for your intelligent context layer:

sync down
edit locally
review
sync up as a new version

A quick local flow

Shell

// inside your project
versuno init
versuno login

// pick workspace and inspect assets
versuno teams list
versuno switch personal
versuno assets list

// pull one asset, edit it, then push a version
versuno pull <asset-id>
versuno diff
versuno push -m "Improve onboarding tone"

Example in a script

Shell

// !/usr/bin/env bash
set -euo pipefail

versuno pull "$1"
// your script or editor updates local file content here
versuno push -m "Automated refresh from release pipeline"

This is useful when you want predictable updates from CI jobs or internal tooling.

Built on top of API v0

CLI v0 is powered by the same Public API v0 foundation.

API v0 gives you direct HTTP control. CLI v0 gives you the same power in a local, file-first workflow.

If API v0 is the programmable interface, CLI v0 is the everyday operator experience.

Who should use CLI v0 now

CLI v0 is a strong fit if you:

manage prompts and contexts across multiple projects
want local editing and review before publishing changes
need repeatable release workflows with version checkpoints
want to connect Versuno to scripts and CI pipelines

Start here

The best starting point is the CLI docs:

https://docs.versuno.ai/cli/overview

From there, you can run your first pull and push in a few minutes.