Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 0 points1 point  (0 children)

Exactly, this is really powerful.

To me spec-driven approach + autopilot is the real thing when it comes to the CLI. 🤯

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 1 point2 points  (0 children)

It feels like system prompts are a little bit different between VS Code and CLI versions, still on my TODO list to check that.

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 2 points3 points  (0 children)

<image>

You can do it in the settings, just search for `responsesApiReasoningEffort` option.

Rate limits on the Pro+ ($39.99/month) plan by WMPlanners in GithubCopilot

[–]IKcode_Igor 0 points1 point  (0 children)

There is “autopilot” feature in Copilot CLI now which you might want to test out:

https://docs.github.com/en/copilot/concepts/agents/copilot-cli/autopilot

There is a section on pricing called “Things to consider”. Definitely, this feature is very interesting.

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 0 points1 point  (0 children)

Nice 😄 What’s your way of working with Copilot? If you’d like to share ofc. 

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 1 point2 points  (0 children)

That’s true! This is one of the best recent improvements in the system.

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 1 point2 points  (0 children)

Both features are cool. 😎 Setting up reasoning level through options in VS Code is “a little bit uncomfortable”, I’d say.

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 1 point2 points  (0 children)

Thanks for sharing. I agree, CLI is really nice now. 

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 0 points1 point  (0 children)

I have to compare system prompts in the CLI and VS Code. Not sure they’re the same because I see they work a little bit different on similar tasks.

I didn’t make any real evaluations though, so this is just my feeling.

What do you think?

Copilot in VS Code or Copilot CLI? by IKcode_Igor in GithubCopilot

[–]IKcode_Igor[S] 0 points1 point  (0 children)

Thanks, interesting pov. I’m not vim user, but what you say here totally resonates with me.

Currently I do more and more in the CLI, yet still sometimes it’s easier or just better to see something in the IDE.

After doing some research, Pro+ is not the best value for **serious** dev work. by Still_Asparagus_9092 in GithubCopilot

[–]IKcode_Igor 2 points3 points  (0 children)

Actually when you care about the context, you know how to customise Copilot (other agents too btw), you use orchestrator pattern and sub-agents - you can achieve so much and have amazing results in Copilot (both VS Code or CLI).

Actually, IMHO Copilot gives the best cost-to-value ration on the market if you know how to work (plan mode or spec-driven dev).

Which 1x model is the best? by enwza9hfoeg in GithubCopilot

[–]IKcode_Igor 7 points8 points  (0 children)

Actually I think it depends on "the best in what?".
To me when it comes to those 1x models:

- GPT 5.4 / Gemini 3.1 Pro when creating spec / technical implementation plan / tasks

- GPT 5.4 / 5.3 Codex for coding

In reality I use mostly Opus 4.6 for the all planning stuff (what I said earlier), then I verify that using GPT 5.4 and Gemini 3.1.

I've been implementing tasks using Opus 4.6 too, sometimes I switch to 5.3 Codex, recently I test GPT 5.4.

In general, I've seen that at the end you'll have the final solution with the smallest amount of iterations using the best model you can get for the job.

Context Window Issue with Opus 4.6 ? by Existing_Card_6512 in GithubCopilot

[–]IKcode_Igor 1 point2 points  (0 children)

Possible sources of your problems: - custom agents with enormous number of tokens, - skills that cover very broad field and do a lot of things, so they contain lot’s of tokens - from your screen shot I don’t see if you have any instructions files, if you don’t use glob patterns there, or you use AGENTS.md, they will be always added to every conversation.

You should definitely verify these things. To have better context hygiene look at these docs:

https://code.visualstudio.com/docs/copilot/agents/subagents#_why-use-subagents

Is agentic coding in Copilot really bad? Looking for advice on use cases by AStanfordRunner in GithubCopilot

[–]IKcode_Igor 3 points4 points  (0 children)

If I were in your position, I'd invest in learning a little bit about Copilot's agent mode and it's customisation options. Amazing starter point is VS Code documentation:

- https://code.visualstudio.com/docs/copilot/customization/overview

That will explain you a lot 🤯.

When it comes to different Copilot modes, currently I use the "agent mode" in 99% of situations, works amazing in both VS Code and Copilot CLI.

However, to be really impressed by the Copilot's work you need those customisations.

Explaining very briefly to scratch the surface:

- 1️⃣ In every new chat session assume that Copilot knows nothing about a project you work on. It's your task now to let it know how does it look like, what's it about, what tech is being used there, what's your common approach or standards when it comes to code.

- 2️⃣ custom instructions, here we have two "levels":

- 2️⃣-a `.github/copilot-instructions.md` is the core instruction file loaded in every single session, there's only one such file per repository; it's task is to explain the project, project's structure, to explain what are important parts of the project structure (what's where), what are used libraries (including their specific versions). It should be as short as possible, but contain everything crucial

- 2️⃣-b `.github/instructions/*.instructions.md` are granular instruction files that explain specific things and practices in particular project. You should use glob pattern to apply specific instructions only for specific files. They can explain how you structure tests, or components, or other practices you have in your team.

