Repository navigation
Make onboarding accept free-text instead of rigid categories - #49
Merged
Merged
Conversation
User role, personality, and use case fields now accept any input with hints shown as dim text. Only provider selection (openai/anthropic/etc) remains a strict choice since it drives config logic. Soul and agent markdown files now use the user's own words directly instead of mapping to predefined paragraphs. Unknown model names show a note but don't block setup. Fixes #48 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Fixes #48
Test plan
pytoclaw onboardand enter free-form descriptions for role/personality/use case🤖 Generated with Claude Code