PromptRails
Sign inGet started →
View as Markdown

Assistant

Use the built-in PromptRails Assistant to draft, inspect, and update workspace resources from inside the product.

Best for

New teams, product owners, and engineers evaluating the workflow

The PromptRails Assistant is the product-native helper for working inside a workspace. Use it when you know what you want to build, inspect, or change, but do not want to start by finding every resource and setting manually.

The Assistant opens beside the workspace, so you can ask for help while looking at agents, traces, settings, runs, and workspace health.

What It Can Do

The Assistant is most useful when the work starts as a plain-language request and ends in a visible workspace resource, run, or decision:

  • Build and edit workspace resources -- create or update agents, prompts, prompt versions, agent versions, data sources, MCP tools, guardrails, and memories.
  • Inspect runtime behavior -- review executions, traces, chat sessions, cost, latency, tool calls, blocked responses, and pending approval requests.
  • Operate the workflow -- run an agent, send a chat message to an agent, query a connected data source, or approve and reject human-in-the-loop requests.
  • Configure access -- find credentials, data source schemas, MCP templates, installed tools, masking controls, notifications, and API settings without memorizing navigation.
  • Improve the product text -- turn rough behavior notes into clearer prompt instructions before saving a version, or ask what should be evaluated before shipping.

The Assistant can take action, but it does not replace review. Treat its output like a draft or an operator action: inspect proposed changes, run the agent, and use traces or evaluations before shipping.

How It Fits The Product Loop

The Assistant sits beside the same surfaces you use manually:

1Describe the task
→
2Review the suggested setup
→
3Run the agent
→
4Inspect the trace
→
5Save the version

It is especially helpful when a non-technical teammate needs to explain desired behavior and an engineer wants the final configuration to stay visible, versioned, and traceable in Studio.

Technical detailsHow the Assistant works

The Assistant works inside the active workspace. It uses the same product resources you use manually: agents, prompts, versions, credentials, data sources, MCP tools, guardrails, memories, executions, traces, chat sessions, and approvals.

When it needs to do work, it can call workspace-scoped tools, stream progress back into the panel, and refresh the affected product surfaces after changes. It can also use page context from "Ask Assistant" entry points, so a question from an agent, trace, or settings page starts with the right resource in view.

Any generated or suggested configuration should still follow the same workspace controls as manual changes: roles, credentials, masking, approvals, version history, traces, and audit logs.

For production changes, keep the same release discipline you would use for manual edits:

  • Run the agent with representative inputs.
  • Inspect the trace and cost.
  • Add evaluation cases for important behavior.
  • Commit a prompt or agent version with a clear message.
  • Quickstart -- Use the Assistant as one path to the first useful run
  • Agents -- Review and run the resources the Assistant helps create
  • Tracing -- Inspect the run after the Assistant helps configure it
  • Workspace Management -- Workspace settings and audit trail
PreviousQuickstartNextChangelog