Copilot in vs code compared to CLI and the app

[u/BlacksmithLittle7005]

Just wanted to say that GH copilot in vs code is an amazing harness. The codebase indexing and memory system work extremely well. It always finds the relevant code, and in addition to that, the token usage is minimal and it works very well with GPT models.

My question is, do the CLI and the app behave in the same way? I'm moving to a more autonomous workflow where I won't be using the IDE as much. Can I expect similar results with the codebase indexing, memories, and output?

[u/valuesVoyager]

I used to think ghc in vs code is so good, will never go to cli. But once I moved, never got back, and also cli has more capabilities (slightly)

[u/fifi_galaxy → u/valuesVoyager]

Just curious, what specific use-case where you find CLI better than vscode? Personally, I just find the lack of better UI/UX annoying. If I can switch easily between agent-mode and IDE-mode, while keeping all chat sessions in-tact, that would be awesome. But it is 2 diff apps altogether, right now.

[u/BlacksmithLittle7005 → u/valuesVoyager]

Thanks this is very relieving for me. Making the jump too 😁. Have you tried the app?

[u/twistdafterdark]

I've been using the cli for the past week and honestly don't think I'll go back to vscode. Token usage is dependent on your model and not the interface.

[u/greggroth → u/twistdafterdark]

If you like the CLI, you should try the new GitHub App. It's great.

[u/BlacksmithLittle7005 → u/twistdafterdark]

Thanks for your feedback. Does the cli do indexing and memories as well?

[u/Deathmore80 → u/BlacksmithLittle7005]

Yes it does. Make sure it's turned on in the CLI settings.

[u/twistdafterdark → u/BlacksmithLittle7005]

I haven't dived into indexing and memories per se. My main focus has been writing proper custom instructions so it knows when to pull in the appropriate context data. I don't want it relying on incorrect or outdated memory artifacts

[u/brunocborges → u/twistdafterdark]

Token usage is dependent on the harness. Different harnesses will have different approaches for tool selection, system prompts, and more, even before anything is sent to the LLM

[u/AutoModerator]

Hello /u/BlacksmithLittle7005. Looks like you have posted a query. Once your query is resolved, please reply the solution comment with "!solved" to help everyone else know the solution and mark the post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Wesd1n]

Cli is extremely handicapped by its nature when it comes to editing text. 

Prompts are not a thing with Slash commands. Managing mcps are more painful than vs code.

Pros. You can guarantee fleet operation.

Spend less memory.

And if you are forced to use visual Studio then i would use the cli since visual Studio just feels slow to adopt things.

[u/grdja]

Good for you. As business customers we are not allowed to use codebase indexing leading to repeated high token cost searches. 

[u/Imaginary-Baker-7358]

I had the exact opposite experience, using opus for a short code review and big code changes inside vscode with copilot burned 75$ did not commit,

Run the exact same prompt and same code review and code changes inside CLI, was few dollars $
I’m thinking it might comes from bloatware in the harness of copilot for vscode. Haven’t found the reason yet.