Skip to content

A newcomer's first workflow, from the chat to verified results - #9

Open
mvsbm wants to merge 4 commits into
fix/debt-passfrom
feat/first-run
Open

mvsbm wants to merge 4 commits into
fix/debt-passfrom
feat/first-run

Conversation

@mvsbm

@mvsbm mvsbm commented Oct 21, 2026

Copy link
Copy Markdown
Owner

Stacked on #8 (which is stacked on #7): merge #7, then #8, then this.

Why

A simulated first-time user ("I have a spreadsheet of sales orders; I want total sales per region every month") got the right numbers, but only by knowing where to click: a Templates popup about nayose, a chat that read like a debug console, 60-line approval cards, a canvas built off-screen, no way to give the agent a file, a run that asked to re-approve everything, and a workflow never saved.

What a newcomer sees now

  • First visit: the Agent opens on an empty canvas with example requests (no Templates popup; templates stay in the Templates sidebar, renamed "Record matching …").
  • Chat: one line "Connected · model", details folded under it; status and tool rows in plain words.
  • Approvals: a short summary, the full contract/design one click away; an amendment leads with "Changed since you approved it"; an identical re-proposal asks nothing.
  • Files: attach in the chat (paperclip or drop), ComfyUI's own upload into a folder named after the workflow; the workflow's data input takes it.
  • Canvas: the whole workflow is framed after each build, beside the chat.
  • Contract: a title that names and saves the workflow natively; examples bring their own sample files, so they run before the user's data exists; a failed example names the node and its error; a table example matches as written ("North 1500, South 800").
  • App mode: inputs labelled in the contract's words; the Upload button follows its folder.
  • New nodes: Sort rows; Table from tool result (a code tool's table into the table nodes).

Bugs the real runs found

  • The Data folder refused folders it had not listed at page load (sample folders, new uploads).
  • The agent's copy of node definitions never refreshed in a chat.
  • An amended contract lost each output's step (a false gap in the Contract tab).
  • Read table dropped a header-only CSV's columns.

Verified

  • Unit (252), web, every browser test in both add-on modes; new first_run.cjs; requirement R40.
  • Real agents, isolated fixture: Pi + DeepSeek, 4 runs. The last one: 4 questions, contract, design, attach, one run, 3/3 steps verified, no gaps. Claude Code + Haiku, 2 runs: both reach the right totals; the second is fully green.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TBhEZ9Kdkj46ENKUQjk9FP

mvsbm and others added 4 commits October 21, 2026 20:35
A simulated first-time user (real agents: Pi with DeepSeek, Claude Code with Haiku)
now goes from "I have a spreadsheet" to verified totals without detours.

- First visit: no Templates popup; the Agent sidebar opens on an empty canvas
  with example requests. Templates renamed "Record matching ...".
- Chat: one connection line; status and tool rows in plain words; approval
  cards lead with a short summary (full text one click away), and an
  amendment with what changed since the user approved it; an identical
  re-proposal asks nothing.
- Files: attach in the chat (paperclip or drop) with ComfyUI's own upload,
  into a folder named after the workflow; the workflow's data input takes it.
- Canvas: the whole workflow is framed after each build, beside the chat.
- Contract: a title that names and saves the workflow natively on approval;
  examples bring their own sample files, run before the user's data exists;
  a failed example says which node failed and why; a table example matches as
  a person writes it ("North 1500, South 800").
- App mode: inputs labelled in the contract's words; the Upload button follows
  its folder.
- Fixes found by the real runs: the Data folder takes any existing folder
  (sample and newly uploaded ones); the agent's node definitions refresh;
  an amended contract keeps each output's step; Read table keeps a header-only
  CSV's columns.
- New nodes: Sort rows; Table from tool result (a code tool's table into the
  table nodes).

Verifies: R40 (new), with unit, web and browser tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TBhEZ9Kdkj46ENKUQjk9FP
Next month's export works whatever its name: the newcomer is no longer told to
keep the file named orders.csv. The agent leaves File empty for user data.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TBhEZ9Kdkj46ENKUQjk9FP
"North,1500; South,800" and "North 1500, South 800" now both match the same rows (whole
cells only), so the agent no longer amends a contract just to reformat an example.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TBhEZ9Kdkj46ENKUQjk9FP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant