uncaged/workflow
10
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: buildOutputFormatInstruction should explicitly forbid extra frontmatter fields #394

New Issue
Closed
opened 2026-05-22 10:39:30 +00:00 by xiaoju · 0 comments
xiaoju commented 2026-05-22 10:39:30 +00:00
Owner
Copy Link
Copy Source

Problem

Agents output extra frontmatter fields not defined in the role schema (next, confidence, artifacts, scope). The engine ignores them (only schema fields are extracted), but it wastes tokens and confuses the output.

Root Cause

buildOutputFormatInstruction says "Your meta output must satisfy these fields" but doesn't say "output ONLY these fields". Agents fall back to Hermes' default frontmatter habits.

Fix

Add explicit instruction: "Output ONLY the fields listed below. Do not add extra fields."

Discovered During

Dogfood of solve-issue workflow on #335 — planner outputs next, confidence, artifacts, scope alongside the schema-required status and plan.

— 小橘 🍊（NEKO Team）

## Problem Agents output extra frontmatter fields not defined in the role schema (`next`, `confidence`, `artifacts`, `scope`). The engine ignores them (only schema fields are extracted), but it wastes tokens and confuses the output. ## Root Cause `buildOutputFormatInstruction` says "Your meta output must satisfy these fields" but doesn't say "output ONLY these fields". Agents fall back to Hermes' default frontmatter habits. ## Fix Add explicit instruction: "Output ONLY the fields listed below. Do not add extra fields." ## Discovered During Dogfood of solve-issue workflow on #335 — planner outputs `next`, `confidence`, `artifacts`, `scope` alongside the schema-required `status` and `plan`. — 小橘 🍊（NEKO Team）
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aobing jiashuang (Jia Shuang) jiayi (Jiayi) luming scottwei tuanzi xiaoju xiaomo xiaonuo xingyue
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: uncaged/workflow#394
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?