Should you harness the harness: what a workflow engine actually is

Description and use

<p><a href="https://fullgc.github.io/should-you-harness-the-harness-part-1/" rel="noopener noreferrer">Part one</a> described a procedure that lives inside the agent session, and the limits that follow from it living there. This part is about the alternative, and about how little of what is sold as the alternative actually is one.</p> <p>A <strong>workflow engine</strong> is a program that holds the procedure and calls the coding agent when it needs intelligence. That is the whole definition. Everything separating an engine from a skill follows from it, including the two things it will cost yo

Problem

<p><a href="https://fullgc.github.io/should-you-harness-the-harness-part-1/" rel="noopener noreferrer">Part one</a> described a procedure that lives inside the agent session, and the limits that follow from it living there. This part is about the alternative, and about how little of what is sold as the alternative actually is one.</p> <p>A <strong>workflow engine</strong> is a program that holds the procedure and calls the coding agent when it needs intelligence. That is the whole definition. Everything separating an engine from a skill follows from it, including the two things it will cost yo

Outcome

<p><a href="https://fullgc.github.io/should-you-harness-the-harness-part-1/" rel="noopener noreferrer">Part one</a> described a procedure that lives inside the agent session, and the limits that follow from it living there. This part is about the alternative, and about how little of what is sold as the alternative actually is one.</p> <p>A <strong>workflow engine</strong> is a program that holds the procedure and calls the coding agent when it needs intelligence. That is the whole definition. Everything separating an engine from a skill follows from it, including the two things it will cost yo

Evidence

Should you harness the harness: what a workflow engine actually is

Source