Skip to content

Conversation

continue[bot]
Copy link
Contributor

@continue continue bot commented Sep 24, 2025

Description

This PR fixes the issue where cn login only performed authentication but didn't start the CLI session, requiring users to run cn separately and authenticate again.

Changes

  • Modified the login command in extensions/cli/src/commands/login.ts to automatically start the chat session after successful authentication
  • Added import for the chat function and call it after successful login
  • Improved user experience by eliminating the need for double authentication

Testing

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.

  • Bug Fixes
    • login command now imports and calls chat() after successful WorkOS login.
    • Adds a "Starting Continue CLI..." message and transitions to interactive chat.
    • Failure behavior unchanged; exits with code 1 on error.

- Modified login command to start chat session after successful login
- Users no longer need to run 'cn' separately after login
- Improves user experience by eliminating the need to authenticate twice

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>
@continue continue bot requested a review from a team as a code owner September 24, 2025 20:10
@continue continue bot requested review from RomneyDa and removed request for a team September 24, 2025 20:10
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Sep 24, 2025
Copy link

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

  • feat: add changelog generation support
  • fix: resolve login redirect issue
  • docs: update README with new instructions
  • chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

  • 📝 Automatic changelog generation
  • 🚀 Automated semantic versioning
  • 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:XS This PR changes 0-9 lines, ignoring generated files.
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

1 participant