Skip to content

Add required per-turn output schemas - #1577

Draft
hunterassembly wants to merge 1 commit into
vercel:mainfrom
hunterassembly:codex/required-output-final-step
Draft

Add required per-turn output schemas#1577
hunterassembly wants to merge 1 commit into
vercel:mainfrom
hunterassembly:codex/required-output-final-step

Conversation

@hunterassembly

Copy link
Copy Markdown

Summary

  • propagate a per-turn required output-schema flag across the Eve client, channel, durable session, and workflow boundaries
  • force exactly one final-output step when a required structured turn would otherwise terminate as prose
  • expose the terminal step.failed event to channels so consumers can settle required-output failures truthfully

Proof

  • pnpm --filter eve test:unit — 565 files, 5,890 passed, 1 skipped
  • pnpm --filter eve typecheck
  • pnpm --filter eve build
  • autoreview: clean after one prior session-token-limit repair

This is the framework dependency for Remi REMI-1525.

@vercel

vercel Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@hunterassembly is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.


if (stepInput?.outputSchema !== undefined) {
return { ...session, outputSchema: stepInput.outputSchema };
return {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The continue path accepts outputSchemaRequired: true without an accompanying outputSchema but silently drops the flag, so required-final-output enforcement never triggers and no error is surfaced.

Fix on Vercel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant