feat(workflows): implement interactive workflow run with approval loops, quiet connection, and automatic file uploading by yxvnyk · Pull Request #547 · codemie-ai/codemie-code

yxvnyk · 2026-09-09T07:15:39Z

Ticket

Summary

This MR extended CodeMie CLI to support executing custom or shared workflows by ID or Name under the codemie workflow run and codemie sdk workflows run commands.

Changes

Impact

Both commands are feature-complete and support:

Interactive Interruption & Approval Handler:
- Detects Interrupted status from any node (e.g. approval states) and presents an interactive CLI choice to the user: Approve & Continue, Edit current message, or Abort workflow.
- Supports looping over successive interruptions seamlessly.
- Leverages a stable, engine-level execution ID (execId) across resumes to prevent state loss after a generic success base response.
Quiet Authentication Connection:
- Suppresses the standard ✔ Connected to CodeMie and configuration-loading spinner when raw JSON output is requested (such as during --no-wait or --json execution), making the CLI commands fully pipeline-safe and compliant with Unix stdout standards.
Clean Immediate Exit (--no-wait):
- Correctly handles commander options negation. Triggering a run with --no-wait outputs ONLY clean, raw JSON starting metadata and exits instantly.
Unix Pipeline-safe Completed Outputs:
- Successful executions display ONLY the actual finalized markdown/text output (fetched from the graph's finalizer state), omitting extra metadata or checkmark wrappers.
Automatic File Upload Assignment:
- Re-adds the -f, --file <name> option. Specifying a local file automatically reads and uploads it to the CodeMie files API before launching the workflow with its remote file_url reference attached.

Verification & Testing Evidence

Integration Tests
Executed and passed 100% of the workflow test suite:

npx vitest run tests/integration/cli-commands/workflow.test.ts

   1  RUN  v4.1.5 C:/epam/codemie-dev/codemie-code
   2
   3  Test Files  1 passed (1)
   4       Tests  6 passed (6)
   5    Duration  5.28s

Manual Verification Scenarios

A. Standard Output Extraction (Successful Polled Run)

`node ./bin/codemie.js workflow run d362c364-ee7f-4716-a1b7-f6f706d09f0d --input "hello"`

Output: Displays only the markdown result from the graph finalizer:

   1 ✔ Connected to CodeMie
   2 ✓ Workflow completed successfully.
   3
   4 # Conversation Summary
   5
   6 ## Initial User Task
   7 The user greeted with "hello"...

B. Clean JSON Trigger (--no-wait Suppressing Spinner)

1 node ./bin/codemie.js workflow run d362c364-ee7f-4716-a1b7-f6f706d09f0d --input "hello" --no-wait

Output: Returns confirmation about starting the workflow:

✓ ✓ Workflow execution started successfully. (Status: In Progress)

C. File Assignment & Interactive Approval loop

node ./bin/codemie.js workflow run d362c364-ee7f-4716-a1b7-f6f706d09f0d --input "hello my friend" --file "package.json"

Output: Quietly uploads package.json, enters interrupted state, prompts user to Approve/Edit/Abort, accepts edited input, and resumes polling seamlessly:

    1 ✔ Connected to CodeMie
    2 ✔ ✓ File package.json uploaded successfully.
    3
    4 ⚠ Workflow execution is Interrupted and requires your decision.
    5 Interrupted Message:
    6 hello* my* friend* -*
    7
    8 ? How would you like to proceed? Edit current message
    9 ? Enter your edited message: hello* my* friend*
   10 ✔ ✓ Workflow resumed with edited message.
   11 # Conversation Summary
   12 ... (prints only final result)

…tion, and automatic file uploading

yanaSelin · 2026-09-21T10:57:02Z

+        handleSdkError(error, "run workflow");
+      }
+    });
+


Duplicate run command logic across src/cli/commands/sdk/workflows.ts and src/cli/commands/workflow.ts

The run command handler (id/name resolution, file upload, execution polling, the Interrupted approve/edit/abort flow, and result output) is duplicated almost verbatim between sdk/workflows.ts (cmd.command("run <id>")) and workflow.ts (workflow.command('run [workflow-id-or-name]')) — ~230 lines each, differing only in quote style and local variable names.

