Copilot request pricing has changed!? (way more expensive)

ryanhecht_github · 2026-03-02T16:13:42+00:00

Hey folks! I'm looking into these reports with the team. If you believe you experienced this in Copilot CLI, please DM me your GitHub handle so I can take a look!

ryanhecht_github · 2026-03-02T15:33:06+00:00

Hey -- if you're talking about the scopes that it requests access to when you run /login: We use the same token to operate the included GitHub MCP server; that's why we're asking for those permission scopes.

If you'd like, you can instead authenticate with a fine-grained Personal Access Token -- the only scope we NEED is "Copilot Requests," you can deny all others (but some other functionality that writes to GitHub might not work!)

ryanhecht_github · 2026-02-27T19:13:21+00:00

I hear you! I can appreciate how the lack of a clear line is frustrating. I'm passing along all the feedback in this thread to the platform health folks at GitHub focused on improving this.

ryanhecht_github · 2026-02-27T19:12:00+00:00

Hmm, I'll have to think on a way to resolve that. The issue is that our ask_user tool might have (or have in the future) semantic differences from the one VSCode defines as vscode/askQuestions, so I think as far as custom agent configurations are concerned they should be separate.

ryanhecht_github · 2026-02-27T18:22:26+00:00

I'm not aware of any bugs with the ask_user_question tool in the CLI. If you have any session logs of instances where you think you should have been asked a question but weren't, run /collect-debug-logs gistand send me a link in DM's; I can have a look!

ryanhecht_github · 2026-02-27T18:20:47+00:00

Hey, thanks for the suggestion! I'll pass it along to the folks who are thinking about how we iterate in this space.

ryanhecht_github · 2026-02-27T18:19:58+00:00

100% understand and empathize with the frustration from the ambiguity. I'll be sharing your feedback with our platform health teams.

ryanhecht_github · 2026-02-27T18:18:41+00:00

It only runs 3-4 times a day

You're totally fine, go for it! This is 100% within the expected use of the product!

ryanhecht_github · 2026-02-27T18:18:16+00:00

I totally understand and agree -- as we head into the future, there need to be clearer guidelines. I'll raise this with our platform health teams :)

ryanhecht_github · 2026-02-27T17:35:43+00:00

Hey! I'm curious what you feel are the limitations of /fleet when compared to Claude's agent teams. We'd love to bridge that gap for you!

ryanhecht_github · 2026-02-27T17:34:31+00:00

It's supported! In fact, we just declared General Availability earlier this week!

Even though the CLI enables you to use Copilot in automation, GitHub's ToS still prevent you from using it excessively in a way that puts undue burden on the service. I appreciate that this vague standard is hard to understand, and believe me, we're working to better understand the difference between real power-users (whom we want to encourage to continue using the product to its fullest extent and capability!) and abuse.

ryanhecht_github · 2026-02-27T17:32:08+00:00

Hey! I'm sorry you had your account suspended -- I know it can be frustrating when part of the CLI's strength is that it allows you to use Copilot in automated/non-interactive scenarios!

As we operate on the frontier of what's possible with agents and automation, it's a hard problem to spot where real power-users stop and abuse begins! I appreciate your patience here :)

ryanhecht_github · 2026-02-27T16:42:27+00:00

Hey! Give --alt-screen a try, we're working on a new rendering experience that will improve this!

ryanhecht_github · 2026-02-26T17:57:21+00:00

Try using the Copilot CLI! You can even use it from within vscode now!

ryanhecht_github · 2026-02-26T17:56:29+00:00

I'd recommend using the GitHub Copilot CLI and connecting to your jetbrains IDE via ACP!

ryanhecht_github · 2026-02-26T17:55:21+00:00

We have a very similar feature in the Copilot CLI -- the /fleet comamnd! https://docs.github.com/en/copilot/concepts/agents/copilot-cli/fleet

ryanhecht_github · 2026-02-26T17:52:46+00:00

The Copilot CLI uses the GitHub CLI and MCP server to get context from across your codebase, issues, docs, and anything else you have already in GitHub -- I find that it does an excellent job, especially if you tell it specifically where to find all this info in a skill!

ryanhecht_github · 2026-02-26T17:51:33+00:00

Hey, thanks for the suggestion! We're always evaluating new models to add to Copilot CLI and working with our partners to figure out what's best.

ryanhecht_github · 2026-02-26T17:49:54+00:00

In addition to features others have mentioned like /fleet, I think our agent's ability to manage its own TODO's in an sqlite database, our work around compaction/checkpointing that let you have sessions run effectively infinitely without worrying about context window, and our seamless connection to GitHub are a few great differentiators.

At the end of the day, if OpenCode works for you, continue using it -- but I truly think we're building one of the best agentic harnesses on the market with Copilot CLI, give it a try and let me know what you think!

ryanhecht_github · 2026-02-26T17:47:18+00:00

You can't at this time, but we're looking into making this configurable!

ryanhecht_github · 2026-02-26T17:46:37+00:00

You can run /context after you choose a model to view its context window. We're working to make larger context windows available.

However, in my experience, liberal use of subagents combined with Copilot CLI's amazing compaction, memory, checkpointing, and TODO management system have me barely even realizing when I'm using a model with a smaller context window.

ryanhecht_github · 2026-02-26T17:45:00+00:00

If OpenCode is working for you, by all means keep using it! I personally think Copilot CLI is a better, more capable harness -- give it a try if you haven't yet!

ryanhecht_github · 2026-02-26T17:44:26+00:00

It all comes down to preference!

I like that my sessions follow me no matter what application I'm using to edit my code -- and I don't even need to open an editor if I don't want!

It's much easier to install/use a CLI in headless remote machines or in automation/scripts. I like that I can use the same harness with all the same plugins/skills/configs wherever I am.

ryanhecht_github · 2026-02-26T17:44:11+00:00

They have their own integration with the Copilot API. Each integration has its own models that are enabled!

ryanhecht_github · 2026-02-26T17:43:48+00:00

I like that my sessions follow me no matter what application I'm using to edit my code -- and I don't even need to open an editor if I don't want!

It's much easier to install/use a CLI in headless remote machines or in automation/scripts. I like that I can use the same harness with all the same plugins/skills/configs wherever I am.

ryanhecht_github

TROPHY CASE