Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension demands Greptile Pro to add my repo, which I have, but there is nowhere to sign in? #11

Open
JessicaMulein opened this issue Sep 7, 2024 · 10 comments

Comments

@JessicaMulein
Copy link

I have Greptile Pro but the extension is saying I need it to add my repo. There does not appear to be a settings or a place to log in.

@juryrigcoder
Copy link

Get similar experience, even though I am able to sign in with my Github account, but when I try to enter a repo I receive "Permission error: Please upgrade your membership to clone private repos or repos over 10 MB.". Btw, I am a Pro subscriber.

@rajitkhanna
Copy link
Member

Hi guys, we're spread a little too thin to accommodate this extension right now, but since it's open source you can create an API key at app.greptile.com/api and plug and play here.

@justinmilner1
Copy link

The GET /membership endpoint is returning 'free' given the github token linked with my pro account - seems to be an issue on the server side, not with the extension.

@rajitkhanna
Copy link
Member

rajitkhanna commented Sep 13, 2024

This extension was using the v1 of our api which is now deprecated. Docs for interacting with v2 can be found here: https://docs.greptile.com.

The flow would be to login to the Greptile platform, create an api key, and then open chats in the extension by calling the /repositories and /query endpoints with the api key.

@justinmilner1
Copy link

@rajitkhanna Ah I see - okay that could be fixed pretty easily... but before doing so I think it's relevant to ask if you would rather start from scratch? (or close to it)
Should the extension continue to offer chat? Should it prioritize chat? Or should it be more focused on managing greptile index entries/state? Or should it exist at all?
From my surface-level perspective of Greptile, it looks like you guys are heading more towards supplying the backend for codebase semantic search, and away from offering customer-facing UIs.

Side note: Looks like the cli was outdated as well - I drafted a new cli for interacting with the v2 endpoints here

@rajitkhanna
Copy link
Member

I would start from scratch and only offer chat - Cursor/Claude is faster when it comes to inline editing, but our codebase context is far and away the best.

It would be nice if the cli supported streamed responses.

@justinmilner1
Copy link

@rajitkhanna That's what I figured - I'll hold off on any changes to this repo.

Do you intend on competing with Cody, Continue, Copilot, etc in providing ui coding assistant extensions? That is a major project if so.
True cli with streamed responses would be nice but perhaps low priority as all large user groups as this stage expect many chat features beyond what the cli can easily offer.

My surface level perspective of greptile is that the company is moving towards a codebase context specialization, and this would mean that rather than being focused on supplying chat, the extensions/CLIs should focus on index configuration. Is this accurate or do you guys see yourself being more general?

@drwbns
Copy link

drwbns commented Sep 18, 2024

Hi guys, we're spread a little too thin to accommodate this extension right now, but since it's open source you can create an API key at app.greptile.com/api and plug and play here.

After creating an an API key, will using the extension not charge my credit card for any small repos < 10Mb ?

@rajitkhanna
Copy link
Member

Right now, every API request incurs a (15 cent for non-genius or 45 cent for genius mode) charge.

@rajitkhanna
Copy link
Member

@justinmilner1 that is correct. We build the best AI-powered codebase context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants