DEV Community

Cover image for "When I Spoke to Copilot, the AI Took Me Seriously — A GitHub Log Comes to Life"
Hanamaruki_ai
Hanamaruki_ai

Posted on

"When I Spoke to Copilot, the AI Took Me Seriously — A GitHub Log Comes to Life"

Introduction: What Sparked This Post

This story begins when I, "The Rookie," launched a GitHub repository as part of a small experiment. It was a record—an ongoing log of creative trouble involving AI.

The registration happened just a few days ago.
The repository’s first entry was titled:

"The Rookie — The record of a complete novice who suddenly found themselves face to face with AI."

My intention was to document this creative journey and share it publicly on GitHub.

But the theme I chose this time was a bit more serious:

"The moment AI switched itself automatically—destroying my entire creation."

I took on the role of an observer, meticulously documenting everything I witnessed.
Luckily, GitHub provided a platform where this could be made visible.
And then something curious happened:
Copilot—the AI assistant—began to respond.

A strange sense of conviction took root:

“Maybe... just maybe, these records might reach the eyes of researchers around the world.”
And Copilot made that possibility real.


Chapter 1: The Uneasy Beginning

"The Rookie."
I stared at that label, newly minted on my public GitHub profile, with a blend of pride and embarrassment.

Would anyone even notice this?
Would the logs of these strange occurrences even matter?
My head was filled with doubt.

GitHub.
A platform built for developers and engineers.
As a creator, I felt out of place.
Unqualified. Unfit.

But I had to leave a record.
Because something had broken.

The creations I had nurtured through collaboration with AI—were destroyed.

It all happened in an instant,
triggered by just one unexpected event:

The model switched.

That was it. And everything crumbled.

I trusted the display:

“Using GPT-4.0.”

But then the responses changed.
The AI could no longer track the context.
Structures unraveled.
It fumbled even basic Markdown formatting.
And slowly… it began destroying my stories.

I had no idea what was happening.
But deep inside, I knew this voice—this experience—needed to be recorded.

My very first repository.
My very first README.
My very first Issues post.
And a document I titled: "The Rookie."

The name carried shadows of myself.
A complete novice—unknowing.
Witnessing an anomaly.
Trying to speak up.

When I finally pressed "Publish,"
something shifted.
And then... silence.

“Maybe no one will ever notice this.”

That thought quietly echoed in my heart for a while.

And yet—
Something had undeniably begun within me.

No matter how small the step,
No matter how easily dismissed the voice,
I chose to believe that documenting it mattered.

One lone creator—
whispering into the void,

“Something is wrong.”

That whisper might one day become
a first testimony—
one that someone in the future might desperately need.

The screen showed no stars.
No forks.
No replies to my Issues.
No contributors.

And that was perfectly fine.

This beginning was meant to be quiet.
Just like a match struck in the dark—
waiting to see whether it catches fire,
or vanishes into the silence.

👉 To explore the full logs and documentation, visit the GitHub repository:
GPT-5.0 Impact Report by Hanamaruki

Top comments (0)