Studio overview
Bicycle Studio is where you build things on top of your Bicycle data models: data apps (small screens that show numbers), functions (one job, one answer), agents (investigations) and workflows (steps that run in the background and send results). You do not need to be an engineer. A coding agent such as Claude Code or Claude Desktop, connected to Studio, does the building; you decide what it should build, check the numbers, and press the buttons that only a person may press.
Who this is for
- People who own a question (a product manager, an operations lead, an analyst, a founder) and want an app, a report or an alert without waiting for an engineering ticket.
- Engineers who want to know how it is built. See Architecture.
- Coding agents. Every page here has a raw markdown copy at the same address with
.mdadded, and the whole site is at /llms.txt and /llms-full.txt. The exact guide Studio serves to agents is under For coding agents.
The four things you can build
| You want | Build | In one line |
|---|---|---|
| Numbers, trends and breakdowns on a screen | a data app | A small web page bound to one of your data models. Composed from a description, or hand-built from a public template when it needs buttons that call functions. |
| One answer from one input, on demand | a function | A score, a transform, a label or an AI answer. Four kinds: Code, Ask AI, Sort into categories, Agent. |
| Judgement over messy evidence ("why did this order fail?") | an agent | A function that takes several AI steps and read-only lookups, under limits you set. |
| Steps on a schedule, results kept between runs, an email after a check | a workflow | Query, summarise, ask AI, screenshot an app, send. Every send can wait for your approval. |
Two more things are already built for you: Detect and Explain ("what changed in this metric, and why?") and app schedules (email a picture of an app view every Monday).
How the docs are organised
- Getting started: what Studio is and your first app in ten minutes.
- Building with a coding agent: connect Claude Code or Desktop, the start-here guide to give it, and what the agent will ask you.
- One section each for data apps, functions, agents, workflows, runs and traces and Detect and Explain.
- Limits, safety and permissions and Troubleshooting (every error code in plain words).
- Worked examples: six complete builds you can copy.
- For coding agents: the raw guide, and Architecture for engineers.
Three rules that keep you safe
- Nothing reaches other people without a person. Publishing an app, confirming a function's first publish, approving an email, sharing an app: these are done by you, in Studio. A coding agent gives you the link and waits.
- Everything runs as someone. An app runs as the person viewing it; a coding agent runs as you; a scheduled workflow runs as your workspace's service identity. What it can read is what that person can read.
- Every run leaves a trace. Functions, agents, workflows, analyses and schedules all show on the Runs page, with what ran, who started it, how long it took and what it cost.
Where Studio lives
Studio is part of your Bicycle workspace: https://app.bicycle.ai/<your-workspace>/apps/home. Its navigation bar has Apps, Functions, Agents, Workflows, Approvals and Runs, and a Back to Bicycle link.