Tools · Documents and apps

create_app

Changes things

Create an app: a small program saved in the workspace that can be run again later with use_app. Start from a blueprint or supply app.py.

When to use: When a task will be asked again — a weekly report, an intake step, a check you run every release — build an app instead of redoing the work. `create_app` writes it, `set_app_binding` wires a resource into it, and `use_app` runs it with input and hands you the result. An app is a directory with `app.py` exporting `run(input, env)`. It runs in a subprocess: `env` holds only the bindings you wired, and every call on them is gated exactly like the equivalent tool call. Start from `list_blueprints` when one fits; write `app.py` yourself when none does.

Example

The call

tool call
{
  "tool": "create_app",
  "arguments": {
    "name": "tip-calc",
    "title": "Tip calculator",
    "description": "Split a bill and add a tip"
  }
}

Needs an app workspace; see the Apps guide

So it isn't run here, and no output is shown: nothing on this page is made up.

Parameters

NameTypeDescription
name*stringLower snake case. Also the name it is bound under.
title*stringHuman-readable title.
descriptionstringOne line on what the app does.
blueprintstringBlueprint id from list_blueprints, optional.
codestringThe app's app.py, defining run(input, env). Required unless a blueprint supplies it; overrides the blueprint's own app.py when both are given.

* required

Build documents, dashboards and small apps people can open.