Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How to I prevent SourceTree from killing Pageant?

SourceTree apparently recently added the "Automatically start SSH agent" option but even if I turn this off, it still KILLS the agent when SourceTree closes, which is quite stupid -- killing it even if you DID start seems silly, but killing it when you DIDN'T start it is surely just broken code.

Is it possible to fix this bad/broken behaviour?


2 answers

SourceTree apparently goes by process name; I made a copy of pageant.exe called my-pageant.exe and launched it, and it stays running even after I close SourceTree.

Hopefully Atlassian will fix this behavior soon; for SourceTree to forcibly terminate processes that it doesn't start is very unwelcome.

Thanks for this observation - a useful work-around until Athlassian sort out their very anti-social behaviour!    I think it's poor behaviour even if SourceTree launched Pageant, but indefensible behaviour when it /didn't/ launch it.

Like Steffen Opel _Utoolity_ likes this

I renamed the file `` pageant.exe '' but I still have the problem.

I think I will downgrade because it is unbearable.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events