4 ms·
We’ve been grappling with making it local but two considerations 1. Haven’t figured out what should trigger updates. Every commit sounds crazy, every save woul
by dakshgupta 3y ago
We’ve been grappling with making it local but two considerations
1. Haven’t figured out what should trigger updates. Every commit sounds crazy, every save would be perfect but too intensive also.
2. LLMs will not be self hosted. We haven’t been able to get the same results with any smaller LLMs
To answer your questions we definitely want to make this available for local repos and ideally self hosted, on a technical level that’s probably several month away.
- adamtaylor_13 3y agoAnyway to sign up for newsletter updated for when that happens? I’d be very keen to check this out once that feature lands.
- dakshgupta 3y agoWe don’t have a newsletter but there should be a link to join our discord on app.greptile.com You can also email me at daksh [at] greptile.com and I’ll set a reminder to let you know when it’s out
- drcongo 3y agoThanks, some interesting challenges there.
- codingdave 3y ago> Haven’t figured out what should trigger updates. What triggers updates when it is not local?
- dakshgupta 3y agoWhen a commit code is pushed to that remote branch
- codingdave 3y agoOK, then why would that be crazy for local when it is the trigger for non-local?
- dakshgupta 3y agoJust because people commit locally more often than they push. That said, I think you're right and we might be overestimating the lift there. Will look into it more.
- jbellis 3y agoEvery save would work. You just ("just") need good caching. Cursor nails this. https://twitter.com/amanrsanger/status/1750023209733464559 https://twitter.com/amanrsanger/status/1750023209733464559