Repository navigation
FLUJO workers: a later message reaches the model; release 0.7.1 - #23
Merged
Merged
Conversation
A model that handed off to the flow's finish step left the conversation there. FLUJO kept every later message but never showed it to the model, and still reported the turn as completed. The handoff could also end a turn with no written report. Worker flows now have no finish step, so a model ends its turn by writing its report and the conversation can take another message.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A FLUJO worker could silently ignore its next job. Ships as 0.7.1.
Fixes #22
What went wrong
FACTORY's worker flows had a finish step. When a model handed off to it, the conversation stayed there. FLUJO kept every later message, did not show it to the model, and still reported the turn as completed. So a second job looked successful although nothing was done. The handoff could also end a turn with no written report, which left an earlier progress note as the worker's last words.
It only showed on a real model: a scripted one never chose the handoff. A live company run found it, when the lead's closing turn ended in seconds with no output.
The fix
buildFactoryTeamSpecstakesfinishStep(defaulttrue, so templates used elsewhere are unchanged).FlujoSessionDriverbuilds its flows withfinishStep: false. A model can then only end its turn by writing its report, and the prompt says so.Checked on the real FLUJO 3.48.3, with a scripted model
finishStep: false: starts a child, the child ends on plain text, the lead gets the child's resultNot changed: a conversation already sitting on a finish step under 0.7.0 stays there. 0.7.0 shipped hours ago, and no known fleet runs on it.
Local CI (AGENTS.md)
Same steps as
.github/workflows/public-sdk.yml(focused list read from the workflow file), on a cleangit archiveexport of 5601cb8 with freshnpm ci. Linux ran in disposable containers.factory-selfhost profilesnode:22.17.0-bookworm-slim, Python 3.11node:24.22.2-bookworm-slim, Python 3.11Live: the real-model recheck runs with Seagulled's move onto FACTORY, against this release, and its result goes on flujo-app/seagulled#11.