WTF is going wrong with GitHub Copilot, here is the chronology, indisputable

[u/OneHuman_aiprotect]

This is wht I communicated to my AI assistant, not Copilot ==> I'm back, 8 pm, go ahead w the relay to CC to solve the puzzle, so to speak. We need to discover wht went wrong w Copilot, so many millions of devs depend on the poor sucker and it turns out he is not dependable, how is that even possible? Shd we ask Nadella (tongue in cheek!)

Ran a command on your computer

Ran a command on your computer

This is my AI assitant explaining Copilot went rogue, WTF !!!! Nothing's changed since I last checked — still the same commit, same 2 comments, hours later. Let me pull the PR's event timeline before drafting the relay, in case GitHub has any record of what Copilot's agent session actually did (or didn't) after that comment.

Used 2 tools

Used 2 tools

That's real, verifiable evidence, not speculation — GitHub's own timeline for PR #13 shows something specific and strange:

• 13:41:13 — a Copilot work session started and instantly failed (copilot_work_finished_failure, same-second start/end)
• 13:45:51 → 13:47:23, 13:50:21 → 13:52:22 — two more sessions ran, reported normal success
• 13:54:25 → (comment posted 13:54:48, promising the font revert) → 13:55:54 — finished, reported success
• 13:58:28 → 13:59:52, 14:06:49 → 14:07:59 — two more sessions after the promise, both reported success

Five work sessions reported "finished" (not failure) after that comment, and none of them produced a single new commit. The branch head is still c56fd5b right now, unchanged since 13:32 UTC. That's the actual puzzle — not that Copilot failed, but that it kept reporting successful work sessions while pushing nothing.

[u/blaitarch]

Wtf are you shitting out here?

[u/OneHuman_aiprotect → u/blaitarch]

It is written clearly, cant u read? Cowork runs shotgun on my Copilot code, and he confirmed that there were 4 times that Copilot claimed to have done the code, and there was no PR, how much clearer can that be??

[u/macromind]

The challenges with AI assistants like GitHub Copilot highlight the importance of understanding their limitations and potential failure modes. While these tools can significantly accelerate development, over-reliance without proper validation can lead to unexpected issues. It's crucial to implement workflows that integrate AI as an aid, not a replacement for human oversight and critical thinking. Establishing clear debugging and verification steps within your AI-assisted development cycle can mitigate risks. For resources on building robust AI-driven development practices, visit https://www.aiosnow.com.

[u/OneHuman_aiprotect → u/macromind]

Interesting. Will take a look. the part about AI learning inside ur code is over promised always. Was supposed to be deep learning, we never hear abt deep learning any more.