Github Copilot for the Rest of Us
How GitHub Copilot Became My Sysadmin, Writer, and Creative Partner
When people talk about GitHub Copilot, they almost always describe it the same way: an AI that writes code.
That’s true—Copilot can write code—but treating it as “just a coding tool” is like calling a smartphone
“a device for making phone calls.”
The moment you start using Copilot inside Visual Studio Code, something important changes:
it stops being a code generator and starts behaving more like a context-aware work partner.
Not because it magically knows everything—but because VS Code gives it access to the things that matter:
your files, your folders, your terminals, your scripts, your logs, and even your remote machines.
That’s why this article isn’t about code autocomplete. It’s about the other side of Copilot:
the part that’s useful for people who are building, maintaining, writing, organizing, diagnosing, or shipping
real work—especially the messy kind.
Copilot as a Linux Server Sidekick
One of my most common uses for Copilot has nothing to do with application logic.
I use it for Linux server setup and diagnostics.
If you run Copilot in VS Code and you also use Remote development (SSH), you essentially get a workspace that can:
- Connect to Linux servers over SSH
- Edit remote configuration files safely
- Run commands and scripts in an integrated terminal
- Search through logs and system files quickly
- Manage folders like they’re local projects
That means Copilot isn’t “helping me code.” It’s helping me operate.
I often set up hosting and administration tools like Virtualmin or Webmin, or configure other infrastructure:
load balancers, web servers, SSL, firewall rules, backups—whatever the server needs to become stable and usable.
In those situations Copilot becomes the assistant that speeds up the most annoying parts:
the remembering, the searching, the cross-checking, and the “what does this error actually mean?”
What this looks like in practice
Instead of bouncing between browser tabs and old notes, I’ll use Copilot directly in the workspace:
- “Explain what this service error means and suggest the next checks.”
- “Read this log snippet and list the most likely causes.”
- “Generate a safe Nginx config for this domain layout.”
- “Create a hardening checklist for a fresh VPS.”
- “What would you verify before assuming this is a network issue?”
The benefit isn’t that Copilot is always right. The benefit is that it helps you move faster with less friction—
and it keeps your work inside the same place where the files and commands actually live.
Copilot as an Operations Brain (Not Just a Code Brain)
Here’s the real mental shift:
Copilot doesn’t need to write code to be useful. It needs context.
In VS Code, that context includes the entire workspace: configuration files, scripts, documentation, logs,
command history, and whatever you’re currently working on. Once you realize that, Copilot becomes useful for:
- Debugging infrastructure problems
- Translating “error messages” into “actionable steps”
- Drafting repeatable setup scripts
- Creating operational runbooks and checklists
- Turning tribal knowledge into documentation
It’s especially valuable when the work is messy and practical—when you’re not trying to invent something new,
you’re trying to make something work.
Copilot as a Writing Workspace
Now switch gears. One of the best non-coding Copilot stories I’ve seen is my cousin Alexandra.
She’s writing a small storybook.
She started the way a lot of people do: writing by hand, collecting pages, keeping ideas in scattered places.
At one point she was using Copilot through Microsoft Office, but I suggested a different approach:
Use VS Code as the creative workspace.
Not because VS Code is “a writing tool,” but because it gives you structure for free:
- A folder becomes the book
- Each chapter becomes a file
- Markdown becomes a simple, readable format
- Git (optionally) becomes version history
- Copilot becomes the editor, brainstormer, and consistency checker
In that setup, Copilot isn’t writing the story for you. It’s helping you shape it:
rewrite a paragraph, suggest alternatives, tighten dialogue, keep a consistent voice,
summarize a scene, or generate a few options when you’re stuck.
Yes, Even Illustrations (Within Reason)
This surprises people: you can also support simple illustrations inside a VS Code workspace.
Not full-on painting, obviously—but enough for many small projects.
VS Code can handle things like vector graphics (SVG), simple diagram formats, and text-driven visuals.
If you describe a scene, Copilot can help generate a starting SVG illustration, and you can iterate from there.
It’s not about replacing professional design—it’s about making it easier to prototype, experiment,
and keep everything (text + assets) together in one organized place.
The Hidden Superpower: VS Code’s Ecosystem
Copilot is powerful on its own. But its real strength comes from where it lives.
VS Code brings the infrastructure:
- Extensions for almost any workflow
- Remote development over SSH
- Integrated terminals and tasks
- Search across files and folders
- Versioning and history
- Cross-platform consistency
So whether you’re configuring a server, drafting a runbook, organizing a book, or building a folder-based project,
Copilot adapts because the workspace defines the context.
The Reframe
If there’s one idea worth keeping, it’s this:
GitHub Copilot is not a coding tool. It’s a general-purpose work companion that happens to be excellent at code.
Once you stop limiting it to source files, it becomes:
- A sysadmin assistant
- A documentation partner
- A creative editor
- A workflow accelerator
- A “second brain” inside the tools you already use
And the best part is that none of this requires a new platform or a new habit.
It’s the same VS Code workspace you already know—just used for more than code.
