You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .archon/workflows/defaults/archon-workflow-builder.yaml
-5Lines changed: 0 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -189,7 +189,6 @@ nodes:
189
189
10. Use `allowed_tools: []` on classification/analysis nodes that don't need tools
190
190
11. Use `denied_tools: [Edit, Bash]` when a node should only use Write (not edit existing files)
191
191
12. Prefer `model: haiku` for simple classification tasks to save cost
192
-
13. **CRITICAL**: Every generated workflow that accepts user input MUST reference `$ARGUMENTS` (or `$USER_MESSAGE`) in at least one node prompt. For single-node workflows, include it directly in the prompt (e.g., `$ARGUMENTS` on its own line under a `## Input` or `## Request` heading). Without this, the user's invocation message is captured by the harness but never injected into the node's conversation — the agent sees an empty input.
193
192
194
193
## Output
195
194
@@ -224,10 +223,6 @@ nodes:
224
223
exit 1
225
224
fi
226
225
227
-
if ! grep -q '\$ARGUMENTS\|\$USER_MESSAGE' "$FILE"; then
228
-
echo "WARNING: workflow does not reference \$ARGUMENTS or \$USER_MESSAGE — user input will not be injected into node prompts"
0 commit comments