New Rich Editor is live: Build better context with reusable blocks

Public API v0 gave teams a programmable foundation. CLI v0 brought that into local, file-first workflows. MCP v0 connected the same assets to coding agents.

Now we are shipping the next major layer: the new Rich Editor with reusable blocks architecture.

We built it for one simple reason. Writing great prompts and context is not only about content quality. It is also about structure, reuse, and long-term maintainability.

Why this matters

As teams scale, their assets get longer and more complex.

People need to:

• organize content clearly
• update shared instructions in one place
• avoid copy-pasting the same sections into many assets
• keep version history clean while editing fast

Without a structured editor, this becomes hard quickly. Teams duplicate content, drift over time, and spend too much effort on manual consistency checks.

The new Rich Editor solves this by making structure and reuse a first-class part of authoring.

What is new in the Rich Editor

The new editor introduces a block-first writing model with practical tools for daily work:

• slash commands for fast insertion
• rich formatting for readable, scannable assets
• block-level structure with headings, lists, toggles, callouts, and code
• reusable references so teams can avoid duplication
• auto-save for edits and manual version checkpoints for milestones

This gives teams a better authoring loop:

1. Write and structure content in blocks.
2. Reuse key instructions across assets with references.
3. Let edits auto-save while you work.
4. Save named versions when a milestone is ready.

Why reusable blocks are important

Reusable blocks are the core architecture change.

Instead of repeating the same instruction in many assets, you can keep a single source and reference it where needed.

That means:

• fewer inconsistent copies
• faster updates across your library
• lower maintenance cost over time

For teams building serious AI systems, this is a big quality and reliability upgrade.

How this fits with API, CLI, and MCP

This release is not separate from the rest of the platform. It completes the workflow.

• API v0 lets you automate asset operations.
• CLI v0 gives local sync and file-based workflows.
• MCP v0 lets coding agents use your asset library.
• Rich Editor gives the best in-product authoring experience on top of the same asset model.

One intelligent context layer, multiple ways to work.

Quick start

The fastest way to get started is the Editor docs:

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

From there, you can explore blocks, formatting, and keyboard shortcuts.

Example authoring workflow

A practical workflow for a team prompt library:

• Create a reusable block for output constraints.
• Add it into multiple prompt assets using references.
• Update the source block once when policy changes.
• Save a new version checkpoint and review diffs.

This is exactly the kind of workflow we designed the new editor to support.

Who should use this now

This release is a strong fit if you:

• maintain many prompts, contexts, and skills
• need consistent structure across assets
• want less duplication and easier updates
• want fast editing without losing version control

Start now

If you already use API v0, CLI v0, or MCP v0, the new Rich Editor is the natural next step.

Open an asset, start writing with blocks, and turn repeated content into reusable building blocks.