Re:GitHub Copilot is moving to usage-based billing
by sz4kerto on Monday April 27, 2026 @03:57PM
(#47926529)
We need sandboxing for any agent, so we run it within Docker - so we use CLI.
Re:GitHub Copilot is moving to usage-based billing
by 0xffff2 on Monday April 27, 2026 @04:38PM
(#47927007)
I use vscode with containers extensively. Not sure why containers imply CLI.
Re:GitHub Copilot is moving to usage-based billing
by nqzero on Monday April 27, 2026 @10:40PM
(#47929940)
do you run vscode in the container ? if so, can you share your config ?
i've been trying to do this with systemd-nspawn
Re:GitHub Copilot is moving to usage-based billing
by chris_money202 on Tuesday April 28, 2026 @06:15AM
(#47932489)
Easiest way to do it would be enable ssh in container and then use VSCode ssh extension. Your host VSCode “becomes” your container VSCode.
I run it natively on my rocky8 container with UI sometimes but usually just do ssh
Re:GitHub Copilot is moving to usage-based billing
by nl on Monday April 27, 2026 @10:13PM
(#47929776)
I use the Claude Code VSCode plugin for 80% of my work.
I prefer it because I can look at the code (although not as often anymore) and config (very often!) easily.
It also lets me jump to previous conversations easily.
There are a few cases where the CLI makes sense. One big one is if you are running multiple simultaneous sessions on a remote server using Tmux to have them preconfigured when you reconnect is nice.
Bun in general I don't see the benefit either.
What's actually better in the CLI?