Could we extract the shared orchestration logic (everything past argument resolution — polling, interrupt handling, output formatting) into a single helper, and keep both command files as thin wrappers that only bind/resolve CLI arguments (id-or-name, --input, --file, --wait, --json) and delegate to it?

Note: this shared logic shouldn't move into services/workflows.ts — that layer is a clean SDK-only wrapper today (no chalk/ora/inquirer/console.log). The polling/prompt/output code is CLI-presentation logic, so it belongs in a separate CLI-level helper (e.g. sdk/actions/run-workflow.ts) that calls the existing runWorkflow service function, rather than being folded into the service itself.

The sdk workflows run logic is deprecated. I will remove it

Ok, but lets clean up logic here as well. I added some comments, but in general: we need to leave here only thin orchestration and ui logic (spinners, user interactions, logs)

yanaSelin · 2026-09-22T07:05:18Z

+
+      try {
+        let targetId = id;
+        if (!id.startsWith("wfl_")) {


Could you please elaborate what this constant actually mean?

yanaSelin · 2026-09-22T07:11:04Z

+          if (match) {
+            targetId = match.id;
+          } else if (workflows.length === 1) {
+            targetId = workflows[0].id;


Lets separate parameters - id and name
For id we can use getWorkflow service, for name - create separate helper service to find exact match and throw error if there is no exact match.

yanaSelin · 2026-09-22T07:11:19Z

+          } catch {
+            // Keep as string
+          }
+        }


Move to separate helper

yanaSelin · 2026-09-22T07:13:03Z

+                mimeType: "application/octet-stream",
+              });
+              uploadedFileName = uploadRes.file_url;
+              uploadSpinner.succeed(chalk.green(`✓ File ${path.basename(opts.file)} uploaded successfully.`));


Move to separate service

yanaSelin · 2026-09-22T07:14:23Z

+              const resumeSpinner = ora("Resuming workflow with edited message...").start();
+              try {
+                await (client.workflows as any).api.put(
+                  `/v1/workflows/${targetId}/executions/${execId}/resume`,


add this method to sdk

yanaSelin · 2026-09-22T07:16:11Z

+        handleSdkError(error, "run workflow");
+      }
+    });
+


Ok, but lets clean up logic here as well. I added some comments, but in general: we need to leave here only thin orchestration and ui logic (spinners, user interactions, logs)

Andrii Yavnyk added 3 commits September 8, 2026 23:53

epmcdme-12353-run-shared-custom-workflows: add planning artifacts

255f579

feat(workflows): support interactive workflow execution, quiet connec…

b70df45

…tion, and automatic file uploading

fix(workflows): small fixes

17e993d

yanaSelin requested changes Sep 21, 2026

View reviewed changes

yanaSelin requested changes Sep 22, 2026

View reviewed changes

Navigation Menu

feat(workflows): implement interactive workflow run with approval loops, quiet connection, and automatic file uploading - #547

feat(workflows): implement interactive workflow run with approval loops, quiet connection, and automatic file uploading#547
yxvnyk wants to merge 3 commits into
codemie-ai:mainfrom
yxvnyk:feature/EPMCDME-12353_run-workflows-cli

yxvnyk commented Sep 9, 2026

Uh oh!

yanaSelin Sep 21, 2026

Uh oh!

yxvnyk Sep 21, 2026 •

edited

Loading

Uh oh!

yanaSelin Sep 22, 2026

Uh oh!

yanaSelin Sep 22, 2026

Uh oh!

yanaSelin Sep 22, 2026

Uh oh!

yanaSelin Sep 22, 2026

Uh oh!

yanaSelin Sep 22, 2026

Uh oh!

yanaSelin Sep 22, 2026

Uh oh!

yanaSelin Sep 22, 2026

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

yxvnyk commented Sep 9, 2026

Ticket

Summary

Changes

Impact

Verification & Testing Evidence

Uh oh!

Choose a reason for hiding this comment

Uh oh!

yxvnyk Sep 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

yxvnyk Sep 21, 2026 •

edited

Loading