Skip to content

Conversation

@kkashilk
Copy link
Contributor

@kkashilk kkashilk commented Nov 3, 2025

…terminal

Issue #, if available:

  1. App launching takes the focus away from the terminal.
  2. Running the install.sh script twice causes the desktop app to show-up instead of it running in the background.

Description of changes:

fix an issue where starting app in bg causes focus to move away from …

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@kkashilk kkashilk requested a review from a team as a code owner November 3, 2025 23:32

"$macos_bin/$DESKTOP_BINARY_NAME" --no-dashboard > /dev/null 2>&1 &
open -g -a "$MACOS_APP_DIR/$app_name" --args --no-dashboard
sleep 3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to sleep?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rn, we immediately print that installation was successful and finish up the installation. If the user tries to start kiro-cli right after that, it may lead to a situation where the command doesn't immediately succeed, because we don't have the symlinks in place

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than fixed sleep, shall we check for completion of expected work? We can add timeouts and when we are unable to verify completion, then we can have call for action to users to open the desktop App (worst case scenario)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants