| Data model | A named set of metrics and dimensions Bicycle can answer questions about. Every app is bound to exactly one model. A model's data has a start and an end date, and the end is often not today. |
| Data app | A small web page that shows numbers from one model: tiles, trends, breakdowns, tables, and optionally buttons that run functions. It has versions; a version is private until it is published. |
| Publish | Make a version the live one. A published app is readable by everyone in your workspace who can see it. Publishing is always done by a person. |
| Function | One job with one input and one output, run by Studio on demand. Four kinds: Code (Python), Ask AI (one AI answer), Sort into categories (a label from a fixed list) and Agent that investigates. |
| Agent | A function that takes several AI steps and read-only lookups to reach an answer, under limits you set (steps, cost, time). It reads; it never changes anything in another system. |
| Workflow | Steps that Studio runs in the background: on a schedule, when someone presses Run, or when an app calls it. Steps fetch data, summarise, ask AI, take a screenshot of an app and send the result by email or through one of your connected tools. |
| Send and approval | A send is the only way anything leaves Bicycle. A send can wait for a person to approve it in Studio's Approvals inbox; sends through connected tools (Slack, Jira, PagerDuty) always wait unless an admin has allowed that tool to run on its own. |
| Run and trace | Every time a function, agent, workflow, analysis or schedule runs, Studio records one run with a trace: what it did, step by step, who started it, how long it took and what it cost. See the Runs page. |
| Connection | A tool your workspace has connected to Bicycle (Jira, Slack, Atlassian, a warehouse). An agent can be given read access to one; a workflow send can post through one. |
| Detect and Explain | Built-in analysis: which segments of a metric moved unusually (Detect) and what drove the change (Explain). See Detect and Explain. |
| Coding agent | Claude Code or Claude Desktop connected to Studio through MCP. It reads your models, writes code and specs, and calls Studio's tools. It cannot publish, approve or share without you. |
| MCP | The connection standard that lets a coding agent use Studio's tools. You connect it once; see Connect a coding agent. |