Call page.edit_file

Change named files of a site from an instruction — 'redo the pricing section in Pricing.astro', 'rewrite this component', 'change the hero copy in src/components/Hero.astro', 'restructure that page's markup'. Goosy's coding agent makes the change in the site's files in place, starting from the files named in paths, and the result is one checkpoint (page.rollback undoes it) with the agent's own one-line summary — relay that, never more. It works on every site whose files we hold, however it was made or brought in; a site whose files are READ-ONLY here is refused, and so are dependency manifests, lockfiles, build configuration and generated files. Each call is a paid authoring run on the site's own plan, and it raises its approval card first, which is the member's confirmation. While a live workbench is showing the site the change appears there and no build runs (the result says build_deferred; relay its build_hint); otherwise a build follows. Not for a change of a few exact lines you already have — that is page.patch_file. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.