#warp forcibly adds itself to login items without opt out function
6 messages · Page 1 of 1 (latest)
Hi @tulip folio. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Based on the knowledge sources provided, there is indeed an issue reported where Warp automatically launches after a system restart, even when it's not set to "launch at startup" and doesn't appear in the Login items in System Settings. This behavior has been reported as a bug in the Warp GitHub repository.
The issue is described in GitHub Issue #5296, where a user reported that Warp automatically launches after restarting their MacBook, despite not being set to launch at startup. The user also mentioned that there was no way to turn this off since Warp doesn't appear in the Login items in System Settings.
It's important to note that this issue seems to be unintended behavior rather than a deliberate feature. The GitHub issue is still open, which suggests that the Warp team is aware of the problem but hasn't resolved it yet.
Unfortunately, the knowledge sources don't provide information about a specific opt-out function for this behavior or any official workaround. The issue appears to be affecting multiple users, as evidenced by comments on the GitHub issue.
If this behavior is causing problems for you, I recommend following the GitHub issue for updates or potentially adding your own comment to provide more context or express your concern about the intrusiveness of this behavior. You could also try reaching out to Warp's support team directly for assistance or to report your experience with this issue.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@tulip folio Kapa.ai is still learning and improving, please let me know how I did by reacting below.
remove it in system settings > close warp > open warp again > it adds itself back to my login items
ah yeah it looks like it was raised here, very recently too with some messages 19 hours ago. i only experienced this recently, not like the original poster on september 10 2024 https://github.com/warpdotdev/Warp/issues/5296