Fix installer UX: Move all file modifications before commit #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reorganized the installer flow to prevent uncommitted changes after the initial commit. Previously, role configuration and demo task creation happened after the commit, leaving the user with immediate uncommitted changes. This was confusing UX. New flow: 1. Initial setup (Steps 1-4) 2. Role configuration (Step 5) - modifies config.yaml 3. Demo task creation (Step 6) - modifies workflow-state.json 4. Commit everything together (Step 7) 5. Launch agent (Step 8) - clean working directory This ensures users have a clean git state when starting their first agent, eliminating the confusing "uncommitted changes" prompt. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Owner
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Problem
After running the installer and committing the initial setup, users were immediately faced with uncommitted changes when trying to start an agent:
The uncommitted changes were from the installer itself:
.conductor/config.yaml.conductor/workflow-state.jsonSolution
Reorganized the installer steps from:
To:
This ensures all file modifications happen before the commit, resulting in a clean working directory when the user starts their first agent.
Test plan
🤖 Generated with Claude Code