Brvvo IDE

Use this when the person wants an edit to an existing Brvvo project, for example 'change the headline' or 'add a contact form'. Queues one change instruction for the named project; it runs in the Brvvo app on their computer and edits that project's files, which can overwrite earlier content (earlier versions can be restored in the Brvvo app). Confirm the change with the person first and set userConfirmed to true only after they agree. It does not publish. Retrying with the same idempotencyKey does not apply the change twice. Use list_projects first if you do not know the exact project name.

make_change

Use this when the person asks how a build, change or publish is going. Returns its state (waiting, queued, in progress, done, failed), progress and, once finished, the preview link. Without buildRef it reports the most recent request in the account, or the most recent one for projectName. Read-only. If Brvvo is not open on the person's computer the answer says it is waiting for Brvvo to be open on your computer; tell the person to open Brvvo and check again later.

get_build_status

Use this when the person wants a link to look at one of their projects in a browser. Returns the latest preview link for the named project. Read-only. The preview is served from the person's computer while Brvvo is open, so a link may not load when Brvvo is closed. A preview is not a public launch; use it to review, not to share widely.

get_preview_link

Use this when the person asks what they have built with Brvvo, or when you need the exact project name for another request. Lists up to 25 projects in the linked Brvvo account (name, preview link, published address when there is one). Read-only and limited to the person's own account; it never shows anyone else's projects. The list is as of the last time Brvvo was open on their computer.

list_projects

Use this when someone describes a website or app idea and wants a structured brief (site type, pages and sections, features, open questions) before anything is built. It only organises the idea you give it: it needs no Brvvo account, reads no projects and creates nothing. Returns a brief to show the person and adjust with them. Do not use it to build, change or publish a site.

plan_site

Use this only when the person explicitly asks to put a finished project online at a public web address. Queues a publish for one named project; it runs in the Brvvo app on their computer. Once published, anyone on the internet can open the address, and publishing can replace what was published before, so first ask the person to confirm in this conversation and set confirmPublish to true only after they clearly say yes. With confirmPublish false nothing happens and the tool only describes what would be published. Retrying with the same idempotencyKey does not publish twice.

publish_site

Use this when the person has agreed to a website or app brief and wants Brvvo to build it. It queues one build in the person's own Brvvo account. The build runs in the Brvvo app on their computer, so it starts only while Brvvo is open there; until then the status says it is waiting. Confirm the brief with the person first and set userConfirmed to true only after they agree; with false nothing is queued. Retrying with the same idempotencyKey (or sending an identical request within 10 minutes) returns that same build, so no second build is started. Does not publish anything. At most 5 requests can be in progress per account.

start_build