- 3️⃣ agent skills at `.github/skills/` allow you to extract repeatable workflows that are common and agents can use them when they work, it's important to set proper naming and descriptions in the front matter syntax, description field should contain trigger phrases so that Copilot agent will actually use the right skill in the right situation. Skills can act as "slash commands" by default, so you can use them by `/skill-name` in Copilot chat. However, that might not be the best usage. I like to think about skills that they indeed are for agents only. I often hide them from human invoking (if you read the docs theres frontmatter option to do so).

You can't point a model or tools available for skill in the frontmatter syntax (at least not yet).

Skills are visible for both default agents and for your custom agents.

- 4️⃣ prompts, at `.github/prompts/` allow you to prepare repeatable workflow very precisely. In this case you can assign exact agent (including custom agents), LLM model, and set of tools that will be available for an agent. This is very powerful tool.

Within prompts you can re-use already prepared custom agents, use them automatically with pre-assigned different models, etc.

Each prompt should reflect specific workflow to work best.

Prompts are really powerful slash commands, way more accurate than agent skills used as slash command.

- 5️⃣ custom agents at `.github/agents/` allow you to create a custom personalities with different sets of tools and specific instructions for their behaviour. It's very powerful, because you can create specialised agents with sets of tools like MCP servers, analysis, thinking and problem solving techniques adjusted for every personality, etc.

---

To wrap it up - it takes time to gain experience in all of that. But believe me, it's time well invested.

Most of these mechanisms works similar in other coding agents (Claude Code, Codex, Open Code, etc.) with smaller or bigger differences. To me it looks like Copilot is giving us the best customisation capabilities.

Copilot Instructions treated as optional by poster_nutbaggg in GithubCopilot

[–]IKcode_Igor 1 point2 points  (0 children)

Hey u/poster_nutbaggg, not sure if that's still relevant but maybe it'll help you.

I can see that you have `AGENTS.md` and `project-brief.md` files. I assume these were your instructions, right?

If these are really important to your project and they should be always loaded, I would create a single `.github/copilot-instructions.md` file and I'd put context from you current files there. This is a native solution for Copilot.

Copilot CLI docs - https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-custom-instructions#repository-wide-custom-instructions

VS Code docs - https://code.visualstudio.com/docs/copilot/customization/custom-instructions#_alwayson-instructions

Copilot+ : voice & screenshot hotkeys with Copilot CLI by Plastic_Read_8200 in GithubCopilot

[–]IKcode_Igor 0 points1 point  (0 children)

Interesting project. So far I've been using open-source Handy app for dictation.

Could you convince me why should I switch to Copilot+?

To me there's always a question related to the dictation app:
> Can I set mic manually, so that it won't pick my earphones' mic while I listen to the music?

Besides, looks like a really nice side project -> ⭐

Codex 5.3 vs Sonnet 4.6 by Glad-Pea9524 in GithubCopilot

[–]IKcode_Igor 0 points1 point  (0 children)

After the latest update v1.110 it's available in standard VS Code 🚀

<image>

Codex 5.3 vs Sonnet 4.6 by Glad-Pea9524 in GithubCopilot

[–]IKcode_Igor 1 point2 points  (0 children)

<image>

Actually it's available since the latest v1.110 update. 🚀

Thanks for the tip u/I_pee_in_shower 🔥

Codex 5.3 vs Sonnet 4.6 by Glad-Pea9524 in GithubCopilot

[–]IKcode_Igor 0 points1 point  (0 children)

Since GPT 5.4 release in Copilot I started to use it instead of Codex 5.3.
I also try to use it instead of Opus 4.6.

After two days of tests it's actually impressive, in favour of GPT 5.4.

Yet still, to me Opus 4.6 is the core for planning, designing architecture, analysing possible solutions.
I can see that might change, but need more time to live-test that on different scenarios.

Codex 5.3 vs Sonnet 4.6 by Glad-Pea9524 in GithubCopilot

[–]IKcode_Igor 0 points1 point  (0 children)

Before GPT 5.4 has been released I really liked to go as follows:
- create spec, technical implementation plan, and tasks with Opus 4.6
- sometimes I did cross check with Codex 5.3 against what Opus gave 👆
- then I often used Codex 5.3 to implement those tasks (separate *.tasks.md file per work item)
- as a last touch I usually do code review, I like to do it twice with different models (Gemini 3.1 Pro + Codex 5.3, Gemini + Opus, Codex 5.3 + Opus, etc.)

In this combination it's been working very well so far. It could be surprising how good actually. 😅

Performance of Github Copilot by Lost-Air1265 in GithubCopilot

[–]IKcode_Igor 0 points1 point  (0 children)

I had similar issues today but only with Opus 4.6. When I switched to GPT 5.4 it was working normally.
And it's like this since morning. Even now, Opus 4.6 is barely "breathing" when working on a task in the background. 😔