You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
explore - apply - archive flow on new project broken
#1571
Moved from issue #831, originally opened by @stdweird on 2026-03-11. Continuing the conversation here in Discussions — the original issue thread (including any comments) stays available at #831 for the record.
i started a new project from scratch with the explore step, and after some back and forth a first change was created and apply'ed and archived. however, the context of that lead to the change is not kept/summarised so it can be reused for further steps/changes.
is this something that we are supposed to managed on our own? when making a new project, should we first create multiple cahnges during the explore phase and only then start applying them?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Note
Moved from issue #831, originally opened by @stdweird on 2026-03-11. Continuing the conversation here in Discussions — the original issue thread (including any comments) stays available at #831 for the record.
i started a new project from scratch with the explore step, and after some back and forth a first change was created and apply'ed and archived. however, the context of that lead to the change is not kept/summarised so it can be reused for further steps/changes.
is this something that we are supposed to managed on our own? when making a new project, should we first create multiple cahnges during the explore phase and only then start applying them?
All reactions