Fix my computer. Then turn it off.

I’m a web developer, but that doesn’t make me a PC repair expert. I usually use Linux for work. When something odd happens on a Windows computer, I can still end up wondering where to look.

That’s one of the things I’m figuring out with Codex: how useful it can be for the small computer problems and tedious actions that interrupt an ordinary day.

The requests I have in mind aren’t especially impressive on paper. A window is off the screen. The computer feels slow. I’m going to bed and want it turned off. But getting help with those things would be pretty awesome.

“The window is off the screen. I can’t grab it.”

This is the kind of problem that can make you feel silly. You know the application is running, but you can’t get to its window.

If you already know where to look, there may be a straightforward way to bring it back. If you don’t, you can waste time trying menus and settings that have nothing to do with the problem.

That’s where I see the value. I want to describe what’s happening in ordinary language and get help finding the right place to investigate. I don’t want to become an expert in every part of the operating system just to get back to my work.

“Is there a way to improve my computer’s performance?”

This is a bigger question. “Make it faster” isn’t a diagnosis, and I don’t expect a magic speed boost from a prompt.

A useful starting point would be to look at what’s running, ask when the slowdown happens, and work out what is actually worth changing. Maybe there’s a simple explanation. Maybe the problem needs more investigation.

I’d rather understand one useful, reversible change than run an unknown cleanup script or delete things because they might be slowing the computer down. The help should make the situation clearer, not leave me with a faster-looking machine and a new problem I don’t understand.

“Can you turn my computer off? I’m going to bed.”

This is the wonderfully ordinary end of the same idea.

I don’t need a whole new application for everything. Sometimes I just want to say what I need and have the small task handled.

Turning a computer off still needs a bit of care. Is there unsaved work? Is a download, build, or another background job still running? A useful assistant should check that context and ask when something important could be interrupted, rather than treating “off” as the only thing that matters.

These requests need a connected computer and authorized access. A website example by itself doesn’t give an assistant control of your machine.

Small tasks, real value

I’m still exploring these workflows. These are examples of what I want to be able to ask, not a claim that one prompt can fix every computer problem.

What interests me is the practical help: knowing where to look, understanding a proposed change, and getting a tedious task out of the way. That doesn’t make specialist knowledge unimportant. It makes that knowledge easier to use when you don’t have it yourself.

The examples on the homepage are a starting point for that exploration. And this is the same approach behind Opinionated defaults, not locked-in choices: show what I know, be clear about the limits, and take care with what I offer.