Request access

Features · Agents

Agents and workflows, versioned like prompts.

An agent is instructions plus settings. A workflow is steps that pass results on. Both deserve a history.

Agents: instructions with a history.

An agent holds its instructions, a provider and a temperature. Keep the system prompt that makes it behave in one place, commit changes with a message and branch to try another approach. The starter agent, The critic, names the weakest sentence of a draft and offers one replacement.

  • Providers: internal, Anthropic, OpenAI, Google, Vercel
  • Instructions and temperature are versioned
  • Tags, collections and sharing like any asset
Create an agent
{ "tool": "agents", "action": "create",
  "args": { "title": "The critic", "provider": "internal" } }

Workflows: steps in order.

A workflow is a list of nodes. An input node takes your text, a prompt node runs one of your prompts on what came before. Change a prompt and every workflow that uses it follows. Workflows have versions too.

draft-then-sharpen.workflow3 nodes
a step can be any prompt in your library

Honest note

Running them is your AI’s job.

  • Pre-beta
    Store, version, share, fetch

    All work now. Your AI reads an agent or a workflow over MCP and runs it.

  • Planned
    Running agents and workflows inside the app

    Switched off during the pre-beta.

Questions

About agents.

Can an agent in Prompt Verse run by itself?

Not in the pre-beta. You store, version and share agents and workflows, and your AI runs them. The running is done by the AI you bring.

Give your agents a place to live.