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.

Every save would work. You just ("just") need good caching. Cursor nails this. https://twitter.com/amanrsanger/status/1750023209733464559

Anyway to sign up for newsletter updated for when that happens? I’d be very keen to check this out once that feature lands.

We 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

> Haven’t figured out what should trigger updates.

What triggers updates when it is not local?

When a commit code is pushed to that remote branch

OK, then why would that be crazy for local when it is the trigger for non-local?

Just 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.

Thanks, some interesting challenges there.

Also looking for something local but I feel like Apple will probably eventually release local LLMs for your entire filesystem.

[not part of greptile]

I've given it a fairly serious shot and my conclusion is that building IDE hooks is seriously depressing. IntelliJ deprecates APIs constantly and the docs don't really keep up.

And then there's the total dumpster fire that is trying to support GPU acceleration on multiple platforms.

Unfortunately it's easily 10x the work to do this kind of thing local only.