[FEATURE] Dynamic Workflow Feature List

Resolved 💬 1 comment Opened May 31, 2026 by ByteOfCode-Jimmy Closed Jul 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [ ] This is a single feature request (not multiple features)

Problem Statement

I was working in the Workflow Dynamics and I love it. It's kind of like Agent SDK. I would like to add in new features, which I haven't been able to find.

Proposed Solution

  1. loadJSON(path, opts?) — Reads a JSON file from disk directly into the script. Replaces the clunky wrapper-workflow pattern. Supports optional schema validation. Results re-read on resume (not cached), so stale data is never a risk.
  1. humanInput(prompt, opts?) — Pauses the entire workflow and waits for a typed response. Supports a display field for showing content above the prompt, a timeout with defaultValue, and multi-line input. User types /finish or /complete_workflow to signal they're done — returns the sentinel '__DONE__' so you can branch cleanly.
  1. exec(command, opts?) — Runs a shell command and returns { stdout, stderr, exitCode, ok }. Supports cwd, env, timeout, stdin input, and throwOnError. Lets you run Python/Node scripts, formatters, test suites, or any CLI tool and feed the output directly back into the workflow.
  1. createAgent(systemPrompt, opts?) — Returns a callable handle that maintains conversation history across multiple calls. Each await bot('...') continues the same thread. The handle exposes .history(), .inject(), .reset(), and .turns. Multiple handles are independent and can run in parallel(). Cached by label for resume.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Developer tools/SDK

Use Case Example

additional_features.md

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