Idea
Right now every agent (including the first one) receives a freshly initialized workflow state where \payload\ is empty (\core/engine.py:749, defaults in \core/state.py). Only \meta\ (run_id, workflow_name, started_at) is pre-filled via _init_run_meta().
It would be useful to let the user seed the workflow state with their own information in \payload, so the first agent starts with context instead of an empty payload.
This is a rough idea / stub, not a concrete plan. No implementation has been started.
Scope sketch (unclear, needs discussion)
- Configurable initial payload, ideally in the workflow file.
- Should be settable from both the CLI and the GUI.
- Details (CLI flag syntax, GUI field, validation, merge vs. replace semantics) are still open.
Out of scope
Idea
Right now every agent (including the first one) receives a freshly initialized workflow state where \payload\ is empty (\core/engine.py:749, defaults in \core/state.py). Only \meta\ (run_id, workflow_name, started_at) is pre-filled via _init_run_meta().
It would be useful to let the user seed the workflow state with their own information in \payload, so the first agent starts with context instead of an empty payload.
This is a rough idea / stub, not a concrete plan. No implementation has been started.
Scope sketch (unclear, needs discussion)
Out of scope