Glossary
Understand common Runner terms used across the workspace and documentation.
Entry path: Runner documentation → Help and reference → Glossary.
| Term | Meaning in Runner |
|---|---|
| Agent | Runner capabilities that use reusable Skills and project or workspace Memory. |
| App | A connection between Runner and another service, or an agent-level capability shown on the Apps page. |
| Artifact | An output produced during a task or workflow, such as a report, file, preview, or earlier task result. |
| Automation | A configured action that runs from a trigger or schedule when available. |
| Chat | A project conversation where you request and review work. |
| Checkout | The customer path that collects shipping and payment to create an order. |
| Credits | Workspace usage allowance shown in the current product. The live billing page is authoritative. |
| Design Mode | A storefront editing view for selecting and changing visible content. |
| DNS | The internet records that connect a domain name to the correct storefront. Runner shows the values to copy into your domain provider. |
| Drafted | A store without a current live publication. |
| Endpoint | A destination address used by an integration, such as a webhook receiver. Treat endpoint addresses and their credentials as sensitive. |
| Experiment | A controlled comparison used to measure a change when the feature is available. |
| Fly | A conditional guided mission workspace. |
| Fulfillment | The work of preparing and sending items from an order, including any supported supplier or shipping-provider steps. |
| Memory | Saved context Runner can reuse at its defined scope. |
| Media Library | The project’s place for generated or uploaded visual assets. |
| Preview | The current project storefront view before or independent of publication. |
| Project | The store-specific Runner workspace containing chat, storefront, operations, apps, and tools. |
| Provider | An outside service connected to Runner for payments, shipping, email, sourcing, analytics, or another supported task. |
| Publish | Create the first live version after requirements pass. |
| Republish | Send newer draft changes to a store that already has a live version. |
| Research | A conditional workspace for structured business studies and reports. |
| Session (Analytics) | A recorded storefront visit used in traffic and conversion reports. It is different from a signed-in account session. |
| Session (Account) | A signed-in Runner connection on a browser or device that can be reviewed or revoked in security settings. |
| Simulation | A tool for running a configured scenario and reviewing its result when available. |
| Skill | A reusable set of instructions or workflow that Runner can apply to work. |
| SKU | A store-defined code used to identify a product or variant for inventory and operations. |
| Store Operations | Product, order, customer, promotion, shipping, sourcing, and store-management pages. |
| Task | A unit of work Runner tracks inside a conversation. |
| Variant | A purchasable version of a product, such as a particular size or color, with its own price or inventory. |
| Version | A saved storefront state shown in Version History. |
| Webhook | A configured delivery of a supported project event to another service. |
| Workflow | A reusable multi-step project flow when the feature is enabled. |
| Workspace | The team and billing boundary that contains stores, members, settings, credits, and notifications. |