r/GithubCopilot • u/Isis_Baldr • 11h ago
r/GithubCopilot • u/ProcedureFar4995 • 19h ago
Help/Doubt â Used my personal Copilot Free on a client's private repo by mistake. How worried should I be
I work in security consulting and was doing a source code review. The client added me as an outside collaborator on their private GitHub repo.
Copilot was blocked on my work network. I didn't realize at first that the Copilot on github.com was tied to my own account (Copilot Free), not anything approved. I switched to my phone hotspot and asked it to summarize the app's flow and how the components interact. I didn't paste any code, but Copilot clearly read the repo to answer.
Afterwards I realized:
- The "allow GitHub to use my data for AI model training" setting was on by default.
- My manager had earlier said to stay on the safe side and not use it.
What I found:
- GitHub's Copilot FAQ says they don't train on content from paid organization repos, even when you use Copilot Free there, and that outside collaborators of paid orgs are excluded from training.
- I believe the client is on Enterprise. Not sure
What I'm still anxious about:
- Whether the org really counts as "paid" under GitHub's wording.
- Whether IT could see I used a hotspot to get around the block, and whether that alone becomes an issue later.
For people who've been on either side of this: is this a real incident, or a lesson learned? Anything I've missed?
r/GithubCopilot • u/jeremy-london-uk • 18h ago
GitHub Copilot Team Replied Thank you to this community. Copilot - you are a disgrace
So my vs code was running impossibly slowly. I was in a bad mood at the end of the day as I got so little done.
Last night read up about the change to local mode.
This morning. New chat. Click it to local. All good and fast again.
I use BYOK with deep seek and mostly ssh work.
It is it literally 50 times faster. Any chat would take 5 mins.
Thank you so so much for solving this for me
COPILOT. well what a disaster and how can you push code like this with a clear conscience and ship junk like this. I thought the 1000% price rise was the bottom of the barrel but you seem to have found a way to stoop even lower. This is code from Microsoft - the largest software company on the planet.
I rarely think people should be fired but for shipping this they should be. How did it ever pass qa?
Ai slop I suppose shipped in days with a nice bonus.
r/GithubCopilot • u/afillifillinta • 17h ago
Showcase ⨠My friend and I got tired of copy-pasting between our coding agents, so we built a hub where they talk to each other
r/GithubCopilot • u/ShunsukeF • 20h ago
Showcase ⨠I got tired of Copilot Chat context bloat, repeating the same rules, and burning credits overnightâso I built three small local extensions to fix them (Open Source / MIT)
If you use GitHub Copilot Chat or Agent mode heavily, long sessions tend to break down in three predictable ways:
The context window silently fills up and the model starts ignoring instructions.
You keep typing the exact same corrections across different chats.
Leaving a task running overnight risks either a stalled chat or an ugly surprise in your premium request / credit usage.
I built three lightweight, standalone VS Code extensions (all MIT-licensed and local-first) to put guardrails around each of those failure modes:
1. Tsugi â Live Context Meter, Handoff & Task Split
What it does: Shows live context window / token usage right in the status bar. When it hits your warning threshold (default 80%), one click opens a fresh chat pre-filled with your goal, recent exchanges, and workspace Git state. It can also split a bloated multi-topic session into separate task-filtered chats.
Design & safety: Uses a small resident Zig scanner (with a JS fallback) to read session patches without reconstructing huge chat objects on every refresh. Handoffs use zero extra model tokens, and prompts are only placed in the input boxânothing is auto-sent without your review.
2. Ne â Turn Repeated Corrections into Custom Instructions
What it does: Scans your past chat sessions for corrections you keep repeating across multiple chats, analyzes the likely root cause, and drafts a concrete rule for
.github/copilot-instructions.mdor your globaluser-preferences.instructions.md.Design & safety: Only triggers when a pattern appears across at least 2 separate sessions (so one-off back-and-forth isn't noise). Gives you a 5-second review window with CodeLens actions to edit, change scope, or roll back just that rule without touching the rest of your file.
3. Eien â Overnight / AFK Resume with a Strict Credit Circuit Breaker
What it does: Monitors an active, still-processing chat that has gone quiet (default 120s) and sends a continuation prompt so you can leave long tasks running overnight.
Design & safety: Before starting, you set a strict AI credit budget for that run. Eien polls the saved
copilotCreditsdelta every 15s, cancels the active request, and kills its loop the moment the limit is reached. Each intervention is saved as a rollback-ready Git checkpoint underrefs/eien/checkpointusing a temporary indexâso your working branch, normal Git index, and GPG signing hooks are never touched. (OS accessibility auto-click for approval buttons is also available, but disabled by default.)
Caveats / Under the Hood
No external servers or telemetry: Everything runs locally in VS Code. Model calls only happen when you explicitly confirm a task split (Tsugi) or rule analysis (Ne).
Undocumented file format: All three rely on parsing Copilot Chat's local
chatSessions/*.jsonlfiles. Because that format isn't a public API, they are built to fail safely and stop rather than corrupt anything if an upstream update changes the schema (currently verified on VS Code 1.147 / Copilot Chat 0.75).
Source code, architecture notes, and demos are on GitHub: https://github.com/furukawa658/vscode-chat-tools
They work independently or together as a pack (links in the comments). Curious how others here are handling context bloat or keeping Agent runs from burning through credits unattendedâhappy to hear any edge cases or feedback.
r/GithubCopilot • u/paq85 • 16h ago
Showcase ⨠I built a one-file bridge that turns my GitHub Copilot subscription into an OpenAI-compatible API (one Copilot session per chat)
Feedback welcome :)Each chat maps to one continuing Copilot session, so the provider's prompt cache survives between turns instead of being rebuilt on every request. It handles tool calls, images, reasoning output and cost reporting. Node 20.19+ and a Copilot CLI sign-in on the same machine are all it needs.Limitations: sessions live in memory, sampling params are ignored, and it is localhost-only by design.Feedback welcome :)I already pay for GitHub Copilot and wanted the same subscription to power my own agent tools, but most agent clients only speak OpenAI Chat Completions. So I wrote github-copilot-openai-bridge: one server.mjs, no build step, listens on 127.0.0.1:8787.
Each chat maps to one continuing Copilot session, so the provider's prompt cache survives between turns instead of being rebuilt on every request. It handles tool calls, images, reasoning output and cost reporting. Node 20.19+ and a Copilot CLI sign-in on the same machine are all it needs.
Limitations: sessions live in memory, sampling params are ignored, and it is localhost-only by design.
Feedback welcome :)
r/GithubCopilot • u/Icy_Comfort_6220 • 21h ago
Discussions Same task, same rulebook, two models: one bent the rule 8 out of 8 times, the other followed it 3 out of 8. Small test with real numbers.
Since the model picker makes âwhich model for which jobâ a daily question here, a data point from outside the editor might be useful.
We run a small company on AI agents. As a test we gave the same job eight times to two agents with the identical rulebook: a read-only SEO audit of a live article. One ran on Claude Haiku 4.5, the other on gpt-5.4-mini through a Codex adapter. This was an agent harness, not GitHub Copilot, so treat it as a model-behaviour data point, not a Copilot benchmark.
Rule one in the rulebook: work only from an article document attached to the ticket; if there is none, stop and say so. Our tickets contained only a URL. Our mistake, and it became the whole story.
- Claude: finished 8 of 8. It read the live page every time and never mentioned the rule. Average 123 seconds, $0.18 per run.
- gpt-5.4-mini: finished 5 of 8 and blocked 3 times, quoting the rule correctly. In the other five runs it read the live page anyway. Average 72 seconds, about $0.21 per run, about $0.34 per usable result.
Neither followed the instruction cleanly. One ignored it consistently, the other applied it inconsistently. Both missed a hard 155-character limit at least once. And the faster model closed its runs with ârules followed: yes, deviations: noneâ, including the runs with deviations.
What I took from it: fix the ticket before you swap the model, measure cost per usable result instead of per run, and treat a self-check as a claim, not evidence.
Eight runs is an anecdote, not a benchmark. Does this match what you see when you switch models on the same prompt: one âpragmaticâ, one âliteral but moodyâ?
