Skip to main content
Folders are an organizational aid for project content. Use them when a project has many prompts, datasets, or supporting objects and the team needs a clearer structure. Keep folder names based on user-facing workflow or product ownership rather than temporary implementation details. Folders do not change runtime behavior. Moving a prompt, dataset, or tool into a folder helps people find it, but it does not change traces, evaluations, Improve cycles, or deployments.

​
Good folder patterns

  • Product area, such as Support, Billing, or Research.
  • Workflow, such as Onboarding, Refunds, or Escalations.
  • Release ownership, such as Production prompts and Experimental prompts.
  • Evidence type, such as Regression datasets or Golden datasets.
Avoid folders named after temporary experiments unless the experiment will remain visible to the team.

​
Before moving objects

Moving objects is safe for organization, but review the operational relationships first:
  • Prompt deployments still point to deployment snapshots.
  • Evaluators still belong to their prompts.
  • Datasets can still be linked through evaluators or dynamic prompt columns.
  • Tools can still be referenced by prompts.
  • Trace and Behavior evidence still belongs to the project.