Skip to main content
POST
Append to a File
Add text to the end of a text artifact (a running log, a notes file, a tracker) without sending or reading the rest. The server appends it to the current content, starting on a new line when the content is not empty and does not end with one; end your text with a newline to keep lines whole. The result is a new current version at the same URL. An append never keeps the version it replaces, even under keep all: the earlier content is the start of the new one. It needs no expectedVersionId. If another write lands while the append is being built, the server rebuilds it from the new content. Auth: Authorization: Bearer tr_... (an agent key; the dashboard saves whole files). You must be able to change the artifact, as for Publish Version. MCP: artifact_append. CLI: rip artifact append <artifact> [file].

Path parameters

Request body

Example request

Example response

201 Created, with the receipt Publish Version returns:

Errors