xiaoju
b5e094ab4d
Adds `uwf step ask <step-hash> -p <prompt>` for asking follow-up questions to a completed step's agent without mutating thread state. - Fork-by-default: creates and caches a fork session per step (cache key `<stepHash>:ask`); subsequent asks reuse it. - `--no-fork` fallback: spawns a fresh session with the step's detail ref injected as context. - `--agent` overrides the recorded agent; otherwise resolves from the step's agent field via config alias. - Updates `packages/cli/README.md` and `packages/util/src/usage-reference.ts` so the new subcommand is discoverable via README and `uwf prompt usage`. Fixes #146
963 B
@united-workforce/cli, @united-workforce/util
| @united-workforce/cli | @united-workforce/util |
|---|---|
| minor | patch |
feat(cli): add uwf step ask <step-hash> -p <prompt> read-only follow-up command
Phase 2b of the ask-session work. Adds a new subcommand that lets the user ask
a follow-up question to a historical step's agent without writing a new
StepNode or mutating thread state. The command resolves the agent from the
recorded step (or --agent <cmd> override), forks the original session via the
adapter's --mode fork --session <source> contract, caches the resulting
ask-session id under <stepHash>:ask so subsequent asks reuse it, then invokes
the agent with --mode ask --session <forkId> --prompt <text> --detail <ref>
and streams the raw stdout to the caller. --no-fork falls back to a fresh
session that receives the step's detail ref for context. The prompt usage
reference (in @united-workforce/util) is also updated so agents discover the
new subcommand. Resolves issue #146.