Fix cn login to start CLI session after successful authentication #7953
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.
Description
This PR fixes the issue where
cn login
only performed authentication but didn't start the CLI session, requiring users to runcn
separately and authenticate again.Changes
login
command inextensions/cli/src/commands/login.ts
to automatically start the chat session after successful authenticationchat
function and call it after successful loginTesting
The change follows the existing pattern where the root command calls the
chat
function. After successful authentication, the CLI will now automatically transition to the interactive chat interface.Related
Fixes issue reported in Slack thread: https://app.slack.com/client/T058C7L9R26/C095VPZUYDP/thread/1758736641.672809
This agent session was created by tingwai and co-authored by Continue [email protected].
Summary by cubic
Automatically starts the Continue CLI chat session after cn login completes authentication. Users no longer need to run cn again or authenticate twice.