Function WriteFileSchema

internal/tools/write.go:39–61

WriteFileSchema is the OpenAI tool definition for write_file. The description steers the model away from bash heredocs (shell-quoting failure mode) for small-to-medium writes, and toward heredoc appends for large files (streamed tool-call args truncate server-side), mirroring the system prompt's rul

()

			return fmt.Sprintf("(write error: %v)", err)
		}
		return fmt.Sprintf("appended %d bytes to %s", len(content), path)
	}
	if err := os.WriteFile(path, []byte(content), 0o644); err != nil {
		return fmt.Sprintf("(write error: %v)", err)
	}
	return fmt.Sprintf("wrote %d bytes to %s", len(content), path)
}

// WriteFileSchema is the OpenAI tool definition for write_file. The description
// steers the model away from bash heredocs (shell-quoting failure mode) and
// names append as the recovery for a body too large for one streamed call,
// so the truncation dead end is a one-line fix instead of a tool switch.
func WriteFileSchema() map[string]any {
	return map[string]any{
		"type": "function",
		"function": map[string]any{
			"name":        WriteFileName,
			"description": "Write content bytes to a file at path. Creates parent directories. Overwrites unless append is true. Use this instead of bash heredocs for multi line content or content with quotes, dollar signs, or backticks - no shell quoting issues. For an existing file prefer edit_file: a full rewrite risks a one-character regression. A very large body can be cut off mid-stream by the server; if that happens, send it in parts of at most ~200 lines - first part plain, each later part with append true.",
			"parameters": map[string]any{
				"type": "object",
				"properties": map[string]any{
					"path": map[string]any{
						"type":        "string",
						"description": "Absolute or relative file path. Relative paths resolve against the working directory.",
					},
					"content": map[string]any{