edit_file
Destructive
Replace an exact string in a world VFS file.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| as | No | Your own name, when you are one of several agents sharing one connection to this engine (the sub-agents one agent session runs share its connection, so without it the engine sees all of them as one caller). Pass the same name on every call you make. The engine then treats you as a caller of your own: your roster name is this name, and your play session, the play-shadow writes and refusals that say who wrote what, engine.modeOwner, your shell session and your notices are yours alone. Lowercase letters, digits, '-' and '_'. Leave it out when you are the only agent on your connection. | |
| new | No | Alias for new_string | |
| old | No | Alias for old_string | |
| path | Yes | ||
| quiet | No | When true, write the result without firing write side effects (importer dispatch, assetType onChange, vfs.watch subscribers). | |
| durable | No | When true, the edited bytes go to canonical /source even while play is RUNNING, and the session stays in play. The affected modules and components hot-reload, so the edit is observed running in the same play session with nothing left to promote — the call for bytes whose destination is known before they are edited, where vfs.promotePlayShadow(path or {paths}) takes bytes already on the shadow with play still running. An edit that cannot become canonical source is an error naming why, instead of a success that landed on the shadow. | |
| new_string | No | ||
| old_string | No | ||
| replace_all | No |