Skip to main content
PYRAMYD
Solutions

Foundation

GA

Prompts Manager

Edit, version, and govern the prompts used by APEX skills and agents across the platform.

4 top capabilitiesIn the Product Graph

What it is

Prompts Manager.

A prompt is one of the platform's universal node types rather than a settings row, so it carries an owner, a sharing scope and the same row-level security as every other entity — and gets the node card, the action menu and access management without special-casing. Each prompt holds more than its text: declared variables, input and output schemas, a tool policy, guardrails and an evaluation rubric, across seven prompt types. Every runtime that uses prompts — agent instructions, retrieval synthesis, approval gates, slide generation — stores a pointer to the saved prompt and resolves it through one shared primitive, so editing the prompt changes behaviour everywhere it is referenced without touching a flow. A prompt can pin the model it runs against, and forking records the parent rather than overwriting in place.

See it in the product

Prompts Manager in the workspace.

Top 4 capabilities

The most impactful capabilities.

Each capability is the parent of dozens of typed features in the production taxonomy. Hover any feature in Studio to drill into the underlying nodes.

01

A prompt is a universal node type

Because a prompt is a first-class node rather than a settings row, it inherits the node card, the action menu and access management for free — and the same three-tier row-level security that protects everything else.

02

One resolver serves every runtime

Every consumer stores a pointer to the saved prompt alongside its original inline text, and one resolver prefers the pointer. Editing the saved prompt changes behaviour everywhere it is referenced without touching a single flow.

03

A typed contract, not a text blob

Beyond the message bodies a prompt carries its variables, schemas, tool policy, guardrails and rubric, across seven prompt types. A render endpoint substitutes the declared variables server-side, so callers receive a resolved prompt rather than doing their own templating.

04

Pinned model, pinned agent, forked lineage

Pinning the model means the same text cannot silently drift onto a different one, and forking records the parent rather than overwriting in place — so where a prompt came from stays answerable.

See Prompts Manager running against your category.

30-minute walkthrough. We'll filter the workspace to your category and walk through the top capabilities live.