Skip to content

Iterate on a result - #32

Merged
shirkattack merged 1 commit into
mainfrom
feat/iterate-from-result
Sep 3, 2026
Merged

shirkattack merged 1 commit into
mainfrom
feat/iterate-from-result

Conversation

@shirkattack

Copy link
Copy Markdown
Owner

Summary

Item 4. Every optimization started from whatever was typed in the prompt box; chaining runs meant copying the result back by hand.

  • Iterate on this (next to Share on the Optimized Prompt card) makes the result the starting prompt, clears the previous result, keeps the method and dataset selections, and focuses the prompt box.
  • A banner under the prompt says which session it is iterating on, with an x to drop that link.
  • The follow-up session is named "Iteration of ", so lineage is visible in the sidebar and analytics.

Verification

  • tsc 0 errors
  • Headless browser on private ports with a scratch database: reopened a completed session, clicked Iterate, prompt box held the optimized text with the banner shown, ran again, new session named "Iteration of Seed run", banner cleared on completion, no page errors

@shirkattack
shirkattack force-pushed the feat/iterate-from-result branch 4 times, most recently from 8f40e29 to 5c64688 Compare September 3, 2026 20:00
"Iterate on this" on the Optimized Prompt card makes the result the
starting prompt for another run, keeping the method and dataset, with
a banner naming the source session; the follow-up session is named
"Iteration of <source>". Chaining runs, for example GEPA after a
meta-prompt rewrite, no longer needs copy and paste.
@shirkattack
shirkattack force-pushed the feat/iterate-from-result branch from 5c64688 to 246bff5 Compare September 3, 2026 20:00
@shirkattack
shirkattack merged commit 0809160 into main Sep 3, 2026
2 checks passed
@shirkattack
shirkattack deleted the feat/iterate-from-result branch September 3, 2026 21:16
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