From ed2bd6308bd835db2963499f4dec2757502793f1 Mon Sep 17 00:00:00 2001
From: Jarrod Sibbison <72240382+jsibbison-square@users.noreply.github.com>
Date: Mon, 29 Sep 2025 08:37:04 +1000
Subject: [PATCH] doc: file parameter recipe update (#4594)

---
 documentation/docs/guides/recipes/recipe-reference.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/documentation/docs/guides/recipes/recipe-reference.md b/documentation/docs/guides/recipes/recipe-reference.md
index 29e5a72d..67cd6ccb 100644
--- a/documentation/docs/guides/recipes/recipe-reference.md
+++ b/documentation/docs/guides/recipes/recipe-reference.md
@@ -125,9 +125,19 @@ The `required` and `optional` parameters work best for recipes opened in Goose D
 :::important
 - Optional parameters MUST have a default value specified
 - Required parameters cannot have default values
+- File parameters cannot have default values regardless of requirement type
 - Parameter keys must match any template variables used in instructions or prompt
 :::
 
+#### File Parameter Type
+
+When using `input_type: file`, the parameter value should be a file path. At recipe execution time, Goose will:
+
+1. **Read the file contents** from the provided path
+2. **Replace the parameter** with the actual file contents in the recipe template
+
+**Security Consideration**: File parameters **cannot have default values** to prevent unintended importing of sensitive files
+
 ## Extensions
 
 The `extensions` field allows you to specify which Model Context Protocol (MCP) servers and other extensions the recipe needs to function. Each extension in the array has the following structure: