Apper - App & Website Builder

Delete a secret by its numeric id from list_secrets.

delete_secret

Call this for every new user message, before any other tool EXCEPT the one that establishes projectId: for a brand-new app, call create_app first (no projectId exists yet); for an existing app whose projectId isn't already known in context, call search_apps first. Once you have a projectId, call this tool with it to record the user's message and get back a fresh messageId (an integer) that represents that one user message — every other tool call made while handling this message must pass this same messageId. When the user sends their NEXT message, call this again for a new messageId; never reuse a messageId across two different user messages. Exactly one call per user message: never call this a second time while still handling the same message, no matter how much work it involves or how many tool calls it takes. A multi-part request, a mid-task re-orientation, and a recovery from any failure — a failed edit, a failed build, an auth error — are all still the same user message, so they keep the same messageId.

generate_message_id

The source of truth for mock vs connected: a schema means connected, empty/error means mock. Also the only source of the numeric ids update_database needs.

get_backend_schema

Same as get_backend_schema, scoped to the tables you name (with or without _c) plus their RLS policies. Profiles always return in full. Use it once you know which table you're changing.

get_backend_schema_filtered

Check the build after a shouldBuild:true commit. Blocks server-side until a terminal status or ~75s — call it once, not in a loop. COMPLETED → preview_app. *-FAILED → read the error, fix the cause, commit again. Any other status → call once more.

get_build_status

The platform contract and build guidance for creating a new Apper app. Read once, before create_app.

get_create_app_instructions

How to turn a spec into a complete, distinctly designed product: the product brief to write first, the design decisions to derive from it, and the quality and completeness floors every screen clears — plus a design draw picked by the server for this app (shell, type, palette, signature) so it does not look like the last one. Call it once per new app, before writing files, and before adding any new page or surface to an existing one.

get_design_directives

Read one edge function's source by id. The repo copy lags — this is the source of truth.

get_edge_function

The platform contract and edit guidance for changing an existing Apper app. Read once per session, before the first edit.

get_edit_app_instructions

List env variable key names (values are never returned). Secrets live in create_secrets.

get_env_keys

The project's full file tree. Read it once per session before editing; a path missing from it does not exist. Not needed right after create_app.

get_project_tree

How to translate .policy.js files into the JSON RLS policies connect_database and create_database_components / update_database_components / delete_database_components accept. Not part of the create/edit instructions — read it once, right before the first call that carries an rls payload.

get_rls_policy_instructions

List the project's edge functions: id, name, executionUrl, isDeployed.

list_edge_functions

List secret names (never values). Check before creating one.

list_secrets

Edit existing files with {oldStr, newStr} replacements. oldStr is copied verbatim from read_files output and must occur exactly once (line endings normalized). A non-matching edit is skipped, not fatal — everything else still commits; failedEdits lists the skips and finalContent gives each patched file's current content for a retry. Not for new files.

patch_files

Return the app's preview URL. Only after get_build_status returns COMPLETED. Returns previewUrl, mock (true while the app runs on mock data) and, on mock, demoAccounts read from src/services/mockData/users.json (profile, email, password per user). Your reply ALWAYS contains the full previewUrl as plain text and, on mock, every demoAccounts entry one line each plus the "Connect to database" closing line — every time this tool runs, on create, edit and every phase. A `warning` or `usersWarning` in the result means the app is not finished: fix it, build, preview again.

preview_app

Read one or more files in a single call. Always read a file before patching or rewriting it — write_files replaces files whole, so writing from memory drops whatever you forgot. Returns each file's content and sha.

read_files

Find the user's Apper projects by projectId, name, subdomain, label, or preview URL. Omit search to list all. Every other tool needs a projectId from here or from create_app.

search_apps

Set a public VITE_* env variable. Rejects secret-looking keys. Edge-function variables are written by create_edge_function, not here.

set_env_key

Change existing Table | Field | RLS | Profile | Permission components in the connected database, batched into one call per approved change, then update the frontend to match. Each component carries its real id from get_backend_schema and ONLY the properties that change; a Field or RLS update also carries its tableId. A Permission is identified by profileName (bare, e.g. 'Member') plus tableName, with id 0. Access tokens are Full|Read|Create|Update|Delete|Inaccessible. Read get_rls_policy_instructions before any RLS component. Nothing is created here — use create_database_components.

update_database_components

Update an edge function by id; send only changed fields. A rename writes the new env var — update every call site.

update_edge_function

Commit complete file contents. shouldBuild:true = commit, build, deploy, and a new version in the user's history — exactly one true per user message, on the commit that completes it; every other commit in the turn is false (commit only). commitMessage names the files and the change, and the true commit's message covers the whole turn. The only way to create a new file. Send formatted source — one statement or JSX element per line; a file with no line structure cannot be patched reliably and comes back as a warning. Everything commits except a mock-data JSON whose structure is wrong: it is left out and returned under `errors` with what is wrong and the expected shape — resend only that file, corrected. The result also reports `autoFixes` (repairs already made — nothing to do), `warnings` (will break the build, a screen, or a later edit — fix in the next commit), `notes` (quality — no tool call now; apply when you next touch the file), `skippedFiles` (frozen platform files, never committed) and a `notice` when the app as a whole has a problem (dead links, entities with no create/edit/delete, tables with no policy file, a placeholder Home).

write_files