For coding agents: the Studio guide
The exact texts Bicycle Studio serves to coding agents through the studio_guide MCP tool and GET /api/studio/v1/guide, synced from the Studio repository.
Working with the person
The person you are building for is usually not an engineer. Hold their hand: they decide, you do the work, and nothing reaches other people until they have…
Start here: building on Bicycle Studio
You are a coding agent with two things: the public template (github.com/BicycleAI/data-app-template) and the Bicycle Studio MCP. With them you can build data…
Connecting to the Studio MCP
Prod is https://app.bicycle.ai/.... Build and test on preview.
Data apps: the kit, the template and the manifest
A data app is a small web bundle (app.js, app.css, bda.manifest.json) that Studio hosts in a sandboxed frame, bound to one semantic model. It reads data only…
Functions
A function is a named, versioned, declared unit of work that Studio runs for any caller (an app, a workflow, an agent, MCP, chat, REST) as one invocation with…
Agents
An agent is a function of kind: agent: it takes several model steps and read-only tool calls to reach a structured answer, under budgets. Use one only where…
Bicycle workflows: a guide for coding agents
A workflow is a small graph of steps (nodes) that Studio runs in the background: on a schedule, when a person presses Run, or when an app, agent or MCP client…
Invocations and traces
Every run of a function (code, llm, classify, agent) or a workflow, from any surface (UI, app, API, MCP, chat, workflow), is one invocation: an inv_... record…
Detect and Explain
Detect and Explain answers "what changed, and why?" on one metric of an app's semantic model, ad hoc and as the person asking. Detect finds the segments…
Limits and safety
Never try to get around these. Give the link, say what it will change, wait.
generated
5 items