That&#x27;s pretty much what we did! The fact that the `capistrano-harrow` code is a <i>dependency</i> rather than being embedded into Capistrano itself was supposed to benefit people by allowing us to experiment with tasteful integrations without having to repeatedly bump `capistrano` every time we wanted to try something out. Having the integration in a tiny gem also makes it easier to audit for anyone who wants to know what exactly we&#x27;re doing. It&#x27;s regrettable that this has drawn such negativity about the process when it was intended to be <i>better</i> this way. Lesson learned, I suppose.<p>Please excuse the stray line numbers, but here&#x27;s what the output looks like [1], the prompt respects the presence of a tty and defaults to no after a few seconds, and the prompt is only visible when running &quot;cap install&quot; (not &quot;gem install capistrano&quot;)<p>Almost certainly this dependency will go away soon, not because of the negative comments on HN, but because silly as it sounds, I don&#x27;t really like it anymore than anyone else does, I just need to apply a little pressure and see if the product we tried to build will find it&#x27;s place in the market or not.<p>[1]: <a href="https:&#x2F;&#x2F;gist.github.com&#x2F;leehambley&#x2F;7c18c9760e5ec81f5181c018fc90d72e" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;leehambley&#x2F;7c18c9760e5ec81f5181c018f...</a>